trimm inactive on old vertex 4 ssd

thesorcerer · 26. März 2021

Hello,

Can someone help me with the following problem? I have build an omvbox with a vertex 4 ssd as boot drive. When I did a check if the system is using the trim function the result was negative. I have read that omv automatically enables trim on ssd during install. Could it be that because the vertex 4 is old that it wasn't recognized properly? And yes I know, this drive will be replaced in due time . I used the following commands to obtain info:

Code

root@openmediavault:~# systemctl status fstrim.timer
● fstrim.timer - Discard unused blocks once a week
   Loaded: loaded (/lib/systemd/system/fstrim.timer; disabled; vendor preset: en
   Active: inactive (dead)
  Trigger: n/a
     Docs: man:fstrim

Code

root@openmediavault:~# fstrim --verbose --all
/boot/efi: 510.9 MiB (535654400 bytes) trimmed on /dev/sdc1
/: 93.7 MiB (98189312 bytes) trimmed on /dev/sdc2

Code

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdc2 during installation
UUID=6b4723db-8f54-466b-ba3a-f120fff201ca /               ext4    errors=remoun$
# /boot/efi was on /dev/sdc1 during installation
UUID=C75E-AEA5  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/sdc3 during installation
UUID=b0c33dd1-59cd-4c2a-a5d3-6084be9478b2 none            swap    sw           $
# >>> [openmediavault]
/dev/disk/by-id/md-name-openmediavault:DataRaid1                /srv/dev-disk-b$
/srv/dev-disk-by-id-md-name-openmediavault-DataRaid1/PresciousData/            $
# <<< [openmediavault]

Alles anzeigen

Will the following command solve this problem or do I need to do more?

Code

sudo systemctl enable fstrim.timer

Any help is appreciated.

Thank you.

geaves · 26. März 2021

Try replacing enable with start, the least it will do is barf

thesorcerer · 26. März 2021

Will try asap. Currently in a large transfer of data. Shall post outcome.

thesorcerer · 27. März 2021

output:

Code

root@openmediavault:~# systemctl status fstrim.timer
● fstrim.timer - Discard unused blocks once a week
   Loaded: loaded (/lib/systemd/system/fstrim.timer; enabled; vendor preset: enabled)
   Active: active (waiting) since Sat 2021-03-27 00:22:50 CET; 1min 59s ago
  Trigger: Mon 2021-03-29 00:00:00 CEST; 1 day 22h left
     Docs: man:fstrim

Mar 27 00:22:50 openmediavault.local systemd[1]: Started Discard unused blocks once a week.

Looks good. Thanks.

trimm inactive on old vertex 4 ssd

thesorcerer 27. März 2021

Jetzt mitmachen!

Tags