On Sun, 20 Sep 2026 19:25:47 -0600 Duke Normandin <[email protected]> wrote:
> On Sun, 20 Sep 2026 22:45:22 +0000 > [email protected] wrote: > > > On Sun, 20 Sep 2026, Duke Normandin wrote: > > > > > On Sun, 20 Sep 2026 04:30:55 +0000 > > > drango <[email protected]> wrote: > > > > > > [snip] > > > > > > > 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. > > > > > > Sorry - no joy! > > > > > > sh MAKEDEV sd1 => no such file or directory > > > fdisk -v sd1 => ditto > > > sh MAKEDEV => ditto > > > > > > I did a `ls /dev' and got a listing, but 'sd' or 'hd' didn't show up. I > > > hosed something - somewhere!! I hope that you have more clues in your bag > > > of tricks. :) Thanks ... > > > > > > > > > > Are you certain sd1 is your disk? > > > > What do you get if you look at your dmesg? > > dmesg | grep "lun 0" > > I tried sd0, sd1, sd2 and a few others - nada! > I'll leave Linux and try out your `dmesg ...' suggestion. Thx! > Please look at these 2 screenshots. https://controlc.com/a/Vx9o70h `dmesg' shows sd1 in the screenshot, but I can't run any utility programs - not fdisk, dmesg or `sh MAKEDEV'. What gives?
