External NVME dock shows 0 byte drive (multiple brands)

shoelesshunter · 2023-02-04 05:15:27

I purchased a uGreen (realtek) NVME dock. The kernel saw the scsi device, but not the 2TB drive inside it. I tried over A, C, and thunderbolt.

I purchased another adapter that explicitly said "linux compatible." (brand called Pluggable). same issue.

I changed

/etc/usb_modeswitch.conf

To include

DiabableSwitching=1

I rebooted. Drive not detected. The drive is a WD Black with only 2 years of use. Never any issues. And yes, it is nvme, and this is an nvme dock. (the laptop takes internal m.2 SATA).

thoughts? Thank you.

seth · 2023-02-04 08:35:53

My initial thought would be to look at the system journal or at least follow the kernels ringbuffer (dmesg -w) when attaching the dock to get a modest idea what's actually going on beyond "iTs dOeS NoTs wOrKs lOl", https://bbs.archlinux.org/viewtopic.php?id=57855

shoelesshunter · 2023-02-04 13:41:38

journalctl -k | grep -i scsi
Feb 04 06:33:27 kyzer kernel: SCSI subsystem initialized
Feb 04 06:33:27 kyzer kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 241)
Feb 04 06:33:27 kyzer kernel: scsi host0: ahci
Feb 04 06:33:27 kyzer kernel: scsi host1: ahci
Feb 04 06:33:27 kyzer kernel: scsi 1:0:0:0: Direct-Access     ATA      WDC  WDS200T2B0B 20WD PQ: 0 ANSI: 5
Feb 04 06:33:27 kyzer kernel: sd 1:0:0:0: [sda] Attached SCSI disk
Feb 04 06:33:28 kyzer kernel: scsi host2: usb-storage 2-3:1.0
Feb 04 06:33:29 kyzer kernel: scsi 2:0:0:0: Direct-Access     Generic- SD/MMC CRW       1.00 PQ: 0 ANSI: 6
Feb 04 06:33:37 kyzer kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk

sdb is indeed the nvme adapter.

dmesg -w showed nothing as I connected the drive.

shoelesshunter · 2023-02-04 15:36:34

back to the realtek adapter I began with:

dmesg | grep -i real*
[    0.240112] NR_IRQS: 20736, nr_irqs: 2048, preallocated irqs: 16
[    0.254902] process: using mwait in idle threads
[    0.290356] DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations
[    0.290356] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.290356] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    1.243571] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.342410] Write protecting the kernel read-only data: 28672k
[    2.804677] systemd[1]: Created slice Slice /system/getty.
[    2.804898] systemd[1]: Created slice Slice /system/modprobe.
[    2.805096] systemd[1]: Created slice Slice /system/syslog-ng.
[    2.805274] systemd[1]: Created slice Slice /system/systemd-fsck.
[    2.805414] systemd[1]: Created slice User and Session Slice.
[    2.805626] systemd[1]: Reached target Local Encrypted Volumes.
[    2.805635] systemd[1]: Reached target Login Prompts.
[    2.805643] systemd[1]: Reached target Local Integrity Protected Volumes.
[    2.805657] systemd[1]: Reached target Path Units.
[    2.805666] systemd[1]: Reached target Remote File Systems.
[    2.805671] systemd[1]: Reached target Slice Units.
[    2.805683] systemd[1]: Reached target Local Verity Protected Volumes.
[    2.810786] systemd[1]: Starting Create List of Static Device Nodes...
[    2.948386] systemd[1]: Finished Create List of Static Device Nodes.
[    4.608907] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC285: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[    4.608913] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    4.608916] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[    4.608918] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[    4.608919] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[    4.608921] snd_hda_codec_realtek hdaudioC0D0:      Mic=0x19
[    4.608922] snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
[    5.373292] scsi 2:0:0:0: Direct-Access     Realtek  RTL9210          1.00 PQ: 0 ANSI: 6
[    5.404844] sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[    5.405860] sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    5.412709] sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[    6.191654] Bluetooth: hci0: Reading supported features failed (-16)
[   13.376123] thermal thermal_zone5: failed to read out thermal zone (-61)
[   14.847917] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   18.068423] wlan0: deauthenticating from 80:b9:7a:8c:a2:c6 by local choice (Reason: 3=DEAUTH_LEAVING)
[   18.682286] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  104.800062] scsi 2:0:0:0: Direct-Access     Realtek  RTL9210          1.00 PQ: 0 ANSI: 6
[  104.807718] sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[  104.808840] sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  104.816090] sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK

