Adguard Home User - update from 24.1.10 to 24.7 failing

[jcsp101]

I tried to update from 24.1 to 24.7 multiple times and a weird issue after reboot (kernel showing an update to 24.1 from 24.7, see below) as well as internet not working.
https://imgur.com/XOyjw9B

I tried it from the Web UI first, then via SSH, also tested live boot as well.

Updating from web UI - the update "completes" but after reboot incorrect versions shows and the Internet doesn't work (though local access to devices like home assistant does) and a kernel "update" is available from from 27.1 to 24.1.

Update via SSH shell update as well (option 12) - after reboot, same as above, no internet, and webUI shows incorrect versions

I also tried a live boot of the new version and importing my current config, which also fails in that internet doesn't work, though this might be because of services not aligning with settings (I use unbound and adguard DNS both as packages on OPNsense)

my ssd has tons of space. I did try a health audit which yielded a checksum mismatch with my adguard home package though i don't think this is related (I assume the mismatch occurred it's since i hit update in the adguard webUI rather than letting opnsense package manager update adguard at least once recently).


Additional note:
I first noticed this some weeks ago, and i wasn't even on 24.1.10 yet - and one thing i tried was declining the major update and instead trying to do the latest minor update (to 24.1.10), and that one was successful.

[newsense]

Try this command and post the output here

Code: [Select]

opnsense-update -pA 24.7.1

[jcsp101]

Try this command and post the output here

Code: [Select]

opnsense-update -pA 24.7.1

to confirm, should i run this SSH shell?

[jcsp101]

here is the output:

Code: [Select]

root@OPNsense:~ # opnsense-update -pA 24.7.1
Updating OPNsense repository catalogue...
pkg-static: Repository OPNsense has a wrong packagesite, need to re-create database
pkg-static: [url]https://mirror.wdc1.us.leaseweb.net/opnsense/FreeBSD:13:amd64/24.7.1[/url]
/latest/meta.txz: Not Found
repository OPNsense has no meta file, using default settings
pkg-static: [url]https://mirror.wdc1.us.leaseweb.net/opnsense/FreeBSD:13:amd64/24.7.1[/url]
/latest/packagesite.pkg: Not Found
pkg-static: [url]https://mirror.wdc1.us.leaseweb.net/opnsense/FreeBSD:13:amd64/24.7.1[/url]
/latest/packagesite.txz: Not Found
Unable to update repository OPNsense
Updating mimugmail repository catalogue...
mimugmail repository is up to date.
Error updating repositories![quote author=jcsp101 link=topic=42587.msg210963#msg210963 date=1725174496]


[newsense]

Sorry that was the wrong command.

What about this one:

Code: [Select]

opnsense-update -bkr 24.7.3 -a FreeBSD:14:amd64

[jcsp101]

Sorry that was the wrong command.

What about this one:

Code: [Select]

opnsense-update -bkr 24.7.3 -a FreeBSD:14:amd64

OK i tried that, here's the output:

root@OPNsense:~ # opnsense-update -bkr 24.7.3 -a FreeBSD:14:amd64
Fetching base-24.7.3-amd64.txz: ..[fetch: https://mirror.wdc1.us.leaseweb.net/opnsense/FreeBSD:14:amd64/24.7.1/sets/base-24.7.3-amd64.txz.sig: Not Found] failed, no signature found

[newsense]

THis should fix it then

Code: [Select]

opnsense-update -bkr 24.7.3 -a FreeBSD:14:amd64 -A 24.7

[jcsp101]

THis should fix it then

Code: [Select]

opnsense-update -bkr 24.7.3 -a FreeBSD:14:amd64 -A 24.7

It moved forward and then after finishing requested a reboot so I typed reboot in the console.

Post reboot nothing is working nor accessible via SSH or webUI. Had to plug a monitor into the computer, and I see that there's no IP address for LAN or WAN

Also, it shows that it is still on OPNsense 24.1.10_8

Also, I cannot log into OPNsense, login doesn't work inputting username and pressing enter requests username again)

[newsense]

Yeah something is preventing the upgrade to complete successfully.

Best case, it's a (weird) permission issue. Worst case is the drive.

Do a fresh install, it is the only way to find out what's happening. If it works ok after importing the config and restoring the plugins you're in luck. Otherwise it is the drive - which is where I would expect things to land if you didn't do anything fancy there other than configuring OPNsense as needed and applying patches.

[jcsp101]

Yeah something is preventing the upgrade to complete successfully.

Best case, it's a (weird) permission issue. Worst case is the drive.

Do a fresh install, it is the only way to find out what's happening. If it works ok after importing the config and restoring the plugins you're in luck. Otherwise it is the drive - which is where I would expect things to land if you didn't do anything fancy there other than configuring OPNsense as needed and applying patches.

yeah honestly i got tired of troubleshooting it, i had made notes on my settings manually and reinstalled the whole thing from scratch.

for reference i doubt it's the drive, since i'm running a mirrored install on 2 SSDs and it's doubtful both failed at the same time