TLDR; If you are using this sabrent ssd enclosure you might need to tweak a boot file to fix boot from USB 3 and overall speed degradation. Please read through this post You need to add this to the start of
/boot/cmdline.txt after finding your product and vendor ID (aaaa:bbbb).
I recently migrated from HassOS to a self managed containerized setup, I did this because I wanted to utilize the new boot from USB and remove the SD card completely. At the time of wiriting this HassOS does not support the new Raspberry Pi 4 boot, from my research it looks to be like a upstream issue with Buildroot and their implementation of U-Boot, though I am not an OS person and only poked around a few days so please correct me. I noticed some random sluggishness and also would hang on boot/fail to boot over USB3. Booting from USB2 was ok, but still sluggish once booted. I would also see this in the boot logs
EXT4-fs error (device /dev/sda2): ext4_find_entry:1463
EDIT: The above info is still valid and will get the device working as a USB mass storage device but does not use the UAS drivers which is needed to achieve full throughput. There is a firmware update for the device that allows the adapter to be used WITHOUT applying the quirks and gives UAS driver support. Sabrent UASP Firmware Update I used this tool via a Windows VM and then removed the quirks from the
cmdline.txt file and it booted just fine and then showed UAS drivers
pi at HomeAssistant in ~ ➜ lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M