- 6.12.11
- Solved
- Minor
Hello, i was having a problem with scheduled trim.
It seems that when you run the ssd_trim script manually in a terminal, or by clicking the "trim now" button in the scheduler page, the script would run as expected, but when the script was run on a cron schedule, it would bypass the check to see if the disk was a "spinning disk" and trim ALL drives.
With the help of members in the general support section, it was determined the initial check in the script, checks to see if the script is being run by a cron job, and if so, runs trim on ALL drives.
I believe this is a bug, unless it is the intended functionality to run a trim on all drives, regardless of SSD/HDD when using the cron schedule.
Link to thread of original issue: