Can't mount USB drive into proxmox (Ubuntu) VM

BrettR

Member
Dec 8, 2017
17
0
6
64
Hello...

I'm seeing errors when I try to mount an external USB drive into a (Ubuntu 16.04) based VM.
(Previously, this used to work..)
Current proxmox version (from pveversion tool: pve-manager 5.3-5/97ae681d )

On the proxmox console, when I run the following commands:

qm monitor 750
device_add usb-host,vendorid=0x13fe,productid=0x3100,id=usb0

The following errors appear on the (750) VM's console:

[311.2632181] sd 2:0:0:0: [sda] No Cacheing mode page found
sd 2:0:0:0: [sda] Assuming drive cache: write through
blk_update_request: I/O error, dev sda, sector 0
Buffer I/O error on dev sda, logical block 0, async page read
blk_update_request: I/O error, dev sda, sector 0
Buffer I/O error on dev sda, logical block 0, async page read
blk_update_request: I/O error, dev sda, sector 0
Buffer I/O error on dev sda, logical block 0, async page read
blk_update_request: I/O error, dev sda, sector 0
Buffer I/O error on dev sda, logical block 0, async page read
...
Dev sda: unable to read RDB block 0
blk_update_request: I/O error, dev sda, sector 0
Buffer I/O error on dev sda, logical block 0, async page read
blk_update_request: I/O error, dev sda, sector 0
Buffer I/O error on dev sda, logical block 0, async page read
...
blk_update_request: I/O error, dev sda, sector 24
Buffer I/O error on dev sda, logical block 0, async page read
blk_update_request: I/O error, dev sda, sector 0
Buffer I/O error on dev sda, logical block 0, async page read
blk_update_request: I/O error, dev sda, sector 0
Buffer I/O error on dev sda, logical block 0, async page read
...
blk_update_request: I/O error, dev sda, sector 31276928
blk_update_request: I/O error, dev sda, sector 31276928
Buffer I/O error on dev sda, logical block 3909616, async page read
blk_update_request: I/O error, dev sda, sector 31276928
Buffer I/O error on dev sda, logical block 3909616, async page read
[ 379.669965] blk_update_request: I/O error, dev sda, sector 0
--------------------------------------------------------------------------------------------------------

The following errors also appear in the /var/log/syslog of the 750 VM's host:

Mar 5 18:36:00 pmaldev systemd[1]: Starting Proxmox VE replication runner...
Mar 5 18:36:00 pmaldev systemd[1]: Started Proxmox VE replication runner.
Mar 5 18:37:00 pmaldev systemd[1]: Starting Proxmox VE replication runner...
Mar 5 18:37:00 pmaldev systemd[1]: Started Proxmox VE replication runner.
Mar 5 18:38:00 pmaldev systemd[1]: Starting Proxmox VE replication runner...
Mar 5 18:38:00 pmaldev systemd[1]: Started Proxmox VE replication runner.
Mar 5 18:39:00 pmaldev systemd[1]: Starting Proxmox VE replication runner...
Mar 5 18:39:00 pmaldev systemd[1]: Started Proxmox VE replication runner.
Mar 5 18:39:37 pmaldev systemd[1]: Started Session 929 of user root.
Mar 5 18:40:00 pmaldev systemd[1]: Starting Proxmox VE replication runner...
Mar 5 18:40:00 pmaldev systemd[1]: Started Proxmox VE replication runner.
Mar 5 18:40:26 pmaldev kernel: [3127985.532120] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:26 pmaldev kernel: [3127985.880056] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:27 pmaldev kernel: [3127987.324117] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:28 pmaldev kernel: [3127987.672054] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:28 pmaldev kernel: [3127988.052107] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:29 pmaldev kernel: [3127988.400116] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:29 pmaldev kernel: [3127988.780054] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:29 pmaldev kernel: [3127989.128112] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:30 pmaldev kernel: [3127989.508110] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:30 pmaldev kernel: [3127989.856055] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:30 pmaldev kernel: [3127990.236108] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:31 pmaldev kernel: [3127990.584057] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:31 pmaldev kernel: [3127990.964063] usb 3-6: reset high-speed USB device number 6 using
...

