[SOLVED] Voodoo mit USB-Disks

bobx

Well-Known Member
Jul 12, 2018
68
1
48
Hallo,

ich habe hier etwas Voodoo mit USB Disks am PVE (7).

Die USB-Disk steckt in einem Quickport und ist per USB mit dem Rechner verbunden. Der Quickport hat einen USB3 Anschluss, den ich am USB3 Anschluss des Rechners anschließe.

Wenn ich den Rechner starte und im Nachhinein die USB-Disk einschalte, wird sie vom System erkannt. ich kann auf die Disk zugreifen (mounten, Daten lesen/schreiben). So weit so schick. Lasse ich die Disk mit Quickport an und reboote den Rechner, dann wird die Disk erst erkannt, um danach laut Logfile (siehe unten) mit I/O errors wieder "ausgeworfen" zu werden. Die Disk wird dann auch nicht im System angezeigt (lsusb, blkid)

Mache ich das ganze am USB2-Port, dann scheint es nach dem Reboot zu klappen.

Nehme ich eine andere Disk, die ich direkt per Kabel am USB3-Port anschließe, ist es das gleiche Verhalten. Auch ein Wechsel der Steckplätze scheint nichts zu bringen.

Hat jemand eine Idee, woran das liegen kann? Evtl. nötige Einstellungen im BIOS? Aber eigentlich geht es ja ... Irgendwie Voodoo ... :confused:

Hier Auszüge aus den Logs:

