Wiki » History » Version 2
Luke Murphey, 08/27/2016 05:56 AM
1 | 1 | Luke Murphey | h1. Wiki |
---|---|---|---|
2 | 1 | Luke Murphey | |
3 | 1 | Luke Murphey | |
4 | 1 | Luke Murphey | h2. Getting the Source Code |
5 | 1 | Luke Murphey | |
6 | 1 | Luke Murphey | This project is open source. You can get the code on "GitHub":https://github.com/LukeMurphey/splunk-smartmon. |
7 | 1 | Luke Murphey | |
8 | 2 | Luke Murphey | h2. How failures are dedicated |
9 | 2 | Luke Murphey | |
10 | 2 | Luke Murphey | Failures are identified based on the two things" |
11 | 2 | Luke Murphey | |
12 | 2 | Luke Murphey | # SMART health status |
13 | 2 | Luke Murphey | # Known bad attributes |
14 | 2 | Luke Murphey | |
15 | 2 | Luke Murphey | Monitoring SMART health status is easy. SMART will flag a disk as being a failure and indicate a failed test. |
16 | 2 | Luke Murphey | |
17 | 2 | Luke Murphey | However, there are some other attributes that do not necessarily flagged by SMART as a failure but are known to be associated with failing disks. BackBlaze (see https://www.backblaze.com/blog/hard-drive-smart-stats/) has determined that the following can be used to flag drives as likely failing soon: |
18 | 2 | Luke Murphey | |
19 | 2 | Luke Murphey | * SMART 5 – Reallocated_Sector_Count. (1-4 warning, > 4 replace) |
20 | 2 | Luke Murphey | * SMART 187 – Reported_Uncorrectable_Errors. (> 1 replace) |
21 | 2 | Luke Murphey | * SMART 188 – Command_Timeout. (1-13 warning, > 13 replace) |
22 | 2 | Luke Murphey | * SMART 197 – Current_Pending_Sector_Count. (> 1 replace) |
23 | 2 | Luke Murphey | * SMART 198 – Offline_Uncorrectable. (> 1 replace) |
24 | 2 | Luke Murphey | |
25 | 1 | Luke Murphey | h2. Contents |
26 | 1 | Luke Murphey | |
27 | 1 | Luke Murphey | {{child_pages}} |