Mar 5 18:40:59 pmaldev kernel: [3128018.608112] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:59 pmaldev kernel: [3128018.956117] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:40:59 pmaldev kernel: [3128019.336108] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:41:00 pmaldev systemd[1]: Starting Proxmox VE replication runner...
Mar 5 18:41:00 pmaldev kernel: [3128019.684085] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:41:00 pmaldev systemd[1]: Started Proxmox VE replication runner.
Mar 5 18:41:00 pmaldev kernel: [3128020.064108] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:41:01 pmaldev kernel: [3128020.412053] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:41:01 pmaldev kernel: [3128020.792083] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:41:01 pmaldev kernel: [3128021.140079] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:41:02 pmaldev kernel: [3128021.520095] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:41:02 pmaldev kernel: [3128021.868073] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:41:02 pmaldev kernel: [3128022.248054] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:41:03 pmaldev kernel: [3128022.600086] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:41:03 pmaldev kernel: [3128022.980103] usb 3-6: reset high-speed USB device number 6 using xhci_hcd
Mar 5 18:41:03 pmaldev kernel: [3128023.328105] usb 3-6: reset high-speed USB device number 6 using xhci_hcd

_hcd
-------------------------------------------------------------------------------------------------------------------------

Thanks in advance!

--Brett R.

...
2,1 Top
 
blk_update_request: I/O error, dev sda, sector 0
sounds like a broken usb drive?

did you try a different one?
are you sure the host is not accessing the usb drive?
 
Hello.

I don't think that I have a broken USB drive..since the drive works correctly on other hosts.

I tried another (larger, Seagate) USB drive ..and saw the same type of errors (see listing below).

Also, the drive is not mounted/accessed on the proxmox server host (The proxmox server host
device name../dev/sdc1 disappears..when I run the 'qm monitor' 'device_add' command..to move
the device into the LinuxVM.)

Error listing from 2nd USB Drive Mount Attempt
----------------------------------------------------------------
Dev sda: unable to read RDB block 0
blk_update_request: I/O error, dev sda, sector 1953524992
blk_update_request: I/O error, dev sda, sector 1953524992
Buffer I/O error on dev sda, logical block 1953524992, async page read
blk_update_request: I/O error, dev sda, sector 1953524993
Buffer I/O error on dev sda, logical block 1953524993, async page read
blk_update_request: I/O error, dev sda, sector 1953524994
Buffer I/O error on dev sda, logical block 1953524994, async page read
Buffer I/O error on dev sda, logical block 1953524995, async page read
---------------------------------------------------------------------

