I had one of my drives show 4 pending sectors. I replaced the drive and I am now running a test on the drive with badblocks. After the first pass (witing AA), the pending sectors cleared, and have not come back after the second pass (55). I was more than 99% the first write pass, before the pending sectors changed from 4 to 0, so I know the bad spots are in the last 1%. The self test stopped very quickly with the errors shown in the log below.
Since a complete pass takes about 23 hours, I would like to "spot test" the area around the previous bad sectors. The badblocks statement I used and the relevent parts of the output from smartctl are shown below. I tried calculating an address based on 512 bytes and 4096 bytes, but neither value seems to generate an offset consistent with ~99% of the total disk space. Can someone tell me how to calculate the parameters to modify the badblocks so I just tests the last 1% of the disk.
badblocks statement used:
Relevnt sections of smartctl output:
Is this type of error likely to be caused by a power failure? FreeNAS experienced an unexpected power outage due to a simulataneous power failure and UPS battery failure. Assuming the drive passes a few tests, how likely is the drive to be safe?
Any input much appreciated.
Since a complete pass takes about 23 hours, I would like to "spot test" the area around the previous bad sectors. The badblocks statement I used and the relevent parts of the output from smartctl are shown below. I tried calculating an address based on 512 bytes and 4096 bytes, but neither value seems to generate an offset consistent with ~99% of the total disk space. Can someone tell me how to calculate the parameters to modify the badblocks so I just tests the last 1% of the disk.
badblocks statement used:
Code:
badblocks -b 4096 -c 65536 -wsv /dev/$devid
Relevnt sections of smartctl output:
Code:
Model Family: Western Digital Red Device Model: WDC WD60EFRX-68MYMN1 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 195 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 206 193 021 Pre-fail Always - 8700 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 271 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 042 042 000 Old_age Always - 42694 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 98 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 70 193 Load_Cycle_Count 0x0032 187 187 000 Old_age Always - 39240 194 Temperature_Celsius 0x0022 109 101 000 Old_age Always - 43 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 Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 42658 3088571888 # 2 Extended offline Completed: read failure 90% 39369 3088575408 # 3 Extended offline Completed without error 00% 17065 - # 4 Extended offline Aborted by host 90% 17051 - # 5 Extended offline Aborted by host 90% 17051 - # 6 Extended offline Completed without error 00% 16961 - # 7 Short offline Completed without error 00% 16918 -
Is this type of error likely to be caused by a power failure? FreeNAS experienced an unexpected power outage due to a simulataneous power failure and UPS battery failure. Assuming the drive passes a few tests, how likely is the drive to be safe?
Any input much appreciated.