On Sun, 20 Sep 2026 04:30:55 +0000 drango <[email protected]> wrote:
> > On Sat, 19 Sep 2026, Duke Normandin wrote: > > > On Sat, 19 Sep 2026 21:37:21 -0600 > > Ian Darwin <[email protected]> wrote: > > > > > On 9/19/26 9:17 PM, Duke Normandin wrote: > > > > I see - but Linux is on one HDD and OpenBSD on a completely different > > > > HDD. GRUB on the Linux HDD doesn't know anything about the 2nd HDD. > > > > > > > > For the time being, I'm select the boot drive from the BIOS boot order. > > > > Would this scenario still cause the "Boot Mode Mismatch"? TIA ... > > > > > > I doubt it. But I'm not sitting in front of your computer. > > > > > > Please explain what you mean by "the boot starts over". > > > > > > And show exactly what you see and what you're typing at the OpenBSD boot > > > prompt. > > > > It's awkward because I'm answering on a Linux box. Basically, I get to the > > OpenBSD boot prompt and 4-5 seconds later it tries to boot, chokes, tries > > again, chokes, on and on. > > > > I then squeezed in an `ls' to have it stop cycling like that. > > Tried boot /bsd.rd and I think that the command that got me to of all things > > the Install/Upgrade/etc/etc menu like I was installing all over again. > > I hit reboot, went into my BIOS, selected my Linux drive and called it a > > flop! > > > > I would have to boot OpenBSD again to get the exact details/msgs. > > At the boot prompt, is there a command available to list the devices that > > OpenBSD sees to boot from. I'm thinking I could do something like: > > `boot hd1a:bsd.rd > > > > -- > > Duke > > > > > > You can run with bsd.rd, it won't break anything. > When it says (I) Install (U) Upgrade... (that initial line) > > There is an (S) option for shell. > > Do that, and you can grab output from fdisk -v hda2 <- your drive > > It its EFI it will look kinda like this: > > # fdisk -v sd0 > #: type [ start: size ] > 1: EFI Sys [ 64: 960 ] > d0834013-dab8-44df-a5e4-123148f17e03 EFI System Area > 3: OpenBSD [ 1024: 500117105 ] > cd356d77-8369-44b4-996e-79e8b9a47bfe OpenBSD Area > > If its MBR, it will look something like this: > > Primary GPT: > Not Found > > Secondary GPT: > Not Found > > MBR: > Disk: sd0 geometry: 60801/255/63 [976773168 Sectors] > Offset: 0 Signature: 0xAA55 > Starting Ending LBA Info: > #: id C H S - C H S [ start: size ] > ------------------------------------------------------------------------------- > 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] > Unused > 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] > Unused > 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] > Unused > *3: A6 0 1 2 - 60801 80 63 [ 64: 976773104 ] > OpenBSD > > You'll (we'll) know your on EFI or MBR > > I think you can see the disks from the Ramdisk image. > If not, before running fdisk you might need to run this: > > # cd /dev > # sh MAKEDEV sd0 <- change to your drive name > > I think this works anyway. Someone more knowledgable will help more I > suspect. > Much obliged! Getting late here for this old man - so it'll be a tomorrow job, otherwise I'm sure to make matters worse than they are. LOL Can't wait to try it out. Thanks again ... -- Duke
