Check Ubuntu TRIM: Timer, Discard Support and Service Results Are Different Checks
An active Ubuntu TRIM timer answers a scheduling question. It does not, by itself, prove that the disk supports discard or that unused blocks reached a physical SSD. Check the timer, its configured schedule, the reported device capability and the service result as separate pieces of evidence.
This read-only walkthrough matches the Leverage Lab Studios demonstration recorded on Ubuntu 24.04 in a virtual machine. The example’s virtual disk reports a discard maximum of 0B. That result is important: a working timer cannot establish physical-device TRIM support through a storage path that does not expose it.
Four questions, four checks
| Question | Read-only check | What it does not establish |
|---|---|---|
| Is the timer enabled and active? | systemctl is-enabled and is-active | Whether discard reaches this disk |
| What is its schedule? | systemctl cat and list-timers | That every scheduled run completed |
| What capability is reported? | lsblk --discard | SSD health, performance or successful physical trimming |
| What happened on the last run? | Service status and journal | That every filesystem issued a successful device operation |
1. Inspect the timer’s state
systemctl is-enabled fstrim.timer
systemctl is-active fstrim.timer
systemctl status fstrim.timer --no-pagerRead the actual output rather than assuming your machine matches the video. An enabled unit is configured for activation through its installation links. An active timer is currently participating in scheduling. These are related but distinct states. An inactive or missing unit requires investigation; it is not a reason to start changing disk settings blindly.
Some systemctl inspection commands return a nonzero exit status when the state being queried is false. Preserve the output and interpret the reported state. This walkthrough does not run an enable or start command.
2. Read the effective schedule
systemctl cat fstrim.timer
systemctl list-timers --all fstrim.timerThe unit text shows the timer configuration and any displayed drop-in overrides. The timer listing gives its currently calculated next and previous trigger information. The example uses a weekly schedule. Your distribution, local overrides and scheduling options can change the details; use your own loaded unit and listing as the evidence.
A configured interval is a plan, not a completed storage operation. Keep the timer’s trigger information separate from the service’s execution result.
3. Check the capability exposed by the storage path
lsblk --discard
lsblk --output NAME,TYPE,SIZE,MOUNTPOINTS,DISC-GRAN,DISC-MAX,DISC-ZEROIdentify the device and its filesystem path before interpreting its discard columns. Do not assume that a name such as sda refers to the same kind of drive on every machine. If you need help understanding a known existing Linux volume, see our Linux mounting walkthrough; mounting and formatting are different operations.
In the recorded virtual-machine example, DISC-MAX is 0B. Treat that as the capability currently reported through the guest’s storage path. It does not diagnose the host SSD’s health, and it is not evidence that a physical SSD was trimmed. USB bridges, virtual controllers, device-mapper layers and filesystem configuration can affect what is exposed.
Conversely, a nonzero reported maximum is a capability clue. It is not a complete proof that a later trim operation reached the intended physical device.
4. Inspect the last service result
systemctl status fstrim.service --no-pager
systemctl show fstrim.service --property=Result,ExecMainStatus
journalctl --unit=fstrim.service --no-pager --lines=20A service result of success and an exit status of zero describe how that service invocation completed. Review the associated journal entries and the actual command configured for the service. In particular, the fstrim manual explains that its all-filesystems options can skip unsupported filesystems. A successful service run therefore does not override a disk reporting no discard capability.
Missing history is also a limitation, not proof of success or failure. Journal retention and the current user’s access can affect which entries are visible. Keep a note of which checks were actually readable.
What a useful result looks like
Record the timer state, its effective schedule, the relevant device’s discard values, and the service result with its journal context. That gives you four statements you can defend individually. Avoid collapsing them into a single claim such as “TRIM is working” unless the evidence supports the full storage path you mean.
The tutorial deliberately stops after inspection. It does not manually run fstrim, change a mount option, enable a unit or alter a virtual disk. For broader operating-system context, read our Windows, macOS and Linux TRIM overview. For device condition, use a separate Linux SSD health check; discard scheduling and health are different questions.
References and next steps
Continue through the tutorial collection for more matching videos and written steps. Before making later changes to a real storage system, make sure you have a recoverable backup; our backup guide for beginners is a starting point.
James Kennedy is a writer and product researcher at Drives Hero with a background in IT administration and consulting. He has hands-on experience with storage, networking, and system performance, and regularly improves and optimizes his home networking setup.




