Hi There,
What file system is Umbrel using? I only see it mounted as bind
I am asking, as I want to know how suitable is it for SSD’s, or do I need to
make some changes (eg TRIM ) to increase lifespan on the device …
At the moment I have Umbrel installed on a Samsung 850 evo SSD connected to USB3 via a Transcend (ASM1051) bridge to a RPI5, performance wise it is a great combo.
Thanks
I played around with lsblk and found it is ext4:
lsblk -o FSTYPE,MOUNTPOINT
FSTYPE MOUNTPOINT
vfat /run/rugpi/mounts/config
vfat /boot
ext4 /run/rugpi/mounts/system
ext4 /run/rugpi/mounts/data
Still have no idea how to turn on TRIM for thex ext4 partitions with this setup …
Personally, I don’t understand the benefit of what you want to do.
It’s true. A solid state drive gets worn out by write actions. Especially older SSD generations were vulnerable in that regard, but to a (much) lesser degree, that’s still the case for newer SSD generations.
Within reason, because a modern SSD is already pretty resistant to wear and tear by default.
TRIM cleaning action is recommended for good long-term performance of an SSD. Otherwise, it might become slow after a while.
This is true even for new SSDs: although new SSDs today usually have some kind of garbage collection built into their firmware, it’s always better to run a regular TRIM as well.
Unless your SSD is from before 2010, they usually don’t support TRIM.
Anyway, umbrelOS is based on Debian. It runs on Debian and it already takes care of all that work. In fact, if you want to confirm it, log into umbrelOS via SSH and use the following command which will show you the settings Debian uses for TRIM.
systemctl cat fstrim.timer
And while you’re there, check how many times it has done this.
journalctl | grep fstrim.service
Also, any changes you make will be wiped out by the next umbrelOS update that is applied. That’s how it is, at least for now.
Anyway, I don’t know… Why bother? Why fix it if it works?
Perfect, that’s what I wanted to know. I just wanted to confirm that something had been done to enable TRIM on the SSD – so I don’t need to do anthing more, great!
sudo journalctl | grep fstrim.service
[sudo] password for umbrel:
Jan 14 23:08:36 umbrel systemd[1]: Starting fstrim.service - Discard unused blocks on filesystems from /etc/fstab...
Jan 14 23:08:36 umbrel systemd[1]: fstrim.service: Deactivated successfully.
Jan 14 23:08:36 umbrel systemd[1]: Finished fstrim.service - Discard unused blocks on filesystems from /etc/fstab.
Jan 20 01:00:25 umbrel systemd[1]: Starting fstrim.service - Discard unused blocks on filesystems from /etc/fstab...
Jan 20 01:00:25 umbrel systemd[1]: fstrim.service: Deactivated successfully.
Jan 20 01:00:25 umbrel systemd[1]: Finished fstrim.service - Discard unused blocks on filesystems from /etc/fstab.
Jan 27 00:34:15 umbrel systemd[1]: Starting fstrim.service - Discard unused blocks on filesystems from /etc/fstab...
Jan 27 00:34:15 umbrel systemd[1]: fstrim.service: Deactivated successfully.
Jan 27 00:34:15 umbrel systemd[1]: Finished fstrim.service - Discard unused blocks on filesystems from /etc/fstab.
Feb 03 00:05:04 umbrel systemd[1]: Starting fstrim.service - Discard unused blocks on filesystems from /etc/fstab...
Feb 03 00:05:04 umbrel systemd[1]: fstrim.service: Deactivated successfully.
Feb 03 00:05:04 umbrel systemd[1]: Finished fstrim.service - Discard unused blocks on filesystems from /etc/fstab.