Boot loop with certain Sata to USB adaptors

Solution 1:

So after some more testing, I did get this to boot. Seams that simply blacklisting the uas module breaks boot. However adding usb-storage.quirks=<device-id> to the kernel cmd line, which also forces it to use normal usb storage module, fixes the problem.

At least this way I can use the DeLock controller, but it does not really provide much of an answer to the problems. Why does a quirks option on usb-storage work rather than blacklisting uas? And why does uas fail to begin with? Why does the USB-3.1 Hama controller not use uas but the USB-3.0 from DeLock do, and how can one make sure what uses what before buying these products?

EDIT:
Further testing shows that the Hama product already has a quirks match within the usb-storage module, which explains why it simply works out-of-box. Not sure what the point is with uas then, taken into account that products that are built for it, only works with this feature disabled.