[SOLVED] USB Drive invisible

DrillSgtErnst

Active Member
Jun 29, 2020
91
6
28
Hi,
on my machine I can no longer see USB attached Drives.
I have an USB Drive attached, but it does not show in lsblk.
Neither do I see it in the Drives Tab.
my pveversion

root@pve:~# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve)
pve-manager: 7.0-13 (running version: 7.0-13/7aa7e488)
pve-kernel-helper: 7.1-2
pve-kernel-5.11: 7.0-8
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-3-pve: 5.11.22-7
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.11-1
proxmox-backup-file-restore: 2.0.11-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-4
pve-firmware: 3.3-2
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-16
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1
root@pve:~#

I can't see the drive as a redirectable USB Devices either

lsusb is empty either
root@pve:~# lsusb
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 004: ID 0b1f:03ee Insyde Software Corp. RNDIS/Ethernet Gadget
Bus 007 Device 003: ID 0557:9241 ATEN International Co., Ltd SMCI HID KM
Bus 007 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I could see the drive about a month ago.
 
can you post the output of 'dmesg' as well as a journal output from a boot where it worked?
 
[10444.906952] Buffer I/O error on dev zd0, logical block 266320290, lost async page write
[10444.906960] Buffer I/O error on dev zd0, logical block 762111, lost async page write
[10444.906962] Buffer I/O error on dev zd0, logical block 266320291, lost async page write
[10446.235368] zd0: p1
[10446.254126] zd48: p1 p2
[244940.071157] EXT4-fs (sde): recovery complete
[244940.072336] EXT4-fs (sde): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[244944.187416] xhci_hcd 0000:44:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0031 address=0xfd80f000 flags=0x0000]
[244974.405325] sd 18:0:0:0: [sde] tag#23 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT
[244974.405874] sd 18:0:0:0: [sde] tag#23 CDB: Write(10) 2a 00 00 00 07 74 00 00 7f 00
[244979.513194] xhci_hcd 0000:44:00.0: xHCI host not responding to stop endpoint command.
[244979.513759] xhci_hcd 0000:44:00.0: USBSTS:
[244979.514256] xhci_hcd 0000:44:00.0: xHCI host controller not responding, assume dead
[244979.514756] xhci_hcd 0000:44:00.0: HC died; cleaning up
[244979.515285] usb 6-1: cmd cmplt err -108
[244979.515298] sd 18:0:0:0: [sde] tag#22 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD
[244979.526162] sd 18:0:0:0: [sde] tag#22 CDB: Write(10) 2a 00 00 00 06 f4 00 00 80 00
[244979.532392] usb 6-1: USB disconnect, device number 2
[244979.532649] sd 18:0:0:0: [sde] tag#21 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD
[244979.533662] sd 18:0:0:0: [sde] tag#21 CDB: Write(10) 2a 00 00 00 06 74 00 00 80 00
[244979.534179] sd 18:0:0:0: [sde] tag#20 uas_zap_pending 0 uas-tag 1 inflight: CMD
[244979.534700] sd 18:0:0:0: [sde] tag#20 CDB: Write(10) 2a 00 00 00 05 f4 00 00 80 00
[244979.535220] sd 18:0:0:0: [sde] tag#17 uas_zap_pending 0 uas-tag 5 inflight: CMD
[244979.535744] sd 18:0:0:0: [sde] tag#17 CDB: Read(10) 28 00 00 00 00 00 00 00 20 00
[244979.536268] sd 18:0:0:0: [sde] tag#20 uas_eh_abort_handler 0 uas-tag 1 inflight:
[244979.544387] sd 18:0:0:0: [sde] tag#20 CDB: Write(10) 2a 00 00 00 05 f4 00 00 80 00
[244979.557513] sd 18:0:0:0: [sde] tag#17 uas_eh_abort_handler 0 uas-tag 5 inflight:
[244979.569597] sd 18:0:0:0: [sde] tag#17 CDB: Read(10) 28 00 00 00 00 00 00 00 20 00
[244979.633196] sd 18:0:0:0: Device offlined - not ready after error recovery
[244979.633936] sd 18:0:0:0: Device offlined - not ready after error recovery
[244979.634530] sd 18:0:0:0: Device offlined - not ready after error recovery
[244979.635080] sd 18:0:0:0: Device offlined - not ready after error recovery
[244979.635629] sd 18:0:0:0: Device offlined - not ready after error recovery
[244979.657180] blk_update_request: I/O error, dev sde, sector 15264 op 0x1:(WRITE) flags 0x800 phys_seg 127 prio class 0
[244979.657850] blk_update_request: I/O error, dev sde, sector 14240 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
[244979.658432] blk_update_request: I/O error, dev sde, sector 13216 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 0
[244979.659001] blk_update_request: I/O error, dev sde, sector 12192 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 0
[244979.659573] blk_update_request: I/O error, dev sde, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
[244979.660145] blk_update_request: I/O error, dev sde, sector 3905159168 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[244979.660726] Buffer I/O error on dev sde, logical block 488144896, lost sync page write
[244979.661321] JBD2: Error -5 detected when updating journal superblock for sde-8.
[244979.666021] Aborting journal on device sde-8.
[244979.668901] blk_update_request: I/O error, dev sde, sector 3905159168 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[244979.671091] blk_update_request: I/O error, dev sde, sector 3905159168 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[244979.673270] Buffer I/O error on dev sde, logical block 488144896, lost sync page write
[244979.676672] JBD2: Error -5 detected when updating journal superblock for sde-8.
[244979.703314] sd 18:0:0:0: [sde] Synchronizing SCSI cache
[244979.720764] blk_update_request: I/O error, dev sde, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[244979.721712] blk_update_request: I/O error, dev sde, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[244979.993176] sd 18:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[244980.137294] xhci_hcd 0000:44:00.0: WARN Can't disable streams for endpoint 0x81, streams are being disabled already
[245983.142188] zd48: p1 p2
[245983.189503] zd0: p1
[251193.054072] zd0: p1
[251194.827592] zd48: p1 p2
root@pve:~#

