USB 3.0 to SATA - Storage Disconnect

[dbrenuk]

Hi Proxmox folks,

I have two external SSDs which I'm trying to connect to my Proxmox node via USB 3.0 to SATA cables. However, I'm seeing behaviour where I have one of them plugged into the USB 3.0 port running just fine, but when I plug the other one in, the first one disconnects

Here are the relevent system logs where you can see the behaviour:

NOTE: vg-ssd-crucial/lv-ssd-crucial is the LV thin pool for the disconnected SSD.

Sep 12 16:53:58 proxmox01 kernel: usb 2-1: new SuperSpeed USB device number 12 using xhci_hcd
Sep 12 16:53:58 proxmox01 kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=9201, bcdDevice=f2.00
Sep 12 16:53:58 proxmox01 kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 12 16:53:58 proxmox01 kernel: usb 2-1: Product: Ugreen Storage Device
Sep 12 16:53:58 proxmox01 kernel: usb 2-1: Manufacturer: Ugreen
Sep 12 16:53:58 proxmox01 kernel: usb 2-1: SerialNumber: 132711258E08
Sep 12 16:53:58 proxmox01 kernel: usb 2-1: Enable of device-initiated U1 failed.
Sep 12 16:53:58 proxmox01 kernel: usb 2-1: Enable of device-initiated U2 failed.
Sep 12 16:53:58 proxmox01 kernel: usb 2-1: Enable of device-initiated U1 failed.
Sep 12 16:53:58 proxmox01 kernel: usb 2-1: Enable of device-initiated U2 failed.
Sep 12 16:53:58 proxmox01 kernel: scsi host4: uas
Sep 12 16:53:58 proxmox01 kernel: usb 2-3: USB disconnect, device number 2 <--- Here
Sep 12 16:53:58 proxmox01 kernel: scsi 4:0:0:0: Direct-Access Samsung SSD 870 QVO 1TB 1.02 PQ: 0 ANSI: 6
Sep 12 16:53:58 proxmox01 kernel: sd 3:0:0:0: [sda] Synchronizing SCSI cache
Sep 12 16:53:58 proxmox01 kernel: sd 4:0:0:0: Attached scsi generic sg0 type 0
Sep 12 16:53:58 proxmox01 kernel: sd 4:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Sep 12 16:53:58 proxmox01 kernel: sd 4:0:0:0: [sdc] Write Protect is off
Sep 12 16:53:58 proxmox01 kernel: sd 4:0:0:0: [sdc] Mode Sense: 37 00 00 08
Sep 12 16:53:58 proxmox01 kernel: sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 12 16:53:58 proxmox01 kernel: sd 4:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
Sep 12 16:53:58 proxmox01 kernel: sd 4:0:0:0: [sdc] Optimal transfer size 33553920 bytes
Sep 12 16:53:58 proxmox01 kernel: sd 4:0:0:0: [sdc] Attached SCSI disk
Sep 12 16:53:58 proxmox01 kernel: sd 3:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Sep 12 16:53:59 proxmox01 pvestatd[1897]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Sep 12 16:53:59 proxmox01 pvestatd[1897]: no such logical volume vg-ssd-crucial/lv-ssd-crucial

The two USB 3.0 to SATA cables I'm using are different, one is a UGREEN drive enclosure and the other is this. I've had to plug one in at a time to get the below lsusb outputs:

root@proxmox01:~# lsusb
Bus 002 Device 003: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge

root@proxmox01:~# lsusb
Bus 002 Device 012: ID 0bda:9201 Realtek Semiconductor Corp. Ugreen Storage Device

Version details:

root@proxmox01:~# uname -a
Linux proxmox01 6.8.12-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-1 (2024-08-05T16:17Z) x86_64 GNU/Linux
root@proxmox01:~# pveversion --verbose
proxmox-ve: 8.2.0 (running kernel: 6.8.12-1-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.8: 6.8.12-1
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
proxmox-kernel-6.2.16-12-pve: 6.2.16-12
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.2
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.2-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1

I'm not entirely sure why this is happening so any help with this issue would be greatly appreciated. Let me know if further details are needed and I can provide those.

 

[dbrenuk]

Just a small update. I shutdown the node and plugged both USB 3.0 to SATA cables in, so far it's showing both connected:

root@proxmox01:~# lsusb
Bus 002 Device 003: ID 0bda:9201 Realtek Semiconductor Corp. Ugreen Storage Device
Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge

I will monitor to see if either of them get disconnected.