Here is a portion of the 'dmesg' command output:
------------------------------------------------------------------
[70425.041492] usb 1-2.3: Product: Backup+ BK
[70425.041493] usb 1-2.3: Manufacturer: Seagate
[70425.041494] usb 1-2.3: SerialNumber: NA51G3Y6
[70425.042687] usb-storage 1-2.3:1.0: USB Mass Storage device detected
[70425.042776] usb-storage 1-2.3:1.0: Quirks match for vid 0bc2 pid a013:
2000000
[70425.042785] scsi host4: usb-storage 1-2.3:1.0
[70426.047194] scsi 4:0:0:0: Direct-Access Seagate Backup+ BK
0409 PQ: 0 ANSI: 6
[70426.048791] sd 4:0:0:0: Attached scsi generic sg1 type 0
[70426.054597] sd 4:0:0:0: [sda] 1953525167 512-byte logical blocks: (1.00
TB/932 GiB)
[70426.059849] sd 4:0:0:0: [sda] Test WP failed, assume Write Enabled
[70426.065011] sd 4:0:0:0: [sda] Cache data unavailable
[70426.065013] sd 4:0:0:0: [sda] Assuming drive cache: write through
[70426.083970] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.083973] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.083975] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.083977] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 00 00
00 01 00
[70426.083987] blk_update_request: critical target error, dev sda, sector
0
[70426.084244] Buffer I/O error on dev sda, logical block 0, async page
read
[70426.087034] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.087036] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.087038] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.087039] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 01 00
00 01 00
[70426.087041] blk_update_request: critical target error, dev sda, sector
1
[70426.087289] Buffer I/O error on dev sda, logical block 1, async page
read
[70426.090277] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.090283] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.090287] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.090291] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 02 00
00 01 00
[70426.090294] blk_update_request: critical target error, dev sda, sector
2
[70426.090651] Buffer I/O error on dev sda, logical block 2, async page
read
[70426.093410] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.093416] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.093421] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.093425] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 03 00
00 01 00
[70426.093428] blk_update_request: critical target error, dev sda, sector
3
[70426.093857] Buffer I/O error on dev sda, logical block 3, async page
read
[70426.096455] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.096457] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.096459] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.096461] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 04 00
00 01 00
[70426.096462] blk_update_request: critical target error, dev sda, sector
4
[70426.096798] Buffer I/O error on dev sda, logical block 4, async page
read
[70426.099621] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.099624] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.099626] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.099627] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 05 00
00 01 00
[70426.099628] blk_update_request: critical target error, dev sda, sector
5
[70426.100000] Buffer I/O error on dev sda, logical block 5, async page
read
[70426.102702] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.102704] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.102710] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.102712] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 06 00
00 01 00
[70426.102713] blk_update_request: critical target error, dev sda, sector
6
[70426.103106] Buffer I/O error on dev sda, logical block 6, async page
read
[70426.106516] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.106519] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.106521] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.106523] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 07 00
00 01 00
[70426.106524] blk_update_request: critical target error, dev sda, sector
7
[70426.107354] Buffer I/O error on dev sda, logical block 7, async page
read
[70426.111861] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70426.111868] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70426.111872] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70426.111876] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 00 00
00 01 00
[70426.111880] blk_update_request: critical target error, dev sda, sector
0
[70426.112454] Buffer I/O error on dev sda, logical block 0, async page
read
[70426.116993] Buffer I/O error on dev sda, logical block 1, async page
read
[70426.161596] ldm_validate_partition_table(): Disk read failed.
[70426.262292] Dev sda: unable to read RDB block 0
[70426.390529] sda: unable to read partition table
[70426.761963] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70427.498033] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70428.630026] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70429.398021] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70430.162023] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70430.926022] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70431.694019] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70432.075590] scsi_io_completion: 87 callbacks suppressed
[70432.075596] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_OK
[70432.075599] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 74 70 6d 00 00
00 08 00
[70432.075600] blk_update_request: 87 callbacks suppressed
[70432.075601] blk_update_request: I/O error, dev sda, sector 1953524992
[70432.086912] sd 4:0:0:0: [sda] Attached SCSI disk
[70432.113567] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[70432.113574] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request
[current]
[70432.113579] sd 4:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[70432.113583] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 74 70 6d 00 00
00 01 00
[70432.113586] blk_update_request: critical target error, dev sda, sector
1953524992
[70432.114546] buffer_io_error: 86 callbacks suppressed
[70432.114548] Buffer I/O error on dev sda, logical block 1953524992,
async page read
[70432.466022] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70433.234024] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70434.002033] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70434.766002] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70435.530021] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70436.297997] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70436.679903] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_OK
[70436.679907] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 74 70 6d 01 00
00 07 00
[70436.679908] blk_update_request: I/O error, dev sda, sector 1953524993
[70436.680842] Buffer I/O error on dev sda, logical block 1953524993,
async page read
[70436.681466] Buffer I/O error on dev sda, logical block 1953524994,
async page read
[70436.682110] Buffer I/O error on dev sda, logical block 1953524995,
async page read
[70436.682741] Buffer I/O error on dev sda, logical block 1953524996,
async page read
[70436.683364] Buffer I/O error on dev sda, logical block 1953524997,
async page read
[70436.684018] Buffer I/O error on dev sda, logical block 1953524998,
async page read
[70436.684657] Buffer I/O error on dev sda, logical block 1953524999,
async page read
[70437.066021] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70437.809977] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70438.549980] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70439.290028] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70440.034027] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70440.774020] usb 1-2.3: reset full-speed USB device number 6 using
uhci_hcd
[70441.155521] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_OK
[70441.155524] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 74 70 6d 00 00
00 01 00
[70441.155525] blk_update_request: I/O error, dev sda, sector 1953524992
[70441.156491] Buffer I/O error on dev sda, logical block 1953524992,
async page read
--------------------------------------------------------------------------------------------------