Code:
Jan 10 09:59:01 prox kernel: [    2.734726] usb 4-1: New USB device found, idVendor=067b, idProduct=2773, bcdDevice= 1.00
Jan 10 09:59:01 prox kernel: [    2.734730] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 10 09:59:01 prox kernel: [    2.734732] usb 4-1: Product: Quickport Combo U3
Jan 10 09:59:01 prox kernel: [    2.734733] usb 4-1: Manufacturer: SHARKOON
Jan 10 09:59:01 prox kernel: [    2.734734] usb 4-1: SerialNumber: SHARK000000002
Jan 10 09:59:01 prox kernel: [    2.736650] usb 4-1: Set SEL for device-initiated U1 failed.
Jan 10 09:59:01 prox kernel: [    2.737031] usb 4-1: Set SEL for device-initiated U2 failed.
Jan 10 09:59:01 prox kernel: [    2.738424] usb-storage 4-1:1.0: USB Mass Storage device detected
Jan 10 09:59:01 prox kernel: [    2.738539] scsi host9: usb-storage 4-1:1.0
Jan 10 09:59:01 prox kernel: [    2.738595] usbcore: registered new interface driver usb-storage
Jan 10 09:59:01 prox kernel: [    2.738908] usbcore: registered new interface driver uas
Jan 10 09:59:01 prox kernel: [    2.781554] sd 5:0:0:0: [sdb] Attached SCSI disk
:
:
Jan 10 09:59:01 prox kernel: [    3.808228] scsi 9:0:0:0: Direct-Access     ST3000DM 001-1CH166       CC26 PQ: 0 ANSI: 0
Jan 10 09:59:01 prox kernel: [    3.808424] sd 9:0:0:0: Attached scsi generic sg3 type 0
Jan 10 09:59:01 prox kernel: [    3.808628] sd 9:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
Jan 10 09:59:01 prox kernel: [    3.809236] sd 9:0:0:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
Jan 10 09:59:01 prox kernel: [    3.809908] sd 9:0:0:0: [sdc] Write Protect is off
Jan 10 09:59:01 prox kernel: [    3.809911] sd 9:0:0:0: [sdc] Mode Sense: 03 00 00 00
Jan 10 09:59:01 prox kernel: [    3.810543] sd 9:0:0:0: [sdc] No Caching mode page found
Jan 10 09:59:01 prox kernel: [    3.810576] sd 9:0:0:0: [sdc] Assuming drive cache: write through
Jan 10 09:59:01 prox kernel: [    3.829878] sd 9:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
Jan 10 09:59:01 prox kernel: [    3.896425]  sdc: sdc1
Jan 10 09:59:01 prox kernel: [    3.911164] sd 9:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
Jan 10 09:59:01 prox kernel: [    3.913603] sd 9:0:0:0: [sdc] Attached SCSI disk
Jan 10 09:59:01 prox kernel: [    4.026761] DMAR: DRHD: handling fault status reg 2
Jan 10 09:59:01 prox kernel: [    4.026818] xhci_hcd 0000:07:00.0: WARNING: Host System Error
Jan 10 09:59:01 prox kernel: [    4.026820] DMAR: [DMA Read] Request device [07:00.0] PASID ffffffff fault addr fffa6000 [fault reason 06] PTE Read access is not set
Jan 10 09:59:01 prox kernel: [    4.026876] DMAR: [DMA Read] Request device [07:00.0] PASID ffffffff fault addr fffa6000 [fault reason 06] PTE Read access is not set
Jan 10 09:59:01 prox kernel: [    4.026928] DMAR: [DMA Read] Request device [07:00.0] PASID ffffffff fault addr fffa6000 [fault reason 06] PTE Read access is not set
Jan 10 09:59:01 prox kernel: [    4.026978] DMAR: DRHD: handling fault status reg 300
:
:
an 10 09:59:01 prox kernel: [   14.318916] Btrfs loaded, crc32c=crc32c-intel, zoned=yes
Jan 10 09:59:01 prox kernel: [   39.465496] xhci_hcd 0000:07:00.0: xHCI host not responding to stop endpoint command.
Jan 10 09:59:01 prox kernel: [   39.465514] xhci_hcd 0000:07:00.0: USBSTS: HSE EINT
Jan 10 09:59:01 prox kernel: [   39.497521] xhci_hcd 0000:07:00.0: Host halt failed, -110
Jan 10 09:59:01 prox kernel: [   39.497524] xhci_hcd 0000:07:00.0: xHCI host controller not responding, assume dead
Jan 10 09:59:01 prox kernel: [   39.497560] xhci_hcd 0000:07:00.0: HC died; cleaning up
Jan 10 09:59:01 prox kernel: [   39.497612] usb 2-1: USB disconnect, device number 2
Jan 10 09:59:01 prox kernel: [   39.497707] sd 9:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=35s
Jan 10 09:59:01 prox kernel: [   39.497712] sd 9:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 03 08 00 00 01 f8 00 00
Jan 10 09:59:01 prox kernel: [   39.497713] blk_update_request: I/O error, dev sdc, sector 776 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0
Jan 10 09:59:01 prox kernel: [   39.497838] usb 4-1: USB disconnect, device number 2
Jan 10 09:59:01 prox kernel: [   39.505467] scsi 9:0:0:0: rejecting I/O to dead device
Jan 10 09:59:01 prox kernel: [   39.505500] blk_update_request: I/O error, dev sdc, sector 776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 10 09:59:01 prox kernel: [   39.505535] Buffer I/O error on dev sdc1, logical block 520, async page read
Jan 10 09:59:01 prox kernel: [   39.505569] scsi 9:0:0:0: rejecting I/O to dead device
Jan 10 09:59:01 prox kernel: [   39.505598] blk_update_request: I/O error, dev sdc, sector 777 op 0x0:(READ) flags 0x0 phys_seg 7 prio class 0
Jan 10 09:59:01 prox kernel: [   39.505646] Buffer I/O error on dev sdc1, logical block 521, async page read
Jan 10 09:59:01 prox kernel: [   39.505682] Buffer I/O error on dev sdc1, logical block 522, async page read
Jan 10 09:59:01 prox kernel: [   39.505720] Buffer I/O error on dev sdc1, logical block 523, async page read
Jan 10 09:59:01 prox kernel: [   39.505769] Buffer I/O error on dev sdc1, logical block 524, async page read
Jan 10 09:59:01 prox kernel: [   39.505805] Buffer I/O error on dev sdc1, logical block 525, async page read
Jan 10 09:59:01 prox kernel: [   39.505841] Buffer I/O error on dev sdc1, logical block 526, async page read
Jan 10 09:59:01 prox kernel: [   39.505877] Buffer I/O error on dev sdc1, logical block 527, async page read
Jan 10 09:59:01 prox kernel: [   39.505951] Buffer I/O error on dev sdc1, logical block 520, async page read
Jan 10 09:59:01 prox kernel: [   39.505993] Buffer I/O error on dev sdc1, logical block 521, async page read
:
:

Dank und Gruß
bobx
 
Ich glaube, ich hab eine Lösung:

Das DMAR scheint der Verursacher zu sein.
Ich habe den boot kernel parameter intel_iommu=on geändert in intel_iommu=pt.
Dadurch wird DMAR wohl abgeschaltet. Das IOMMU bleibt aber erhalten.
 

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!