Hello,
I see the a daily cronjob that is nicely trying to do fstrim.
Though, I don’t seem to be able to get it to work with USB connected SSDs (probably same with “shingled” SMR disks) that support it when connected to other machines. I could only find out that there does not seem to be a “uas” kernel module.
lsusb -t does not show the uas driver for the device, and modprobe uas fails.
Is it maybe available somehow or somewhere?
I had a look in the source code for the kernel setup for IPFire and CONFIG_USB_UAS=y is defined for x86_64 and i586. The y means that the module is not only installed but loaded as standard.
modinfo uas shows it as builtin on my x86_64 system.
If you are using an arm or aarch64 system then CONFIG_USB_UAS is not set so the module is not installed.
It seems that the lsusb -t shows you what your usb storage is capable of supporting. It should show uas if it can support uas otherwise it will show usb-storage in which case I believe it doesn’t support uas even if the module was available.
In terms of having the uas module in aarch64, I have no idea if it is possible.
Usually, if the modules are present in some architectures and not in others it is an indication that there are some issues with that module in those architectures. One of the IPFire devs would need to comment on that.
Thank you for explaining, hopefully a dev can shed some light on this.
The USB enclosure and SSD lists and works with UAS when connected to the desktop.
[Edit: And blkdiscard was able to reset the SSD before flashing the ipfire image.]
Reason:
A lot of Core Developers read in this community somehow irregular (although there are some very busy readers like Peter Mueller). This has nothing to do with ignorance just with a lake of time. We cannot monitor a handful of platforms for important information and so important information like the one which you posted here gets somehow lost.
Therefore please post this information in a bug report, that it gets recognized.