Some additional details...
When I used to mount drives successfully into a VM, the device name would
appear as 'sda1' (and not 'sda')


-----------------------------------------------------------------------------------------------------

*** OK, I think that I've figured out the source of the problem... ***

The Linux VM (vmid=750) is only able to detect USB 1.1 USB controller hardware..
but the mounted USB drives are USB 2.0 and USB 3.0 type drives. (which are much
faster than the USB 1.1 interface.)

Here is a portion of the Linux VM's dmesg output:
------------------------------------------------------------------
[ 0.851909] PPP generic driver version 2.4.2
[ 0.855959] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.856591] ehci-pci: EHCI PCI platform driver
[ 0.857214] ehci-platform: EHCI generic platform driver
[ 0.857832] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.858446] ohci-pci: OHCI PCI platform driver
[ 0.859053] ohci-platform: OHCI generic platform driver
[ 0.859663] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.890410] uhci_hcd 0000:00:01.2: UHCI Host Controller
[ 0.891056] uhci_hcd 0000:00:01.2: new USB bus registered, assigned bus
number 1
[ 0.895910] uhci_hcd 0000:00:01.2: detected 2 ports
[ 0.896629] uhci_hcd 0000:00:01.2: irq 11, io base 0x0000e0c0
[ 0.897301] usb usb1: New USB device found, idVendor=1d6b,
idProduct=0001
[ 0.897911] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 0.898514] usb usb1: Product: UHCI Host Controller
[ 0.899103] usb usb1: Manufacturer: Linux 4.4.0-62-generic uhci_hcd
[ 0.899708] usb usb1: SerialNumber: 0000:00:01.2
[ 0.903950] hub 1-0:1.0: USB hub found
[ 0.904552] hub 1-0:1.0: 2 ports detected
[ 0.905249] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at
0x60,0x64 irq 1,12
[ 0.906565] serio: i8042 KBD port at 0x60,0x64 irq 1
-----------------------------------------------------------------------------

The ehci-pci drivers (i.e. USB 2.0) are present...but the VM never sees an ehci-pci
USB controller.

The VM 'does find' a UHCI (i.e. USB 1.1) USB controller. The following dmesg lines
illustrate this:
[ 0.897301] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[ 0.898514] usb usb1: Product: UHCI Host Controller
[ 0.899103] usb usb1: Manufacturer: Linux 4.4.0-62-generic uhci_hcd

--------------------------------------------------------------------------------------------------------------

Now, here's some 'dmesg' output from my proxmox ve server (that manages the Linux
VM:

[ 0.972902] PPP generic driver version 2.4.2
[ 0.972929] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.972931] ehci-pci: EHCI PCI platform driver
[ 0.973073] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 0.973079] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 0.973088] ehci-pci 0000:00:1a.0: debug port 2
[ 0.976980] ehci-pci 0000:00:1a.0: cache line size of 32 is not supported
[ 0.976990] ehci-pci 0000:00:1a.0: irq 18, io mem 0x91e13000
[ 0.992058] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 0.992118] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.992121] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.992124] usb usb1: Product: EHCI Host Controller
[ 0.992126] usb usb1: Manufacturer: Linux 4.15.18-9-pve ehci_hcd
[ 0.992128] usb usb1: SerialNumber: 0000:00:1a.0
[ 0.992344] hub 1-0:1.0: USB hub found
[ 0.992348] hub 1-0:1.0: 2 ports detected
[ 0.992569] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 0.992574] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 0.992583] ehci-pci 0000:00:1d.0: debug port 2
[ 0.996481] ehci-pci 0000:00:1d.0: cache line size of 32 is not supported
[ 0.996484] ehci-pci 0000:00:1d.0: irq 18, io mem 0x91e12000
[ 1.012056] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 1.012118] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.012121] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.012124] usb usb2: Product: EHCI Host Controller
[ 1.012126] usb usb2: Manufacturer: Linux 4.15.18-9-pve ehci_hcd
[ 1.012129] usb usb2: SerialNumber: 0000:00:1d.0
[ 1.012305] hub 2-0:1.0: USB hub found
[ 1.012308] hub 2-0:1.0: 2 ports detected
[ 1.012441] ehci-platform: EHCI generic platform driver
[ 1.012447] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.012449] ohci-pci: OHCI PCI platform driver
[ 1.012458] ohci-platform: OHCI generic platform driver
[ 1.012464] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.012584] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 1.012588] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[ 1.013657] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x00009810
[ 1.013661] xhci_hcd 0000:00:14.0: cache line size of 32 is not supported
[ 1.013740] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.013741] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.013742] usb usb3: Product: xHCI Host Controller
[ 1.013743] usb usb3: Manufacturer: Linux 4.15.18-9-pve xhci-hcd
[ 1.013744] usb usb3: SerialNumber: 0000:00:14.0
[ 1.013844] hub 3-0:1.0: USB hub found
[ 1.013859] hub 3-0:1.0: 15 ports detected
[ 1.014998] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 1.015001] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
[ 1.015003] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
[ 1.015030] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[ 1.015031] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.015032] usb usb4: Product: xHCI Host Controller
[ 1.015033] usb usb4: Manufacturer: Linux 4.15.18-9-pve xhci-hcd
[ 1.015034] usb usb4: SerialNumber: 0000:00:14.0
[ 1.015226] hub 4-0:1.0: USB hub found
[ 1.015237] hub 4-0:1.0: 6 ports detected
[ 1.015881] i8042: PNP: No PS/2 controller found.
[ 1.015955] mousedev: PS/2 mouse device common for all mice
[ 1.016031] rtc_cmos 00:00: RTC can wake from S4
-------------------------------------------------------------------------------------------------------------------

The following USB controllers are found on the proxmox ve server:

[ 0.992124] usb usb1: Product: EHCI Host Controller (i.e. USB 2.0)
[ 1.013742] usb usb3: Product: xHCI Host Controller (i.e. USB 3.0)

---------------------------------------------------------------------------------------------------

So, what do I have to do...to the Linux VM ..to get it to see
the proxmox server's EHCI or xHCI Host Controller hardware ?

If the VM could see either of those USB Host Controllers...it could communicate with
the mounted USB 2.0, or USB 3.0 mounted drives.

Thanks!

--Brett R

P.S. I may have created my Linux VM..from a proxmox template .ISO file..for Ubuntu 16.04 LTS
Could some USB controller drivers be missing from that .ISO file?
 
did you try with setting usb3 to 1?

e.g.:

Code:
usb0: host=1234:5678,usb3=1
?
 
I had not...
Thank you, this actually worked for 'static USB drive' mounting. :)

Is there any way to pass the 'usb3=' type parameter to proxmox, when performing a dynamic
VM mount? e.g.
qm monitor 750
device_add usb-host,vendorid=0x13fe,productid=0x3100,id=usb0

Thanks!

Brett R
 
Hi Dominik.

I tried the following for my USB 2.0 Patriot Memory key (Speed 480 Mb/s; See speed value below.)

