matmat07 Posted February 1, 2020 Share Posted February 1, 2020 (edited) Hi, I am having some issue with my new and first build. I have this VL805 PCIe card with 4 USB3 port that gets recognized by Unraid, but I can't mount the usb drive and stick plugged in. I am not trying to pass them through a VM. The stick was just a test and the drive will be the parity one, once I remove it from it's case and after I've made sure it will work as such. root@Tower:~# lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 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 003: ID 058f:6387 Alcor Micro Corp. Flash Drive Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 05dc:a81d Lexar Media, Inc. LJDTT16G [JumpDrive 16GB] Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@Tower:~# lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/Ivy Bridge DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 05) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation C204 Chipset LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port Desktop SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 980] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1) 02:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) 03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 04:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a) Log for the USB stick : Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] 31457280 512-byte logical blocks: (16.1 GB/15.0 GiB) Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] Write Protect is off Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] Mode Sense: 23 00 00 00 Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Feb 1 10:26:08 Tower kernel: sdb: sdb1 Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] Attached SCSI removable disk Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=0x00 Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00 Feb 1 10:26:08 Tower kernel: print_req_error: I/O error, dev sdb, sector 0 Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00 Feb 1 10:26:08 Tower kernel: print_req_error: I/O error, dev sdb, sector 0 Feb 1 10:26:08 Tower kernel: Buffer I/O error on dev sdb, logical block 0, async page read tower-diagnostics-20200201-1033.zip Edited February 2, 2020 by matmat07 Solved Quote Link to comment
JorgeB Posted February 2, 2020 Share Posted February 2, 2020 Very bad idea to use USB for array devices, especially one with a VIA chipset: Feb 1 10:26:08 Tower kernel: usb 3-1-port1: Cannot enable. Maybe the USB cable is bad? Feb 1 10:26:08 Tower kernel: usb 3-1-port1: cannot disable (err = -22) Feb 1 10:26:08 Tower kernel: usb 3-1-port1: cannot reset (err = -22) ### [PREVIOUS LINE REPEATED 4 TIMES] ### Feb 1 10:26:08 Tower kernel: usb 3-1-port1: Cannot enable. Maybe the USB cable is bad? Feb 1 10:26:08 Tower kernel: usb 3-1-port1: cannot disable (err = -22) ### [PREVIOUS LINE REPEATED 1 TIMES] ### Feb 1 10:26:08 Tower kernel: hub 3-1:1.0: hub_ext_port_status failed (err = -22) Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=0x00 Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00 Feb 1 10:26:08 Tower kernel: print_req_error: I/O error, dev sdb, sector 0 Feb 1 10:26:08 Tower kernel: usb 4-3: USB disconnect, device number 2 Feb 1 10:26:08 Tower kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Feb 1 10:26:08 Tower kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Feb 1 10:26:08 Tower kernel: usb usb4-port3: couldn't allocate usb_device Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 Feb 1 10:26:08 Tower kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00 Feb 1 10:26:08 Tower kernel: print_req_error: I/O error, dev sdb, sector 0 Feb 1 10:26:08 Tower kernel: Buffer I/O error on dev sdb, logical block 0, async page read Use SATA, but if really need USB then at least use a controller with a better chipset, like NEC or Asmedia. Quote Link to comment
matmat07 Posted February 2, 2020 Author Share Posted February 2, 2020 Thanks you tee-tee jorge. I will try to look around now that I have a bit more info on what went wrong. But yes, I will definitely need USB 3 at some point, and that board doesn't have any. Quote Link to comment
matmat07 Posted February 9, 2020 Author Share Posted February 9, 2020 In case someone else stumble upon this, a BIOS update seems to have solved the issue. Or maybe clearing the CMOS did. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.