There exist many tools to access the SMART interface depending on your OS. The key thing is that the HD itself does all the work. The tools just provide access to the HD.
The beauty of SMART is that
- you can run the SMART tests on a running system on a mounted HD in use! Since the HD does the SMART scheduling internally, it can figure out when and how to continue with it's own test while getting normal OS requests.
- it's pretty easy to do a manual scan. For Linux, download the smartctl software and then start issuing commands. There's a lot of documentation on the web.
- with a bit of work you can setup regular SMART background tests and have alerts sent when a HD falls below the built in "failure" thresholds.
- a thorough "long" test takes several hours. On a 1.5TB drive, it takes 4-8 hours.
- you need to have the HD hooked up directly via its native interface, namely PATA or SATA. If a drive is hooked up via a USB enclosure, smartctl will claim the drive does not support SMART. Ugh. (I assume eSATA will work, as this is fundamentally SATA).
I'm not going to repeat all the information out there. But here's some decent links.
- A great article on SMART geared toward Linux.
- The wikipedia article on SMART, with many more links.
No comments:
Post a Comment