USB Device is not showing up

[neuleo]

Hey Guys, ich have a Problem.

I have a hard drive connected to my proxmox server via USB and it worked just fine for a long time. I connected the USB Device in Proxmix via : USB Vendor/Device ID".

Now i want to connect the USB Device to another vm. A few Months ago it worked. But somehow now it doesnt. It just doesnt show up.


This is the vm with the already working USB device


That ist the config:


When I try to select for example USP Port, it looks the following:

Its just empty.

Same if i want to reselect the it using USB Vendor/Device ID:



Does anybody have an Idea, why thats so?

 

[Chris]

Hi,
please post your Proxmox VE version pveversion -v as well as the output of lsusb. There should be at least some devices listed. Can you check in your browsers developer tools network tab if you get error responses? Also, please check the journal for errors, you can get a paged view of it since boot in reverse via journalctl -b -r.

 

[neuleo]

pveversion -v:

root@pve:~# pveversion -v
proxmox-ve: 8.0.2 (running kernel: 6.2.16-6-pve)
pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390)
proxmox-kernel-helper: 8.0.3
pve-kernel-5.15: 7.4-4
proxmox-kernel-6.2.16-6-pve: 6.2.16-7
proxmox-kernel-6.2: 6.2.16-7
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.4
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.7
libpve-guest-common-perl: 5.0.4
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.5
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.2-1
proxmox-backup-file-restore: 3.0.2-1
proxmox-kernel-helper: 8.0.3
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.0.6
pve-cluster: 8.0.3
pve-container: 5.0.4
pve-docs: 8.0.4
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.5
pve-qemu-kvm: 8.0.2-4
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1



lsusb gives no output at all.


journalctl -b -r
root@pve:~# journalctl -b -r | grep "error"
Aug 17 09:01:38 pve sshd[992323]: error: Received disconnect from 192.168.178.14 port 50215:13: Unable to authenticate [preauth]
Aug 12 11:56:05 pve ntfs-3g[484]: Failed to close volume /dev/sdb1: Input/output error
Aug 12 11:56:05 pve ntfs-3g[484]: Failed to sync device /dev/sdb1: Input/output error
Aug 12 11:55:55 pve kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
root@pve:~# journalctl -b -r | grep "failed"
Aug 14 15:27:04 pve pvedaemon[931]: VM 102 qmp command failed - VM 102 not running
Aug 14 15:17:46 pve pvedaemon[932]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Aug 14 15:17:45 pve pvestatd[928]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Aug 14 15:17:35 pve pvestatd[928]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Aug 14 15:17:25 pve pvestatd[928]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Aug 14 15:17:20 pve pvedaemon[931]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Aug 14 15:17:15 pve pvestatd[928]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Aug 14 15:17:05 pve pvestatd[928]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Aug 14 15:16:55 pve pvestatd[928]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Aug 14 15:16:46 pve pvedaemon[931]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Aug 14 15:16:45 pve pvestatd[928]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Aug 14 15:16:35 pve pvestatd[928]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - got timeout
Aug 14 15:16:20 pve pvedaemon[930]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - unable to connect to VM 102 qmp socket - timeout after 51 retries
Aug 12 11:56:05 pve kernel: sd 3:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Aug 12 11:55:56 pve kernel: i915 0000:00:02.0: [drm] [ENCODER:94DI A/PHY A] failed to retrieve link info, disabling eDP
Aug 12 11:55:56 pve kernel: thermal thermal_zone4: failed to read out thermal zone (-61)
Aug 12 11:55:55 pve kernel: cfg80211: failed to load regulatory.db
Aug 12 11:55:55 pve kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Aug 12 11:55:55 pve kernel: sdhci-pci 0000:00:1e.6: failed to setup card detect gpio

 

[Chris]

lsusb gives no output at all.

The WebUI registers usb devices based on such output afaik, so the issue seems to be somewhere deeper. What's the output of mount, also did you try rebooting your system? Can you see your device showing up in dmesg -w while you plug it in, whats the output?

 

[neuleo]

root@pve:~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=16338796k,nr_inodes=4084699,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3274692k,mode=755,inode64)
/dev/mapper/pve-root on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=20509)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-sysctl.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
/dev/sda2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
ramfs on /run/credentials/systemd-tmpfiles-setup.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
//192.168.178.24/proxmox on /mnt/pve/NAS type cifs (rw,relatime,vers=2.1,cache=strict,username=proxmox,domain=workgroup,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.178.24,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=3274688k,nr_inodes=818672,mode=700,inode64)
root@pve:~#


Yes, i rebooted the system multiple times. The bug has been around for a about a month now.

I can't test the dmesg -w Command, because i am not at Home now.

 

[neuleo]

Does anybody know why that is?

 

[Chris]

Does anybody know why that is?

Your proc and sysfs are mounted, so please check if the device shows up in dmesg -w. Do you mabye have some custom udev rules?

 

[neuleo]

Thats the Output i get from dmsg -w | grep "usb":

