Hello, On 2020-08-18 10:57, Alan Stern wrote: > Somehow that commit is causing usb-storage to go crazy. You're going > to have to do some debugging to find out why. > > Here's what to look for in drivers/usb/storage/usb.c: > > Is storage_probe() getting called at all? Yes. > > If it is, it doesn't seem to get as far as calling > usb_stor_probe1(). Can you find out where it goes off the > rails and why? Yes. I added a bunch of calls to printk[1] and noticed the following new lines in dmesg: [Fri Aug 21 23:02:42 2020] [+] Entering storage_probe [Fri Aug 21 23:02:42 2020] [+] Using uas driver So basically, the kernel realizes that UAS cannot be used, tries to use usb-storage instead, and then usb-storage says "well, this device should be using UAS, I'm not going to handle it". Somehow, we forget that UAS is broken for this device along the way. I commented out the call to uas_use_uas_driver()[2] and was able to see my partitions, mount them, read and write data. Everything works as expected. Do you have any idea why usb-storage may be led to believe UAS is suitable for this enclosure? Cyril [1] https://framagit.org/Steap/linux/-/commit/f70143e30fb1ca5f3ce7476ce6d51354786c72c9 [2] https://framagit.org/Steap/linux/-/commit/22b3a6ae411bc9fa98d3c81045308ce83f144b14
