[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
howtos:hardware:smart_hdd_diagnostics [2015/01/05 00:56 (UTC)] – [#4 Start_Stop_Count and #12 Power_Cycle_Count and #193 Load_Cycle_Count] metaschima | howtos:hardware:smart_hdd_diagnostics [2015/01/05 01:18 (UTC)] – [Is my drive failing ?] metaschima | ||
---|---|---|---|
Line 199: | Line 199: | ||
===== #174 Unexpected power loss count and #192 Power-Off_Retract_Count ===== | ===== #174 Unexpected power loss count and #192 Power-Off_Retract_Count ===== | ||
- | Sudden power loss is detrimental to both HDDs and [[http:// | + | Sudden power loss is detrimental to both HDDs and [[http:// |
===== #190 Airflow_Temperature_Cel and 194 Temperature_Celsius ===== | ===== #190 Airflow_Temperature_Cel and 194 Temperature_Celsius ===== | ||
Line 207: | Line 207: | ||
===== Bad Blocks (#5, 196, 197, 198) ===== | ===== Bad Blocks (#5, 196, 197, 198) ===== | ||
- | Bad blocks are basically areas of the disk surface that are damaged and can no longer hold data reliably. Internally the HDD/SSD deals with these by marking them and re-mapping/allocating | + | Bad blocks are basically areas of the disk surface that are damaged and can no longer hold data reliably. Internally the HDD/SSD deals with these by marking them and remapping/reallocating |
====== SMART Tests ====== | ====== SMART Tests ====== | ||
Line 230: | Line 230: | ||
However, this method is difficult to implement safely, so you should usually just wait for the HDD to remap/ | However, this method is difficult to implement safely, so you should usually just wait for the HDD to remap/ | ||
- | How often should you run these tests ? That depends. If you run a server then more often is better, the smartmontools site recommends weekly tests. For a home user, I usually run a long test every 1000 power on hours, but that is up to you and also depends on the details of the drive and situation. Do not ignore your senses, if the HDD sounds unusual or makes strange noises, monitor it closely and/or replace it. | + | How often should you run these tests ? That depends. If you run a server then more often is better, the smartmontools site recommends weekly tests. For a home user, I usually run a long test every 1000 power on hours, but that is up to you and also depends on the details of the drive and situation. |
+ | |||
+ | ====== Is my drive failing ? ====== | ||
+ | |||
+ | A failing drive is defined as: | ||
+ | - Having a '' | ||
+ | - Having an '' | ||
+ | |||
+ | <note important> | ||
+ | |||
+ | Do not ignore your senses, if the HDD sounds unusual or makes strange noises, monitor it closely and/or replace it. Again, SMART cannot tell you with great accuracy if or when the drive will fail. The drive can fail with above threshold attributes and minimal signs. The only hope you have to keep your data safe is to backup your data, use the 3-2-1 strategy as mentioned above. | ||
+ | |||
+ | ====== smartd ====== | ||
+ | |||
+ | What is smartd ? It is a daemon that monitors SMART. So if you don't want to manually monitor and run tests, you can set up smartd to run them on a regular basis. You should refer to '' | ||
====== Sources ====== | ====== Sources ====== | ||
<!-- If you are copying information from another source, then specify that source --> | <!-- If you are copying information from another source, then specify that source --> |