[root][/mnt/data/images/702]# qm monitor 750
Entering Qemu Monitor for VM 750 - type 'help' for help
qm> info usbhost
Bus 3, Addr 8, Port 6, Speed 480 Mb/s
Class 00: USB device 13fe:3100, Patriot Memory
Bus 3, Addr 2, Port 2, Speed 1.5 Mb/s
Class 00: USB device 14dd:1007, D2CIM-DVUSB
qm> device_add usb-host,bus=ehci.0,vendorid=0x13fe,productid=0x3100,id=usb0
Bus 'ehci.0' not found
qm> device_add usb-host,bus=xhci.0,vendorid=0x13fe,productid=0x3100,id=usb0
Bus 'xhci.0' not found
qm>

Any ideas..on what I'm doing incorrectly?

Thanks,

Brett R.
 
the vm has no usb controller ... you have to first add it, see the link i posted previously
 
Understood.

So, from the link that you previously sent...I would need to add a line like the following to my VM 750.conf
configuration file..correct?

args: -device nec-usb-xhci,id=xhci,addr=0x1b,bus=pci.1 -device usb-host,bus=xhci.0,vendorid=0x0480,productid=0xa007

The above line would only work for the 'nec usb' drive..with: vendorid=0x0480,productid=0xa007 .. correct?

Will I have to add a 'vendorid (and productid) specific entry for each USB key that might be dynamically mounted into the VM?

Or, is their a 'generic' entry that can be added to the VM's .conf file..to support an xhci bus?

Thanks!

Brett
 
-device nec-usb-xhci,id=xhci,addr=0x1b,bus=pci.1
this part is the usb3 controller (which provides the xhci bus) and you can add this via device_add via the monitor (described in the link)
it is already added if you have at least one usb3 device in the config (usbX: foo:bar,usb3=1)
 
I had the same errors, fixed them with the proxmox wiki article: https://pve.proxmox.com/wiki/USB_Devices_in_Virtual_Machines.

Simple Way: pass the USB device ID to the guest​

Assigning an Alcor memory stick connected to the host to VM 804.

Figure out in the host the Device Type by

lsusb | grep Alcor

The result is

Bus 002 Device 013: ID 058f:6387 Alcor Micro Corp. Flash Drive

Assign it to the VM by

qm set 804 -usb0 host=058f:6387

Shutdown the VM (if running) and start it again.


No problems now,

Edit: spoke too soon, it is still failing.

