On Sun, Jun 28, 2020 at 9:25 AM Nick Holland <n...@holland-consulting.net> wrote:
> > from your dmesg: > sd0 at scsibus1 targ 0 lun 0: <ATA, ST1000LM049-2GH1, SDM2> > naa.5000c500b98a130c > sd0: 953869MB, 512 bytes/sector, 1953525168 sectors, thin > sd1 at scsibus1 targ 1 lun 0: <ATA, M4-CT512M4SSD2, 040H> > naa.500a07510369b769 > sd1: 488386MB, 512 bytes/sector, 1000215216 sectors, thin > sd2 at scsibus1 targ 2 lun 0: <ATA, SAMSUNG SSD PM85, EXT4> > naa.5002538844584d30 > sd2: 244198MB, 512 bytes/sector, 500118192 sectors, thin > > ERR M basically means that biosboot(8), which is "tagged" with the > physical location of /boot(8) on the disk, doesn't see the marker > that indicates that what it is pointing at is actually /boot. The > windows 10 boot loader is pulling from a disk other than sd0, the pbr > is pointing at something "correct" if it were sd0, but the Windows > boot loader is trying to pull it from whatever the new default disk > is. Maybe. > > There may be some bcdedit magic that can say "boot from this other disk" > which might solve your problem, but I have no idea. A lame way of > doing this might be to shrink your Windows partition by 1G, and install > your OpenBSD root partition there, and the rest on sd0. > Rad, thanks Nick! I'm going to poke around with BCDEasy or whatever that 3rd party software is since it'll be easier to figure out rather than reading through all the bcdedit documentation. I swear back in the Windows ntldr days that I was running Windows and OpenBSD on separate disks so I think this should be doable with their current boot loader. Worse comes to worse I'll go with your last suggestion! Greg
