The installer sends an email to root with
Subject: $(hostname) upgrade log
containing all the information of the upgrade run.
Please show the contents of those mails for an upgrade run with and
without the removable device attached. And indicated which one is which.
There is also a good chance that the dmesg buffer keeps the dmesg of the
bsd.rd run and is accessible in /var/run/dmesg.boot. If so please
provide the bsd.rd dmesg with and without the removable device attached.
That might shed some light on what is going on.
On 2022-01-23 10:03 UTC, Stuart Henderson <stu.li...@spacehopper.org> wrote:
> Installing the UP kernel on an MP system is definitely a bug. Forwarding
> to bugs@ where there's more chance of it being seen by somebody with
> time to look at it.
>
> This might explain the several reports I've seen where people have had
> 1 cpu show up (and usually have "helpful" people telling them to set
> hw.smt=1 ...)
>
>
> From: rgc <rgci...@disroot.org>
> Newsgroups: gmane.os.openbsd.misc
> Subject: sysupgrade, softraid and USB removable devices
> Date: Fri, 21 Jan 2022 20:29:09 +0900
>
> misc@
>
> to document and share something that puzzled me for a bit. other
> users might encounter it too.
>
> given the random nature of device enumeration i don't think it is a
> bug. BUT this scenario is very easy to reproduce.
>
>
> recently i have acquired an old Thinkpad T440p. i populated it with
> 2 SATA SSDs in a RAID 1 configuration. one in main HDD bay, the other
> drive in a caddy that fits in the CD bay. GPT whole disk.
>
> i also have a 2Tb external USB device that i use as a backup device.
>
> i did a sysupgrade to GENERIC.MP#275 today and was surprised to see
> the updater installed an SP kernel.
> ---
> syncing disks... done
> rebooting...
> OpenBSD 7.0-current (RAMDISK_CD) #268: Thu Jan 20 13:09:19 MST 2022
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> real mem = 17035915264 (16246MB)
> ---
>
> after install:
> ---
> root on rd0a swap on rd0b dump on rd0b
> syncing disks...
> OpenBSD 7.0-current (GENERIC) #271: Thu Jan 20 12:55:58 MST 2022
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
> real mem = 17035915264 (16246MB)
> ---
>
> i forced the same update and looked *more* closely at the logs.
>
> i see something like (copying from a video on my phone):
>
> ---
> <dmesg>
> softraid0: volume sd3 is roaming, it used to be sd2, updating metadata.
> :
> <upgrade>
> :
> Making all device nodes... done.
> fw_update: added none; update none; kept ...
> installboot: cross-device install
>
> Failed to install bootblocks.
> You will not be able to boot OpenBSD from sd2.
> <reboot>
> ---
>
> despite the ominous message, the laptop boots but only with an SP kernel.
>
> during upgrade, i see sd0 as one of the RAID disk; sd1 as the other RAID
> disk. sd2 is the external USB device. sd3 is the softraid device.
>
> on a *normal* boot. sd0 and sd1 are the RAID disks. sd2 is the
> softraid device. and sd3 is the external USB device. i guess this is why
> i see the *roaming* message.
>
> the upgrade seems to have skipped installing the MP kernel afterwards.
>
>
> FIX: remove/unplug the external USB device before doing upgrades, and
> remember to plug it back in so that the backups don't fail.
>
>
--
I'm not entirely sure you are real.
