On Tue, Jun 16, 2020 at 10:34:44AM +0200, Janne Johansson wrote: > Den m??n 15 juni 2020 kl 20:18 skrev Kenneth R Westerback < > [email protected]>: > > > > If it would help, I could screenshot one page at a time, that seems to be > > > the best I can do today. > > > > Works for me, though I don't recommend sending all those pics to > > bugs@. > > > > > http://c66.it.su.se:8080/obsd/amd-dmesg-jpegs/index.html > > Painstakingly screenshot:ed one at a time, but hopefully readable as a > series of images in a row. > > -- > May the most significant bit of your life be positive.
I see nvme0: KXG60ZNV256G Toshiba, firmware AGGA4103, serial <blah> scsibus2 at nvme0: 2 targets, initiator 0 sd0 at scsibus2 targ 1 lun 0: <NVMe, KXG60NZV256G TOS, AGGGA> sd0: 244198MB, 512 bytes/sector, 500118192 sectors nvme1: Micro_9300_MTFDHAL3T8DP, firmware 11300DG0, serial <blah> scsibus3 at nvme1: 33 targets, initiator 0 sd1 at scsibus3 targ 1 lun 0: <NVMe, Micron_9300_MTFD, 1130> sd1: 3662830MB, 512 bytes/sector, 7501476528 sectors <sd2 -> sd32 at scsibus3 targ 2 -> 32 lun 0: <NVMe, Micron_9300_MTFD, 1130> nvme2: Micro_9300_MTFDHAL3T8DP, firmware 11300DG0, serial <blah> scsibus4 at nvme2: 33 targets, initiator 0 sd33 at scsibus4 targ 1 lun 0: <NVMe, Micron_9300_MTFD, 1130> sd33: 3662830MB, 512 bytes/sector, 7501476528 sectors <sd34 -> sd64 at scsibus4 targ 2 -> 32 lun 0: <NVMe, Micron_9300_MTFD, 1130> nvme3: Micro_9300_MTFDHAL3T8DP, firmware 11300DG0, serial <blah> scsibus5 at nvme3: 33 targets, initiator 0 sd65 at scsibus5 targ 1 lun 0: <NVMe, Micron_9300_MTFD, 1130> sd65: 3662830MB, 512 bytes/sector, 7501476528 sectors <sd66 -> sd96 at scsibus6 targ 2 -> 32 lun 0: <NVMe, Micron_9300_MTFD, 1130> nvme4: INTEL SSDPED1K375GA, firmware E2010435, serial <blah> scsibus6 at nvme4: 2 targets, initiator 0 sd97 at scsibus6 targ 1 lun 0 <NVMe, INTEL SSDPED1K37, E201> sd97: 357707MB, 512 bytes/sector, 732585168 sectors So FIVE physical drives? It looks to me like the Micron devices are reporting/configured with 33 namespaces. Each namespace is treated as a separate disk. I don't know if the device is actually configured this way, or is reporting a max number where other drives are reporting actual configured namespaces. I am *guessing* that all the namespaces other than the first one have 0 sectors allocated. But we print out the "sdNN at scsibusXX ..." line before the size is determined via INQUIRY. Dunno if that is avoidable. A SCSIDEBUG kernel will print a lot of interesting information that would shed more light. .... Ken
