03-31-2018, 06:24 AM
Are you connecting the drive via USB3?
Try connecting it to the USB2 ports and see what results you get. I've found the USB3 implementation on Linux/OVM to be very temperamental. The only thing I have found to work without an issue is my ORICO drive enclosure.
I just tried a Seagate Expansion Desktop Drive (2TB version). This is not recognise at boot, but if I flip the power off and on again to the drive, it is then recognised, can be mounted and works without issue, I do get one error thrown to the logs as follows....
When I plug it into the USB2 ports, it recognised as boot and is immediately available with no error thrown.
I have another drive enclosure which is recognised but throws lots of "xhci-hcd xhci-hcd.8.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring" errors, but I made this behave by adding a quirks option for the kernel module "options usb-storage quirks=0480:b202:u" I'm no kernel or device driver expert, but this option forces the USB driver to set the device class to "usb-storage" for USB device 0480:b202. I read a post on here suggesting you blacklist the UAS kernel module, but it did not fix the problem with that enclosure.
I'll play around a bit more with the Seagate drive over the following days to see if I can get anywhere with it.
Try connecting it to the USB2 ports and see what results you get. I've found the USB3 implementation on Linux/OVM to be very temperamental. The only thing I have found to work without an issue is my ORICO drive enclosure.
I just tried a Seagate Expansion Desktop Drive (2TB version). This is not recognise at boot, but if I flip the power off and on again to the drive, it is then recognised, can be mounted and works without issue, I do get one error thrown to the logs as follows....
Code:
[ 48.758215] usb 5-1: new SuperSpeed USB device number 2 using xhci-hcd
[ 48.770282] usb 5-1: New USB device found, idVendor=0bc2, idProduct=3321
[ 48.770311] usb 5-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 48.770332] usb 5-1: Product: Expansion Desk
[ 48.770352] usb 5-1: Manufacturer: Seagate
[ 48.770371] usb 5-1: SerialNumber: NA4KN4P8
[ 48.879816] usbcore: registered new interface driver usb-storage
[ 48.901411] scsi host0: uas
[ 48.901830] usbcore: registered new interface driver uas
[ 48.905890] scsi 0:0:0:0: Direct-Access Seagate Expansion Desk 0604 PQ: 0 ANSI: 6
[ 48.907634] sd 0:0:0:0: [sda] Spinning up disk...
[ 49.908061] .......ready
[ 55.914183] sd 0:0:0:0: [sda] 488378645 4096-byte logical blocks: (2.00 TB/1.82 TiB)
[ 55.914209] sd 0:0:0:0: [sda] 16384-byte physical blocks
[ 55.932960] sd 0:0:0:0: [sda] Write Protect is off
[ 55.932997] sd 0:0:0:0: [sda] Mode Sense: 4f 00 00 00
[ 55.933465] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 55.933658] xhci-hcd xhci-hcd.8.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 55.935075] xhci-hcd xhci-hcd.8.auto: @00000000f3866720 00000000 00000000 1b000000 01038001
[ 55.962435] sda: sda1
[ 55.965923] sd 0:0:0:0: [sda] Attached SCSI diskWhen I plug it into the USB2 ports, it recognised as boot and is immediately available with no error thrown.
I have another drive enclosure which is recognised but throws lots of "xhci-hcd xhci-hcd.8.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring" errors, but I made this behave by adding a quirks option for the kernel module "options usb-storage quirks=0480:b202:u" I'm no kernel or device driver expert, but this option forces the USB driver to set the device class to "usb-storage" for USB device 0480:b202. I read a post on here suggesting you blacklist the UAS kernel module, but it did not fix the problem with that enclosure.
I'll play around a bit more with the Seagate drive over the following days to see if I can get anywhere with it.
