Thanks a lot for your reply.HawaiianPi wrote: ↑Fri Jun 26, 2020 7:59 pmWhat does lsusb return with that enclosure connected?Araforn wrote: ↑Thu Jun 25, 2020 2:29 pmHowever what Im seeing as strange is that the Kingston M.2 and adaptor only boots when connected to the usb 2.0 ports!.
Of course this negates the benefit of USB booting entirely. Can anyone help me with this or perhaps indicate why it would boot only on USB2.0?.
That enclosure uses a JMicron USB-SATA bridge chip, and those are somewhat notorious for not properly supporting UAS in Linux. Assuming the output of lsusb indicates a vendor ID of 152d and device ID of 0578, then adding usb-storage.quirks=152d:0578:u to the beginning of the line in /boot/cmdline.txt (with a single space delimiter) should get you up and running from USB 3.0.
In theory, UAS can deliver up to 20% faster performance over USB 3.0, but in real life practical use it's probably less, and might not even be noticeable. However, disabling UAS will also disable TRIM, and that will definitely affect performance with time and use.
I would normally suggest the Eluteng adapter cable, but since you are using an M.2 drive that won't help you. Look for another enclosure with an ASMedia ASM1153E controller, and hope that it doesn't need a firmware update (some do, while others work out of the box, which is preferable, since firmware updates can be hard to find).
It's too bad you didn't get the 2.5" version of that SSD (less expensive, and you could use the Eluteng adapter cable).
Heres what lsusb reports.
Bus 002 Device 002: ID ab12:34cd
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 045e:075d Microsoft Corp. LifeCam Cinema
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The product ID is ab12 and vendor ID is 34cd.
Alas the quirks does not work on this adaptor so i cant use this with USB3.0 booting.
A warning for others.