It would seem there was an issue with the socket on the nvme enclosure - actually the WD NVME connector is slightly differently dimensioned than the Samsung. I swapped housings and I got the WD NVME to be recognized. Now it can be partitioned. I'm in the midst of partitioning with gparted and selected gpt over MBR. Now to create a new partition. I'd like to use the whole 1TB as a partition. It's defaulting to free space preceding = 1MiB, free space following = 0MiB.
What does one use as a Partition name? What is a standard convention? What about label? I am selecting EXT4 as the file system. Any advice? Thanks. On Sun, Mar 21, 2021 at 11:05 AM Bruce Labitt <bdlab...@gmail.com> wrote: > I have a USB3.2-PCIE NVME adapter (actually have 3 of them) using the > JM583 chip. I also have a Samsung 970 EVO Pro 1TB NVME and recently bought > 2 WD 1TB NVME cards. > > I cannot get a WD NVME to be recognized by the OS. I haven't tried the > second WD NVME as I am leaving the package unopened. > > lsusb reveals the JMicron adapter so I have the ID > fdisk -l and lsblk do not show the WD device, nor the JM adapter > The WD disk has never been partitioned or formatted. > > sudo dmesg | tail -n 50 shows some sort of issue. > [ 4015.843758] usb 2-2.1.2: USB disconnect, device number 10 > [ 7180.940213] usb 2-2.1.4: USB disconnect, device number 5 > [ 7186.023443] usb 2-2.1.2: new SuperSpeed Gen 1 USB device number 11 > using xhci_hcd > [ 7186.054656] usb 2-2.1.2: New USB device found, idVendor=152d, > idProduct=0583, bcdDevice= 2.09 > [ 7186.054671] usb 2-2.1.2: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 7186.054684] usb 2-2.1.2: Product: USB to PCIE Bridge > [ 7186.054695] usb 2-2.1.2: Manufacturer: JMicron > [ 7186.054706] usb 2-2.1.2: SerialNumber: 0123456789ABCDEF > [ 7186.069481] scsi host1: uas > [ 7186.070909] scsi 1:0:0:0: Direct-Access JMicron Generic > 0209 PQ: 0 ANSI: 6 > [ 7186.072283] sd 1:0:0:0: Attached scsi generic sg1 type 0 > [ 7194.231709] sd 1:0:0:0: [sdb] Unit Not Ready > [ 7194.231728] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] > [ 7194.231744] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 > [ 7194.233639] sd 1:0:0:0: [sdb] Read Capacity(16) failed: Result: > hostbyte=0x00 driverbyte=0x08 > [ 7194.233657] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] > [ 7194.233673] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 > [ 7194.235281] sd 1:0:0:0: [sdb] Read Capacity(10) failed: Result: > hostbyte=0x00 driverbyte=0x08 > [ 7194.235297] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] > [ 7194.235313] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 > [ 7194.236113] sd 1:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B) > [ 7194.236129] sd 1:0:0:0: [sdb] 0-byte physical blocks > [ 7194.237556] sd 1:0:0:0: [sdb] Test WP failed, assume Write Enabled > [ 7194.238118] sd 1:0:0:0: [sdb] Asking for cache data failed > [ 7194.238133] sd 1:0:0:0: [sdb] Assuming drive cache: write through > [ 7194.239724] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not > a multiple of physical block size (0 bytes) > [ 7194.284844] sd 1:0:0:0: [sdb] Unit Not Ready > [ 7194.284866] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] > [ 7194.284881] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 > [ 7194.286398] sd 1:0:0:0: [sdb] Read Capacity(16) failed: Result: > hostbyte=0x00 driverbyte=0x08 > [ 7194.286415] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] > [ 7194.286430] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 > [ 7194.288145] sd 1:0:0:0: [sdb] Read Capacity(10) failed: Result: > hostbyte=0x00 driverbyte=0x08 > [ 7194.288166] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] > [ 7194.288183] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 > [ 7194.293600] sd 1:0:0:0: [sdb] Attached SCSI disk > > However, the same adapter works fine using the 970 Pro NVME device. On > the 970 I have the complete backup to my laptop. The 970 auto mounts. > Is it possible that UAS doesn't work for the WD NVME? Or is the WD NVME > defective? Or the WD NVME hasn't been prepared properly? My google-fu > seems to be weak - it's been difficult to find appropriate information. > Hope it's just that I missed a step... > I have heard of blacklisting the UAS driver, but it seems odd the adapter > works reliably for the 970 but not the WD. > > I'd greatly appreciate a hint. Currently running on an RPI4B-4GB > Raspberry Pi OS 32bit since my new laptop bit the dust. The laptop has > been sent back for repair. > Thanks for your patience... > > >
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
