On Fri, Nov 07, 2025 at 03:04:07PM -0700, Luke A. Call wrote: > On 2025-11-07 21:58:35+0000, Crystal Kolipe <[email protected]> > wrote: > > On Fri, Nov 07, 2025 at 02:52:17PM -0700, Luke A. Call wrote: > > > On 2025-11-07 20:44:28+0000, Crystal Kolipe <[email protected]> > > > wrote: > > > > On Fri, Nov 07, 2025 at 01:28:17PM -0700, Luke A. Call wrote: > > > > > On 2025-11-07 18:45:00+0000, Crystal Kolipe > > > > > <[email protected]> wrote: > > > > > > On Thu, Nov 06, 2025 at 02:33:20PM -0700, Luke A. Call wrote: > > > > > > > Hi. I am upgrading my test (& backup) laptop from 7.7 to 7.8, and > > > > > > > running sysupgrade rebooted it, but after I entered the FDE key, > > > > > > > it > > > > > > > checks hardware or something for a bit then I think I see "panic" > > > > > > > flash on the screen, and it reboots, even from single-user > > > > > > > mode. Unfortunately that doesn't let me provide a dmesg. It is > > > > > > > an > > > > > > > old dell inspiron. > > > > > > > > > > > > Based on the information you've provided, my first guess is that > > > > > > it's > > > > > > not finding the root filesystem. Since you're using FDE and the > > > > > > physical > > > > > > disk is recognised as wd0, (and there are no other physical disks), > > > > > > your > > > > > > softraid cryto device would be sd0. > > > > > > > > > > > > > So I tried running upgrade from a CD with cd78.iso on it. After > > > > > > > the > > > > > > > prompt to choose a keyboard, it asks which disk is the root disk. > > > > > > > > > > > > > > Typing "?" for details says "wd0: ....", which I believe is > > > > > > > correct, but > > > > > > > entering wd0 at the prompt gives "wd0 is not a valid root disk", > > > > > > > or for > > > > > > > other variations besides wd0, it says "no such disk"). > > > > > > > > > > > > On your system: > > > > > > > > > > > > wd0 is a valid physical disk. It is not the volume that holds the > > > > > > root > > > > > > filesystem. > > > > > > > > > > > > sd0 should appear once the softraid crypto volume, which resides on > > > > > > wd0, > > > > > > is attached. For some reason this doesn't seem to be happening. > > > > > > > > > > > > It might provide useful information if you can boot in to bsd.rd > > > > > > from > > > > > > OpenBSD 7.8-release, (booting from the CD), drop to a shell, and > > > > > > manually > > > > > > try to attach the softraid volume with bioctl. Knowing whether > > > > > > that succeeds > > > > > > would narrow down the possibilities a bit. > > > > > > > > > > Thank you. Would this be the right command to attach it? > > > > > bioctl -cC -l sd0a softraid0 > > > > > > > > No, first there should be a space between -c and C, and secondly the > > > > device > > > > you specify to -l is supposed to be the partition that holds the > > > > underlying > > > > softraid volume. On your machine this is most likely wd0a, or if not, > > > > it's > > > > another partition on wd0. > > > > > > > > So you probably want: > > > > > > > > bioctl -c C -l wd0a softraid0 > > > > > > I have tried bioctl -c C -l wd0[a-s] softraid0 > > > ...and with "/dev/wd0[a-c]" and with just wd0, > > > ...and I am feeling error prone and am probably doing something stupid, > > > > You did make the device files first, didn't you? > > > > # cd /dev > > # sh ./MAKEDEV wd0 > > # sh ./MAKEDEV sd0 > > I hadn't (not understanding how much of this was pre-existing due to the > data already being on that volume, or something), but doing that > worked!: > softraid0: CRYPTO volume attached as sd0 > > What next?
Well, before re-booting it's best to detach the softraid volume again: # bioctl -d sd0 ... otherwise you'll get a warning on next boot about it not being shut down cleanly. Other than that, at least we know that there is nothing fundamentally preventing attaching and mounting your softraid volume with the 7.8 kernel. Does the output from: # disklabel sd0 look normal?
