SMART test vs SMART service

Status
Not open for further replies.

aufalien

Patron
Joined
Jul 25, 2013
Messages
374
I'm confused as to the diff between configuring a SMART test via cron vs SMART service.

They are both scheduled and can run at similar times.

The cron will provide granularity in terms of only choosing to test certain drive(s) but if one wanted to check all drives, wouldn't the service be more practical?

Also, I do see the cron allowing to perform sort or long tests, hence even more granularity.

Any pearls are appreciated.
 

joelmusicman

Patron
Joined
Feb 20, 2014
Messages
249
I just use the GUI, with SMART tests setup as recommended by CyberJock: Run each of the following twice a month, on different days: Short test, Long test, Scrub. Typical start times are 0200 AM, on the same day each month. Make sure to have email set up as then it will warn you if any problems are detected. Otherwise, the SMART info can be fetched with smartctl -a /dev/ada(*), and the scrubs with zpool status.
 

ser_rhaegar

Patron
Joined
Feb 2, 2014
Messages
358

aufalien

Patron
Joined
Jul 25, 2013
Messages
374
To ensure I'm on the right track I've configured my SMART tests via Systems Setting is follows;

smart-tests.png


My desire is to have my short tests run 3 times a month (every 1/4 month) and the long test run at the end of the month, both at 3AM.

* I'm assuming to ignore the Everyday under the Day of the week column?

My Service Setting is as follows;

smart-service.png


This should run on the schedule I have set under System settings?

* I'm assuming that the Check interval is between individual disks as I have 50. I didn't leave it at 30 to avoid a really long test period. Plus I've read that SMART checks data stored as drive attributes so no load will be incurred.
 
Status
Not open for further replies.
Top