Hi David, On 21-03-16 10:08, David Webb wrote:
I am sorry but the 't' option (i.e. US_FL_NO_ATA_1X) may not be robust enough. Yesterday after leaving the system running for a few hours the usb disk would no longer connect.Today when I restarted the system with the 't' option, again the disk would not connect. I then tried repeatedly disconnecting and connecting the usb disk without restarting the system. After four failures the disk mounted correctly. I continued disconnecting and connecting the disk and it worked every time. I repeated the tests with the 'u' option after restarting the system. Amongst the output is the message: kernel: usb 2-7: UAS is blacklisted for this device, using usb-storage instead And the connection worked every time. On this basis I recommend using the flag US_FL_IGNORE_UAS as there must be some other potential conflict which is not handled by the flag US_FL_NO_ATA_1X. The change does not seem to have a large effect on the write speed - which is still of order 100 MB/s. /* Reported-by: David Webb <d...@noc.ac.uk> */ UNUSUAL_DEV(0x0bc2, 0x331a, 0x0000, 0x9999, "Seagate", "Expansion Desk", USB_SC_DEVICE, USB_PR_DEVICE, NULL, US_FL_IGNORE_UAS),
US_FL_IGNORE_UAS is a really big hammer, and there are significant performance benefits to using uas (mostly for random r/w access). Can you try again with the t quirk and when the drive fails to detect, collect error messages from "dmesg" and include these error messages in your next mail ? Thanks & Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
