Let me jump in here (sorry for poor formatting, I'm on mobile). I used to run -current on my Panasonic Lets's Note CF-NX4 using a GPT-formatted SATA SSD. I was also using full disk encryption set up by the installer of 7.6 before I made the initial sysupgrade -s to -current.
I did a sysupgrade -s a few days ago during my weekly system management cycle, and I got hit by this issue as well. Naturally, I chocked this up to my own pebcak as I run a custom kernel due to quirks of my touchpad. As such, I never bothered to report this to misc@. I later re-installed 7.6 and decided it'd be better if I ran -stable for the time being. But- now that I notice that others had this issue, it might not just be my "pebcak". Maybe it is full disk encryption? Or- possibly full disk encrypted setups are additionally affected? Dirk, do you use full disk encryption on your affected machine? Or- do you have a multi-disk setup? More information on your disk and partitioning scheme on the affected hardware would be helpful. Thanks. -------- Original Message -------- From: Janne Johansson <icepic...@gmail.com> Sent: February 25, 2025 8:13:10 AM CST To: dirk coetzee <dcoetze...@yahoo.com> Cc: "misc@openbsd.org" <misc@openbsd.org> Subject: Re: Bad bootblocks 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. -- Sent from a mobile, please excuse shitty formatting.
