Hi Janne, Sort of. This laptop was installed with a fresh 7.6 build and ergo has FDE. So actual device is sd0 - but booting crypto device is sd1 (root fs). This is a standard install - all defaults, just any sysupgrades ;-)
Prior sysupgrades seemed to handle this fine. Regards Tuesday 25 February 2025 at 10:13:24 pm AWST, Janne Johansson <icepic...@gmail.com> wrote: Den tis 25 feb. 2025 kl 12:18 skrev dirk coetzee <dcoetze...@yahoo.com>: > Hi All, > FYI: > I have been upgrading current frequently (sysupgrade -s). > And getting the message: "Failed to install bootblocks." "You will not be > able to boot OpenBSD from sd1.". Please see attached image for further > context. > > The system is able to boot without issues. Does it boot off the drive that the sysupgrade environment thinks is "sd1" or not? My guess is that the scripts are trying to figure out which drive the BIOS sees first, and place-or-update a bootblock there, but if there is a mismatch between what it guesses and where the root filesystem (or the /boot file) is, then the message seems correct. This doesn't prevent you having a booting system, but there are several ways to have weird setups with (for instance) the bootblocks on one drive and the root fs on another. In such a case one could get that message while the system still "works", though perhaps the bootblocks are never updated on the drive that actually does the initial boot. -- May the most significant bit of your life be positive.
