<div dir="ltr">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.<div>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.</div><div><br></div><div>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.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Mar 21, 2021 at 11:05 AM Bruce Labitt <<a href="mailto:bdlabitt@gmail.com">bdlabitt@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">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.<div><br><div>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.</div></div><div><br></div><div>lsusb reveals the JMicron adapter so I have the ID</div><div>fdisk -l and lsblk do not show the WD device, nor the JM adapter</div><div>The WD disk has never been partitioned or formatted.</div><div><br></div><div>sudo dmesg | tail -n 50 shows some sort of issue.</div><div>[ 4015.843758] usb 2-2.1.2: USB disconnect, device number 10<br>[ 7180.940213] usb 2-2.1.4: USB disconnect, device number 5<br>[ 7186.023443] usb 2-2.1.2: new SuperSpeed Gen 1 USB device number 11 using xhci_hcd<br>[ 7186.054656] usb 2-2.1.2: New USB device found, idVendor=152d, idProduct=0583, bcdDevice= 2.09<br>[ 7186.054671] usb 2-2.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3<br>[ 7186.054684] usb 2-2.1.2: Product: USB to PCIE Bridge<br>[ 7186.054695] usb 2-2.1.2: Manufacturer: JMicron<br>[ 7186.054706] usb 2-2.1.2: SerialNumber: 0123456789ABCDEF<br>[ 7186.069481] scsi host1: uas<br>[ 7186.070909] scsi 1:0:0:0: Direct-Access JMicron Generic 0209 PQ: 0 ANSI: 6<br>[ 7186.072283] sd 1:0:0:0: Attached scsi generic sg1 type 0<br>[ 7194.231709] sd 1:0:0:0: [sdb] Unit Not Ready<br>[ 7194.231728] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] <br>[ 7194.231744] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 <br>[ 7194.233639] sd 1:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08<br>[ 7194.233657] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] <br>[ 7194.233673] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 <br>[ 7194.235281] sd 1:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08<br>[ 7194.235297] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] <br>[ 7194.235313] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 <br>[ 7194.236113] sd 1:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)<br>[ 7194.236129] sd 1:0:0:0: [sdb] 0-byte physical blocks<br>[ 7194.237556] sd 1:0:0:0: [sdb] Test WP failed, assume Write Enabled<br>[ 7194.238118] sd 1:0:0:0: [sdb] Asking for cache data failed<br>[ 7194.238133] sd 1:0:0:0: [sdb] Assuming drive cache: write through<br>[ 7194.239724] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)<br>[ 7194.284844] sd 1:0:0:0: [sdb] Unit Not Ready<br>[ 7194.284866] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] <br>[ 7194.284881] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 <br>[ 7194.286398] sd 1:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08<br>[ 7194.286415] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] <br>[ 7194.286430] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 <br>[ 7194.288145] sd 1:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08<br>[ 7194.288166] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] <br>[ 7194.288183] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 <br>[ 7194.293600] sd 1:0:0:0: [sdb] Attached SCSI disk<br></div><div><br></div><div>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.</div><div>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</div><div>seems to be weak - it's been difficult to find appropriate information. Hope it's just that I missed a step...</div><div>I have heard of blacklisting the UAS driver, but it seems odd the adapter works reliably for the 970 but not the WD. </div><div><br></div><div>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.</div><div>Thanks for your patience...</div><div><br></div><div><br></div></div>
</blockquote></div>