[[fester:hvalid_hdd]]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
fester:hvalid_hdd [2017/06/24 15:47] – [Getting Your Test Results] add content danfester:hvalid_hdd [2017/06/24 17:46] (current) – [Non-Destructive Badblocks Test Using tmux] brief instructions dan
Line 419: Line 419:
 ==== Non-Destructive Badblocks Test Using tmux ==== ==== Non-Destructive Badblocks Test Using tmux ====
  
-I don’t know how to do this.+To do a non-destructive ''badblocks'' test, follow the instructions above, but replace -w with -n Example commands might look like:
  
-If someone wants to give me the information and detailed copyright free screen shots will be happy to include them in this guide or you could replace this or any section with your own?+''badblocks -ns /dev/da0'' 
 + 
 +or 
 + 
 +''badblocks -b 4096 -nsv /dev/da1'' 
 + 
 +This test is intended to be non-destructive--once it has completed, the data on your disk should be unharmed.  Even so, I'd discourage running this on a disk with important data unless you have a good, readily-accessible backup.
  
  
Line 554: Line 560:
  
 ==== Making Sense of SMART Data ==== ==== Making Sense of SMART Data ====
 +
 +When looking at SMART data from a SMART storage device certain entries in the table are not important in terms of data integrity and health. They just give general information (e.g. Model, serial number, etc) and other types of information that could be useful in certain circumstances.
 +
 +Other entries are very important and should immediately ring alarms bells if certain values are present.
 +
 +In terms of HDD/SDD hardware validation these are the entries in the SMART data you need to scrutinise.
 +
 +|  \\ __ID#__ \\  |  \\ __ATTRIBUTE_NAME__ \\  |  \\ __FLAG__ \\  |  \\ __VALUE__ \\  |  \\ __WORST__ \\  |  \\ __THRESH__ \\  |  \\ __TYPE__ \\  |  \\ __UPDATED__ \\  |  \\ __WHEN_FAILED__ \\  |  \\ __RAW_VALUE__ \\  |
 +|  \\ 1 \\ |  \\ Raw_Read_Error_Rate \\ |  \\ 0x002f \\ |  \\ 200 \\ |  \\ 200 \\ |  \\ 051 \\ |  \\ Prefail \\ |  \\ Always \\ |  \\ - \\ |  \\ 0 \\ |
 +|  \\ 5 \\ |  \\ Reallocated_Sector_Ct \\ |  \\ 0x0033 \\ |  \\ 200 \\ |  \\ 200 \\ |  \\ 140 \\ |  \\ Prefail \\ |  \\ Always \\ |  \\ - \\ |  \\ 0 \\ |
 +|  \\ 7 \\ |  \\ Seek_Error_Rate \\ |  \\ 0x002e \\ |  \\ 200 \\ |  \\ 200 \\ |  \\ 000 \\ |  \\ Old_age \\ |  \\ Always \\ |  \\ - \\ |  \\ 0 \\ |
 +|  \\ 10 \\ |  \\ Spin_Retry_Count \\ |  \\ 0x0032 \\ |  \\ 100 \\ |  \\ 100 \\ |  \\ 000 \\ |  \\ Old_age \\ |  \\ Always \\ |  \\ - \\ |  \\ 0 \\ |
 +|  \\ 11 \\ |  \\ Calibration_Retry_Count \\ |  \\ 0x0032 \\ |  \\ 100 \\ |  \\ 100 \\ |  \\ 000 \\ |  \\ Old_age \\ |  \\ Always \\ |  \\ - \\ |  \\ 0 \\ |
 +|  \\ 196 \\ |  \\ Reallocated_Event_Count \\ |  \\ 0x0032 \\ |  \\ 200 \\ |  \\ 200 \\ |  \\ 000 \\ |  \\ Old_age \\ |  \\ Always \\ |  \\ - \\ |  \\ 0 \\ |
 +|  \\ 197 \\ |  \\ Current_Pending_Sector \\ |  \\ 0x0032 \\ |  \\ 200 \\ |  \\ 200 \\ |  \\ 000 \\ |  \\ Old_age \\ |  \\ Always \\ |  \\ - \\ |  \\ 0 \\ |
 +|  \\ 198 \\ |  \\ Offline_Uncorrectable \\ |  \\ 0x0030 \\ |  \\ 100 \\ |  \\ 253 \\ |  \\ 000 \\ |  \\ Old_age \\ |  \\ Always \\ |  \\ - \\ |  \\ 0 \\ |
 +|  \\ 199 \\ |  \\ UDMA_CRC_Error_Count \\ |  \\ 0x0032 \\ |  \\ 200 \\ |  \\ 200 \\ |  \\ 000 \\ |  \\ Old_age \\ |  \\ Always \\ |  \\ - \\ |  \\ 0 \\ |
 +
 +If you get any value other than __zero__ in the “RAW VALUE” for these entries you should be suspicious of this drive and may need to return the device for testing depending on the manufacturer’s warranty.
 +
 +Another area you should look at is the “SMART Self-test log structure”. Here is an example. It will tell you if the drive passed its tests.  Any result other than "Completed without error" is cause for concern.
 +
 +SMART Self-test log structure revision number 1
 +
 +|  \\ __Num__ \\  |  \\ __Test_Description__ \\  |  \\ __Status__ \\  |  \\ __Remaining LifeTime(hours)__ \\  |  \\ __LifeTime(hours)__ \\  |  \\ __LBA_of_first_error__ \\  |
 +|  \\ # 1 \\ |  \\ Extended offline \\ |  \\ Completed without error \\ |  \\ 00% \\ |  \\ 503 \\ |  \\ - \\ |
 +|  \\ # 2 \\ |  \\ Conveyance offline \\ |  \\ Completed without error \\ |  \\ 00% \\ |  \\ 494 \\ |  \\ - \\ |
 +|  \\ # 3 \\ |  \\ Short offline \\ |  \\ Completed without error \\ |  \\ 00% \\ |  \\ 75 \\ |  \\ - \\ |
 +
 +(If Fester is misinformed about interpreting SMART data or has omitted something important please let me know and I will try to put it in the guide or you could replace this or any section with your own?)
 +
 +That’s the HDD/SDD validation completed. Now it is time to reinstall FreeNAS and create a basic server.
 +
 +\\
  
  
  • fester/hvalid_hdd.txt
  • Last modified: 2017/06/24 17:46
  • by dan