I do not have an older Log, since I am not sure since when this Problem persists
root@pve:~# journalctl -xe
░░
░░ The job identifier is 417535.
Nov 09 12:49:33 pve login[2997303]: ROOT LOGIN on '/dev/pts/1'
Nov 09 12:49:40 pve postfix/smtp[2995940]: connect to mail.happypost.de[91.136.133.179]:25: Connection timed out
Nov 09 12:49:40 pve postfix/smtp[2995940]: EA84D22380: to=<info@happycomputer.eu>, relay=none, delay=57304, delays=57273/0.01/30/0, dsn=4.4.1, status=deferred (connect to mail.happypost.de[91.136.133>
Nov 09 12:49:40 pve postfix/smtp[2995939]: connect to smtpin.rzone.de[81.169.145.97]:25: Connection timed out
Nov 09 12:49:40 pve postfix/smtp[2995939]: connect to smtpin.rzone.de[2a01:238:20a:202:50f0::1097]:25: Network is unreachable
Nov 09 12:49:40 pve postfix/smtp[2995939]: 003AD20B8F: to=<praxis@frauenaerzte-leer.de>, relay=none, delay=319778, delays=319748/0.01/30/0, dsn=4.4.1, status=deferred (connect to smtpin.rzone.de[2a01>
Nov 09 12:50:00 pve systemd[1]: Starting Proxmox VE replication runner...
░░ Subject: A start job for unit pvesr.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvesr.service has begun execution.
░░
░░ The job identifier is 417599.
Nov 09 12:50:01 pve systemd[1]: pvesr.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvesr.service has successfully entered the 'dead' state.
Nov 09 12:50:01 pve systemd[1]: Finished Proxmox VE replication runner.
Subject: A start job for unit pvesr.service has finished successfully
Defined-By: systemd
Support: https://www.debian.org/support

A start job for unit pvesr.service has finished successfully.

The job identifier is 417599.
Nov 09 12:51:01 pve systemd[1]: Starting Proxmox VE replication runner...
Subject: A start job for unit pvesr.service has begun execution
Defined-By: systemd
Support: https://www.debian.org/support

A start job for unit pvesr.service has begun execution.

The job identifier is 417659.
Nov 09 12:51:01 pve systemd[1]: pvesr.service: Succeeded.
Subject: Unit succeeded
Defined-By: systemd
Support: https://www.debian.org/support

The unit pvesr.service has successfully entered the 'dead' state.
Nov 09 12:51:01 pve systemd[1]: Finished Proxmox VE replication runner.
Subject: A start job for unit pvesr.service has finished successfully
Defined-By: systemd
Support: https://www.debian.org/support

A start job for unit pvesr.service has finished successfully.

The job identifier is 417659.
lines 5765-5816/5816 (END)
 
Just for closure.
The USB Port seems to be broken all of the sudden. Another USB-Controller and everything just works.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!