Failed boot enviroment
-
Hi.
Upgraded to many betas and RC`s but now this:
Boot verification failed for auto-default-20230818173559_20250611064117. Netgate pfSense Plus was automatically rebooted back into auto-default-20230818173559_20250611064117_20250611195530. @ 2025-06-11 20:00:24
What?
-
@maverick_slo the update failed do you have any other logs with it when it was updating ???
-
I do have the same issue that the system cannot apply the update and falls back to the previous kernel during the update boot. See syslog below:
pfsenseBoot_25.03b0610_20250612.txt
Thank you for looking into this and for providing suggestions on how to proceed.
-
Hmm, can I assume neither of you were running the June 6th build?
That looks like a bug in the upgrade code that should be fixed. Hmm.
@meelek I can see your ZFS zpool is named 'zroot'. @maverick_slo do you also have a non-default zpool name?
-
I'm on 15th May build, pool name zroot.
-
@stephenw10 said in Failed boot enviroment:
Hmm, can I assume neither of you were running the June 6th build?
Yes, that is correct as with 0606 the same isuue occurred.
-
Can you try running
zpool statusandzfs list? -
pool: zroot state: ONLINE status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 da0p4 ONLINE 0 0 0 errors: No known data errorsNAME USED AVAIL REFER MOUNTPOINT zroot 8.40G 37.6G 96K /zroot zroot/ROOT 3.61G 37.6G 96K none zroot/ROOT/auto-default-20230818173559 392K 37.6G 2.00G / zroot/ROOT/auto-default-20230818173559/var_cache_pkg 8K 37.6G 217M /var/cache/pkg zroot/ROOT/auto-default-20230818173559/var_db_pkg 64K 37.6G 10.0M /var/db/pkg zroot/ROOT/auto-default-20230818173559_20250611064117 704M 37.6G 2.00G / zroot/ROOT/auto-default-20230818173559_20250611064117/var_cache_pkg 218M 37.6G 218M /var/cache/pkg zroot/ROOT/auto-default-20230818173559_20250611064117/var_db_pkg 3.10M 37.6G 10.1M /var/db/pkg zroot/ROOT/auto-default-20230818173559_20250611064117_20250611195530 2.92G 37.6G 2.00G / zroot/ROOT/auto-default-20230818173559_20250611064117_20250611195530/var_cache_pkg 442M 37.6G 225M /var/cache/pkg zroot/ROOT/auto-default-20230818173559_20250611064117_20250611195530/var_db_pkg 15.3M 37.6G 10.0M /var/db/pkg zroot/reservation 96K 42.2G 96K /zroot/reservation zroot/tmp 560K 37.6G 560K /tmp zroot/var -
Ah, I'm guessing that's an old install that has been upgraded for some time (years)?
That looks like the old ZFS layout we used when it was first introduced in the installer. That's why you're still hitting this issue.
Are you able to just reinstall? That's the easiest way to get to the new layout TBH.
-
Heh I have no license
-
@stephenw10 said in Failed boot enviroment:
zpool status
pool: zroot
state: ONLINE
status: Some supported and requested features are not enabled on the pool.
The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(7) for details.
config:NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 raidz3-0 ONLINE 0 0 0 ada0p4 ONLINE 0 0 0 ada1p4 ONLINE 0 0 0 ada2p4 ONLINE 0 0 0 ada3p4 ONLINE 0 0 0 ada4p4 ONLINE 0 0 0errors: No known data errors
zfs list
NAME USED AVAIL REFER MOUNTPOINT
zroot 48.3G 378G 153K /zroot
zroot/ROOT 4.97G 378G 153K none
zroot/ROOT/24_11 797K 378G 2.29G /
zroot/ROOT/24_11/var_cache_pkg 12.8K 378G 291M /var/cache/pkg
zroot/ROOT/24_11/var_db_pkg 102K 378G 11.1M /var/db/pkg
zroot/ROOT/25_03_beta 765M 378G 2.20G /
zroot/ROOT/25_03_beta/var_cache_pkg 217M 378G 217M /var/cache/pkg
zroot/ROOT/25_03_beta/var_db_pkg 2.78M 378G 11.1M /var/db/pkg
zroot/ROOT/25_03_beta_20250612072157 4.23G 378G 2.26G /
zroot/ROOT/25_03_beta_20250612072157/var_cache_pkg 515M 378G 236K /var/cache/pkg
zroot/ROOT/25_03_beta_20250612072157/var_db_pkg 20.8M 378G 11.1M /var/db/pkg
zroot/reservation 153K 421G 153K /zroot/reservation
zroot/tmp 1.00M 378G 1.00M /tmp
zroot/var 678M 378G 678M /var -
Yup same thing there, it's missing some of the datasets we now use.
If you're seeing the upgrade available (which you are) then your NDI is seen as eligible for Plus. If you boot the installer it will offer you the available Plus versions. Including 25.03-Beta.
-
@stephenw10
So that is the only option to perform a reinstallation followed by a config restore? -
@stephenw10
So what youre saying is that I will have to reinstall my 14 boxes across EU countries?Weeeel nope.
I will migrate them to something else, what is able to be upgraded ... Geez.
-
I'm saying if it's a test box that's next to you then that is trivial and easiest way to get past it. But not if you have numerous remote devices obviously.
Let me see...
-
@maverick_slo said in Failed boot enviroment:
@stephenw10
So what youre saying is that I will have to reinstall my 14 boxes across EU countries?Weeeel nope.
I will migrate them to something else, what is able to be upgraded ... Geez.
I'm working on a solution here. Ideally we will get it in the next beta
-
Sure, one box no prob.
Hyperv vm, no prob.
Remote, pain
-
I've got a fix, it will land in next beta.
-
Thanks!
-
@cmcdonald said in Failed boot enviroment:
I've got a fix, it will land in next beta.
Thank you, it is appreciated