root@pve:~# dmesg -w | grep "usb"
[    0.423129] usbcore: registered new interface driver usbfs
[    0.423129] usbcore: registered new interface driver hub
[    0.423129] usbcore: registered new device driver usb
[    1.568932] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.02
[    1.568934] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.568935] usb usb1: Product: xHCI Host Controller
[    1.568937] usb usb1: Manufacturer: Linux 6.2.16-8-pve xhci-hcd
[    1.568938] usb usb1: SerialNumber: 0000:00:14.0
[    1.571260] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.02
[    1.571262] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.571264] usb usb2: Product: xHCI Host Controller
[    1.571265] usb usb2: Manufacturer: Linux 6.2.16-8-pve xhci-hcd
[    1.571266] usb usb2: SerialNumber: 0000:00:14.0
[    1.824647] usb 1-7: new full-speed USB device number 2 using xhci_hcd
[    1.973929] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b, bcdDevice= 0.01
[    1.973935] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.100566] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
[    2.121570] usb 2-2: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
[    2.121574] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    2.121576] usb 2-2: Product: Ugreen Storage Device
[    2.121578] usb 2-2: Manufacturer: Ugreen
[    2.121580] usb 2-2: SerialNumber: 26A1EE8304FD
[    2.125565] usbcore: registered new interface driver usb-storage
[    2.129031] usbcore: registered new interface driver uas
[    5.858244] usbcore: registered new interface driver btusb
[   15.103377] usb usb2: USB disconnect, device number 1
[   15.103379] usb 2-2: USB disconnect, device number 2
[   15.421461] usb usb1: USB disconnect, device number 1
[   15.421464] usb 1-7: USB disconnect, device number 2

Don't even know what udev is, so i guess no. I left my proxmox pretty much stock and didnt change custom settings or something like that.


The crazy Thing is, that it works on a VM i created a while ago. But if i try to select it, it doesnt appear. Even if i try to reselect it on the VM, where its already working

 

[Chris]

[ 15.103377] usb usb2: USB disconnect, device number 1 [ 15.103379] usb 2-2: USB disconnect, device number 2 [ 15.421461] usb usb1: USB disconnect, device number 1 [ 15.421464] usb 1-7: USB disconnect, device number 2

Seems like your devices got disconnected again, nevertheless you should get the usb hubs in the output of lsusb. What is the output of ls -lah /sys/bus/usb/devices/?

 

[neuleo]

The Output is the following:

root@pve:~# ls -lah /sys/bus/usb/devices/
total 0
drwxr-xr-x 2 root root 0 Aug 30 23:38 .
drwxr-xr-x 4 root root 0 Aug 30 23:38 ..
lrwxrwxrwx 1 root root 0 Aug 30 23:38 1-0:1.0 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-0:1.0
lrwxrwxrwx 1 root root 0 Aug 30 23:38 1-7 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-7
lrwxrwxrwx 1 root root 0 Aug 30 23:38 1-7:1.0 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0
lrwxrwxrwx 1 root root 0 Aug 30 23:38 1-7:1.1 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1
lrwxrwxrwx 1 root root 0 Aug 30 23:38 2-0:1.0 -> ../../../devices/pci0000:00/0000:00:14.0/usb2/2-0:1.0
lrwxrwxrwx 1 root root 0 Aug 30 23:38 2-2 -> ../../../devices/pci0000:00/0000:00:14.0/usb2/2-2
lrwxrwxrwx 1 root root 0 Aug 30 23:38 2-2:1.0 -> ../../../devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0
lrwxrwxrwx 1 root root 0 Aug 30 23:38 usb1 -> ../../../devices/pci0000:00/0000:00:14.0/usb1
lrwxrwxrwx 1 root root 0 Aug 30 23:38 usb2 -> ../../../devices/pci0000:00/0000:00:14.0/usb2

 

[Zetto]

Did this get resolved? I'm having the same issue. I can't select or see any USB device in the UI. However, I installed one VM from a backup that already had a USB device passed through and the works fine (the USB device shows up as 'unknown' in the proxmox UI).

If I do

lsusb

I only see the HUB's but none of the attached USB devices.

 

[fuztec25]

Same here, connected a Studiologic SL88 master keyboard (to be used with VST plugins), showed once, even used it, then dissappeared!
HEEEELP plz. Sorry Neuleo if i just appended it to your original post but the symptoms are the same...

 

[neuleo]

I actually managed this with reinstalling proxmox from scratch.I did a Backup to my NAS and reimported the Machines. Worked flawlessly. Just my snapshots are gone. And it wasn't that much work either, because I leave Proxmox mostly "stock".

 

[fuztec25]

I actually managed this with reinstalling proxmox from scratch.I did a Backup to my NAS and reimported the Machines. Worked flawlessly. Just my snapshots are gone. And it wasn't that much work either, because I leave Proxmox mostly "stock".

Thank you so very much for your kind reply. Just a curiosity: which version did you reinstall?

 

[neuleo]

The newest. I'm on Proxmox 8 and it's working now

 

[fuztec25]

The newest. I'm on Proxmox 8 and it's working now

Got it! Again, thanks a lot! Merry Xmas and Happy New Year .

 

[neuleo]

Your welcome. Merry Christmas and a Happy New Year