umbrel
umbrel copied to clipboard
Implement external disks TRIM and UAS driver
To keep disk performance in goog condition TRIM setting should be used on external (1TB) disk and UAS drive would improve preformance.
eg. USB3.0 SATA M.2 enclosure needs separate TRIM configuration.
Details here for older RPi4 https://forum.manjaro.org/t/trim-support-on-the-argon-m-2/74254/3
My RPi4B 8GB has: lsusb Bus 002 Device 002: ID 174c:1156 ASMedia Technology Inc.
and
lsusb --tree /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
Here you also see usb-storage driver is used instead of uas (UAS USB - which should be way quicker on many cases).
That enclosure seems to have a broken UAS implementation (and many others from the same 174c vendor)
So if anything it should be explicitly disabled.
usb-storage.quirks=174c:1156:u
That enclosure seems to have a broken UAS implementation (and many others from the same 174c vendor)
So if anything it should be explicitly disabled.
usb-storage.quirks=174c:1156:u
Please post
- where (link?) current Debian RPi4 version can be verified to not work with UAS.
- non-working device model of 174c:1156 ASMedia Technology Inc and
- Hardware Revision and firmware version of the device too please?
I have been using following with -Debian 11 & 12 with UAS -on Argon One M.2 SATA (contains 174c:1156 ASMedia Technology Inc) -unfor I'd need to dismantle my node to check HW Rev and FW ver. But one day I'll do it.
sudo pico /etc/udev/rules.d/98-uas-trim-scsi-unmap.rules
ACTION=="add|change", ATTRS{idVendor}=="174c", ATTRS{idProduct}=="1156", SUBSYSTEM=="scsi_disk", ATTR{provisioning_mode}="unmap"
sudo reboot
sudo fstrim -v /
sudo fstrim -v /mnt/hdd
I've been running two devices lite that over an year without a single problem. (note, I have no trim in crontab - should I ?)
So if anything it should be explicitly disabled.
usb-storage.quirks=174c:1156:u
Where above line should be placed?
You can |read the conversation/ask for more details| here, it's not my enclosure.
https://t.me/ArchLinuxARMgroup/7590
That enclosure seems to have a broken UAS implementation (and many others from the same 174c vendor)
So if anything it should be explicitly disabled.
usb-storage.quirks=174c:1156:u
Here seems to be example that it is not broken, but working. like on my devices: https://www.jeffgeerling.com/comment/30836#comment-30836