Trying to add WD 2TB Elements portable drive - communications error

nomadmike

New Member
Oct 20, 2022
29
4
3
Thialand
I just bought a brand new WD 2TB Elements portable drive, connected using both USB3 and USB2 but the drive does not show under Disks, the drive works fine on my windows machine?

I get communications error, could it be the type of USB3 connector with the newer WD drives?

I can see my old passport drive when I attach it
 
Last edited:
Hi,

what is the exact error message?
Please post the output of pveversion -v and lsblk -o +MODEL.

Can you also see if there are any (error) messages related to this in dmesg -H?
(You can also attach the whole thing as a file here, if you want.)
 
See attached outputs

communication failure (0)

[ +0.000001] I/O error, dev sdb, sector 3907028992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[Nov29 16:51] usb 2-3: USB disconnect, device number 2
[ +0.000304] sd 2:0:0:0: [sdb] tag#16 uas_zap_pending 0 uas-tag 2 inflight: CMD
[ +0.000003] sd 2:0:0:0: [sdb] tag#16 CDB: Read(10) 28 00 00 00 00 3f 00 01 00 00
[ +0.000003] sd 2:0:0:0: [sdb] tag#17 uas_zap_pending 0 uas-tag 3 inflight: CMD
[ +0.000002] sd 2:0:0:0: [sdb] tag#17 CDB: Read(10) 28 00 e8 e0 74 3f 00 00 08 00
[ +0.000018] sd 2:0:0:0: [sdb] tag#16 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=77s
[ +0.000001] sd 2:0:0:0: [sdb] tag#16 CDB: Read(10) 28 00 00 00 00 3f 00 01 00 00
[ +0.000001] I/O error, dev sdb, sector 63 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2
[ +0.000035] sd 2:0:0:0: [sdb] tag#17 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=16s
[ +0.000002] sd 2:0:0:0: [sdb] tag#17 CDB: Read(10) 28 00 e8 e0 74 3f 00 00 08 00
[ +0.000001] I/O error, dev sdb, sector 3907023935 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[ +0.000009] device offline error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2
[ +0.000040] device offline error, dev sdb, sector 3907023935 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[ +0.000007] Buffer I/O error on dev sdb1, logical block 1953511936, async page read
[ +0.000010] device offline error, dev sdb, sector 3907023937 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[ +0.000005] Buffer I/O error on dev sdb1, logical block 1953511937, async page read
[ +0.000007] device offline error, dev sdb, sector 3907023939 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[ +0.000006] Buffer I/O error on dev sdb1, logical block 1953511938, async page read
[ +0.000008] device offline error, dev sdb, sector 3907023941 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[ +0.000005] Buffer I/O error on dev sdb1, logical block 1953511939, async page read
[ +0.063553] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
 

Attachments

Last edited:
Hi,

[ +0.000001] I/O error, dev sdb, sector 3907028992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[Nov29 16:51] usb 2-3: USB disconnect, device number 2
[ +0.000304] sd 2:0:0:0: [sdb] tag#16 uas_zap_pending 0 uas-tag 2 inflight: CMD
[ +0.000003] sd 2:0:0:0: [sdb] tag#16 CDB: Read(10) 28 00 00 00 00 3f 00 01 00 00
[ +0.000003] sd 2:0:0:0: [sdb] tag#17 uas_zap_pending 0 uas-tag 3 inflight: CMD
[ +0.000002] sd 2:0:0:0: [sdb] tag#17 CDB: Read(10) 28 00 e8 e0 74 3f 00 00 08 00
[ +0.000018] sd 2:0:0:0: [sdb] tag#16 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=77s
[ +0.000001] sd 2:0:0:0: [sdb] tag#16 CDB: Read(10) 28 00 00 00 00 3f 00 01 00 00
[ +0.000001] I/O error, dev sdb, sector 63 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2
[ +0.000035] sd 2:0:0:0: [sdb] tag#17 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=16s
[ +0.000002] sd 2:0:0:0: [sdb] tag#17 CDB: Read(10) 28 00 e8 e0 74 3f 00 00 08 00
[ +0.000001] I/O error, dev sdb, sector 3907023935 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[ +0.000009] device offline error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2
[ +0.000040] device offline error, dev sdb, sector 3907023935 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[ +0.000007] Buffer I/O error on dev sdb1, logical block 1953511936, async page read
[ +0.000010] device offline error, dev sdb, sector 3907023937 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[ +0.000005] Buffer I/O error on dev sdb1, logical block 1953511937, async page read
[ +0.000007] device offline error, dev sdb, sector 3907023939 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[ +0.000006] Buffer I/O error on dev sdb1, logical block 1953511938, async page read
[ +0.000008] device offline error, dev sdb, sector 3907023941 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[ +0.000005] Buffer I/O error on dev sdb1, logical block 1953511939, async page read
Well, there is definitely something wrong with either the drive or the connection.

Since you say the drive works just fine on some other machine, I'd say that either the USB cable, USB connector on the server, internal cabling or even the connector on the motherboard of the server is bad.

Can you check all these? Esp. the internal cabling onto the motherboard, maybe re-seat all the connections.
Of course, it still cannot be completely ruled out that the drive itself might be (slightly) broken, only working through luck on the Windows machine.
 
The connectors on the server work fine with mouse, keyboard, USB stick and a different HD, its a brand new drive so shouldn't be broken, I have tried the cable from the older passport drive same issue.

The server is running on a BMAX B5 Pro Mini PC Windows 11 CPU Intel® Core™ i5 8260U Intel® UHD Graphics 620