seth · 2023-02-04 15:54:17

grep -i scsi

Don't grep. Certainly not w/o -C16 but don't grep. You don't know where the error occurs.

dmesg -w showed nothing as I connected the drive.

And WDS200T2B0B is an unrelated internal drive?
Did you only attach the drive to the dock or the dock w/ the drive attached to the computer?
If not, try the latter and monitor "dmesg -w".

[qutoe]I purchased another adapter that explicitly said "linux compatible."[/qutoe]
PCI or USB id?

shoelesshunter · 2023-02-04 16:02:10

thank you.

I'm assuming the WDS200T2B0B entry is the internal WD Blue M.2 SATA

dmesg -w

[ 1577.057136] usb 1-1: USB disconnect, device number 6
[ 1582.125872] usb 1-1: new high-speed USB device number 7 using xhci_hcd
[ 1582.315693] usb 1-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
[ 1582.315708] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1582.315713] usb 1-1: Product: Ugreen Storage Device
[ 1582.315718] usb 1-1: Manufacturer: Ugreen
[ 1582.315722] usb 1-1: SerialNumber: 0129380015FF
[ 1582.343057] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 1582.343420] scsi host2: usb-storage 1-1:1.0
[ 1583.348081] scsi 2:0:0:0: Direct-Access     Realtek  RTL9210          1.00 PQ: 0 ANSI: 6
[ 1583.356021] sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[ 1583.356034] sd 2:0:0:0: [sdc] Sense Key : Illegal Request [current] 
[ 1583.356040] sd 2:0:0:0: [sdc] Add. Sense: Invalid field in cdb
[ 1583.356049] sd 2:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
[ 1583.356054] sd 2:0:0:0: [sdc] 0-byte physical blocks
[ 1583.356580] sd 2:0:0:0: [sdc] Write Protect is off
[ 1583.356592] sd 2:0:0:0: [sdc] Mode Sense: 37 00 00 08
[ 1583.357221] sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 1583.364858] sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[ 1583.364863] sd 2:0:0:0: [sdc] Sense Key : Illegal Request [current] 
[ 1583.364865] sd 2:0:0:0: [sdc] Add. Sense: Invalid field in cdb
[ 1583.366046] sd 2:0:0:0: [sdc] Attached SCSI disk

I am attaching the dock containing the drive each time, not the drive to the dock.

seth · 2023-02-04 16:15:11

Here's the explanation:

[ 1583.356021] sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[ 1583.356034] sd 2:0:0:0: [sdc] Sense Key : Illegal Request [current]
…
[ 1583.364858] sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[ 1583.364863] sd 2:0:0:0: [sdc] Sense Key : Illegal Request [current]

Google spat out https://github.com/raspberrypi/linux/is … -782822391 - underpowered.
But that's on a raspberry pi.

It goes on w/ https://github.com/raspberrypi/linux/is … 1320966950 and https://github.com/raspberrypi/linux/is … 1321029071

shoelesshunter · 2023-02-05 14:48:16

thanks. I just found that thread about the pi and was about to share it here.

the drive I am using is a 2TB WD Black. I don't know much about SSDs, but I am assuming as far as consumer SSDs go, it is a power hog.

I just ordered a powered hub. I'll report back how that goes.

of course, I already reinstalled Arch and restored all my configs from cloud backups. I need to learn patience. I appreciate the time you spent on this.

Last edited by shoelesshunter (2023-02-05 14:48:43)

Arch Linux

#1 2023-02-04 05:15:27

External NVME dock shows 0 byte drive (multiple brands)

#2 2023-02-04 08:35:53

Re: External NVME dock shows 0 byte drive (multiple brands)

#3 2023-02-04 13:41:38

Re: External NVME dock shows 0 byte drive (multiple brands)

#4 2023-02-04 15:36:34

Re: External NVME dock shows 0 byte drive (multiple brands)

#5 2023-02-04 15:54:17

Re: External NVME dock shows 0 byte drive (multiple brands)

#6 2023-02-04 16:02:10

Re: External NVME dock shows 0 byte drive (multiple brands)

#7 2023-02-04 16:15:11

Re: External NVME dock shows 0 byte drive (multiple brands)

#8 2023-02-05 14:48:16

Re: External NVME dock shows 0 byte drive (multiple brands)

Board footer