23.09.1 to 24.03 Beta Not Setting Proper Boot Environment
-
@cmcdonald I can't even remember at the moment, I might not have even done that since I think I started on 22.01 from the ISO but maybe it was the CE version available around that time. So maybe 2.5?
-
The problem is your boot loader is REALLY old. As old as whatever the first version you installed was. So old in fact that the loader at that time didn't even understand temporary boot environments.
We recently started updating the boot loader on EFI but haven't done the BIOS path yet. I'm working on that today.
In the mean time, I will circile back after lunch and give you instructions on how to update the boot loader manually.
-
@cmcdonald That makes sense, yah the VM has been around for a while now so that's not surprising!
-
-
/root: gpart show => 40 157286320 da0 GPT (75G) 40 1024 1 freebsd-boot (512K) 1064 984 - free - (492K) 2048 2097152 2 freebsd-swap (1.0G) 2099200 155185152 3 freebsd-zfs (74G) 157284352 2008 - free - (1.0M)
-
@Lurick said in 23.09.1 to 24.03 Beta Not Setting Proper Boot Environment:
/root: gpart show => 40 157286320 da0 GPT (75G) 40 1024 1 freebsd-boot (512K) 1064 984 - free - (492K) 2048 2097152 2 freebsd-swap (1.0G) 2099200 155185152 3 freebsd-zfs (74G) 157284352 2008 - free - (1.0M)
cool
so you'll want to do the following (assuming
default
is still the upgraded BE anddefault_20240308062713
is the old BE.bectl mount default gpart bootcode -b /tmp/be_mount.XXXX/boot/pmbr -p /tmp/be_mount.XXXX/boot/gptzfsboot -i 1 da0 bectl unmount -f default bectl activate -t default shutdown -r now
You should now boot into
default
at which point it will set itself to be the Next Boot Environment (assuming that it does boot properly) -
@cmcdonald Awesome, thanks!
It booted up just fine and without issue, just had to fix the typo, haha :)
Will monitor over the next couple of updates and make sure but hopefully that fixed it! -
And I will be teaching the
pfSense-boot
package how to update BIOS systems :) -
@cmcdonald
Awesome, just make sure you use default and not defaut ;) -
Fixed above lol
-
@cmcdonald
Just a quick update, all good with the latest build too so no more issues updating :) -
@Lurick glad we finally found the root cause