Dec 27 00:18:27 pve kernel: usb 4-2: USB disconnect, device number 8
Dec 27 00:18:44 pve kernel: usb 4-2: new SuperSpeed USB device number 9 using xhci_hcd
Dec 27 00:18:44 pve kernel: usb 4-2: New USB device found, idVendor=1058, idProduct=2620, bcdDevice=10.20
Dec 27 00:18:44 pve kernel: usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 27 00:18:44 pve kernel: usb 4-2: Product: Elements 2620
Dec 27 00:18:44 pve kernel: usb 4-2: Manufacturer: Western Digital
Dec 27 00:18:44 pve kernel: usb 4-2: SerialNumber: 575845324531313538335753
Dec 27 00:18:44 pve kernel: usb-storage 4-2:1.0: USB Mass Storage device detected
Dec 27 00:18:44 pve kernel: scsi host12: usb-storage 4-2:1.0
Dec 27 00:18:45 pve kernel: usb 4-2: reset SuperSpeed USB device number 9 using xhci_hcd
Dec 27 00:19:14 pve kernel: usb 4-2: USB disconnect, device number 9
Dec 27 00:19:14 pve kernel: xhci_hcd 0000:00:10.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 27 00:19:14 pve QEMU[2659679]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Dec 27 00:19:31 pve kernel: usb 4-2: new SuperSpeed USB device number 10 using xhci_hcd
Dec 27 00:19:31 pve kernel: usb 4-2: New USB device found, idVendor=1058, idProduct=2620, bcdDevice=10.20
Dec 27 00:19:31 pve kernel: usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 27 00:19:31 pve kernel: usb 4-2: Product: Elements 2620
Dec 27 00:19:31 pve kernel: usb 4-2: Manufacturer: Western Digital
Dec 27 00:19:31 pve kernel: usb 4-2: SerialNumber: 575845324531313538335753
Dec 27 00:19:31 pve kernel: usb-storage 4-2:1.0: USB Mass Storage device detected
Dec 27 00:19:31 pve kernel: scsi host12: usb-storage 4-2:1.0
Dec 27 00:19:32 pve kernel: usb 4-2: reset SuperSpeed USB device number 10 using xhci_hcd
Dec 27 00:19:56 pve kernel: usb 4-2: USB disconnect, device number 10
Dec 27 00:19:58 pve QEMU[2659679]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Dec 27 00:20:13 pve kernel: usb 4-2: new SuperSpeed USB device number 11 using xhci_hcd
Dec 27 00:20:13 pve kernel: usb 4-2: New USB device found, idVendor=1058, idProduct=2620, bcdDevice=10.20
Dec 27 00:20:13 pve kernel: usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 27 00:20:13 pve kernel: usb 4-2: Product: Elements 2620
Dec 27 00:20:13 pve kernel: usb 4-2: Manufacturer: Western Digital
Dec 27 00:20:13 pve kernel: usb 4-2: SerialNumber: 575845324531313538335753
Dec 27 00:20:13 pve kernel: usb-storage 4-2:1.0: USB Mass Storage device detected
Dec 27 00:20:13 pve kernel: scsi host12: usb-storage 4-2:1.0
Dec 27 00:20:14 pve kernel: usb 4-2: reset SuperSpeed USB device number 11 using xhci_hcd
Dec 27 00:20:46 pve kernel: usb 4-2: USB disconnect, device number 11
Dec 27 00:20:46 pve QEMU[2659679]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Dec 27 00:21:04 pve kernel: usb 4-2: new SuperSpeed USB device number 12 using xhci_hcd
Dec 27 00:21:04 pve kernel: usb 4-2: New USB device found, idVendor=1058, idProduct=2620, bcdDevice=10.20
Dec 27 00:21:04 pve kernel: usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 27 00:21:04 pve kernel: usb 4-2: Product: Elements 2620
Dec 27 00:21:04 pve kernel: usb 4-2: Manufacturer: Western Digital
Dec 27 00:21:04 pve kernel: usb 4-2: SerialNumber: 575845324531313538335753
Dec 27 00:21:04 pve kernel: usb-storage 4-2:1.0: USB Mass Storage device detected
Dec 27 00:21:04 pve kernel: scsi host12: usb-storage 4-2:1.0
Dec 27 00:21:04 pve kernel: usb 4-2: reset SuperSpeed USB device number 12 using xhci_hcd
Dec 27 00:21:25 pve pvedaemon[2695835]: <root@pam> successful auth for user 'root@pam'
Dec 27 00:21:26 pve kernel: usb 4-2: USB disconnect, device number 12
Dec 27 00:21:28 pve QEMU[2659679]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Dec 27 00:21:43 pve kernel: usb 4-2: new SuperSpeed USB device number 13 using xhci_hcd
Dec 27 00:21:43 pve kernel: usb 4-2: New USB device found, idVendor=1058, idProduct=2620, bcdDevice=10.20
Dec 27 00:21:43 pve kernel: usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 27 00:21:44 pve kernel: usb 4-2: Product: Elements 2620
Dec 27 00:21:44 pve kernel: usb 4-2: Manufacturer: Western Digital
Dec 27 00:21:44 pve kernel: usb 4-2: SerialNumber: 575845324531313538335753
Dec 27 00:21:44 pve kernel: usb-storage 4-2:1.0: USB Mass Storage device detected
Dec 27 00:21:44 pve kernel: scsi host12: usb-storage 4-2:1.0
Dec 27 00:21:44 pve kernel: usb 4-2: reset SuperSpeed USB device number 13 using xhci_hcd
Dec 27 00:22:15 pve kernel: usb 4-2: USB disconnect, device number 13

It happens with big files. I have already changed the usb cable. VM is Openmediavault.
I will try your other suggestions.
 
Last edited:

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!