Hi, I am facing a related bug. I am using an SSD enclosure utilizing the ASM1352R controller as well. This controller supports RAID-0, RAID-1 and other configurations with up to two SSDs, and I'm currently using it with only one SSD; the product advertises as ASM1352R-Safe in this configuration, which is also what it advertises as when in RAID-1. I am running Debian buster.
The advertised product IDs and serial, etc. are all different for me. Nevertheless, the bug still remains, and the fix proposed by OP works. OP mentioned "With/without UAS the issue persisted". I suspect that OP might be confused and does not realize that the fix he proposes is responsible for the message "UAS is blacklisted for this device, using usb-storage instead"; the quirk he used disables UAS support from the kernel side. Nevertheless, fix OP proposes is not a universal fix. ASMedia, reputable hardware manufacturer that it is, manufactures multiple chips with different architectures and capabilities under the same vendorId:productId identifier. Blacklisting this identifier will blacklist all its controllers, which may not exactly be a bad thing as multiple other models have issues with UAS under Linux as well. Inspection of latest upstream source seems that it is not handled upstream, though I have not tried running it. I'd be happy to contribute however I can but I have my hands tied if you need more info: I'm running Debian buster, and I'm running the controller with only one SSD. Nevertheless, it seems to me that this is an upstream bug and not Ubuntu-kernel specific. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742318 Title: USB-Storage Quirk for 174c:1356 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs