Re: NetBSD 9.2 installer can't detect disk of some Hetzner VPSes

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Sun, 10 Jul 2022 01:14:05 +0530
    From:        Mayuresh <mayuresh%acm.org@localhost>
    Message-ID:  <20220709194405.towbk55owqgg3xsb@localhost>

  | If you could give me some words to grep that will help.

Look for "not configured" first.

Then ata wd[0-9] ld[0-9] and sd[0-9]  (you could probably just use wd0 ld0
and sd0) - but those assume a relatively normal x86 type install, there
are lots of names for disc drivers that might appear.

What would help would be to look at the 48GB install that works, see what
the drive is called in that one, look for that name in dmesg output
(probably in /var/run/dmesg.boot in a running system) then see what it
connects to, look for that, see what it connects to, etc.

Eg: I have

ld0 at nvme0 nsid 1
ld0: 1863 GB, 243201 cyl, 255 head, 63 sec, 512 bytes/sect x 3907029168 sectors
ld0: GPT GUID: fdb094e2-f6fc-45de-827a-106c6748e9c4
dk0 at ld0: "NetBSD_EFI", 522240 blocks at 2048, type: msdos
(and several more dkN at ld0: lines - those aren't important).

jacaranda$ grep nvme0 /var/run/dmesg.boot
nvme0 at pci2 dev 0 function 0: Samsung Electronics (3rd vendor ID) product a80a (rev. 0x00)
nvme0: NVMe 1.3
nvme0: for admin queue interrupting at msix1 vec 0
nvme0: Samsung SSD 980 PRO 2TB, firmware 3B2QGXA7, serial S69ENF0RA54347E
nvme0: for io queue 1 interrupting at msix1 vec 1 affinity to cpu0
[lots more interrupt related lines]
ld0 at nvme0 nsid 1

jacaranda$ grep pci2 /var/run/dmesg.boot
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
nvme0 at pci2 dev 0 function 0: Samsung Electronics (3rd vendor ID) product a80a (rev. 0x00)

jacaranda$ grep ppb1 /var/run/dmesg.boot
ppb1 at pci0 dev 6 function 0: Intel Alder Lake PCIe G4 Root Port 2 (x4) (rev. 0x02)
ppb1: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x4 @ 16.0GT/s
pci2 at ppb1 bus 2
[plus a bunch of false matches - ppb10 (and more) matches as well...]

jacaranda$ grep pci0 /var/run/dmesg.boot
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
[various things connected, including...]
ppb1 at pci0 dev 6 function 0: Intel Alder Lake PCIe G4 Root Port 2 (x4) (rev. 0x02)
Intel product 7af0 (miscellaneous network, revision 0x11) at pci0 dev 20 function 3 not configured


When you reach mainbus0 (or anything that looks like it) you can stop.

The "not configured" there I included just as an example, that's (what will
one day be) an iwl WiFi interface, but NetBSD doesn't have a driver for it yet.

If you get that info for the system that works, you can search for the
same things (except start in the reverse order) in the one that doesn't.
I can't think of any reason simply configuring a bigger drive should make
any difference - it is likely there are other config differences between
the two systems than just that.

kre