July 2, 201115 yr I just checked the status of the array and noticed that one disk has a red dot beside it and has 80 errors. I checked the syslog and it is very long, so have attached the portion where the errors begin. It looks like the errors started a few hours ago. I'd appreciate any insight into what is going on and if the drive should be replaced. I have a 2 GB cache drive which could easily replace the problem drive. Thanks syslog.txt
July 3, 201115 yr Author I have since replaced the disk with a new one and the data has been rebuilt successfully. Before I did this, I tried to run a SMART report, but the disk could not be reached.
July 3, 201115 yr I have since replaced the disk with a new one and the data has been rebuilt successfully. Before I did this, I tried to run a SMART report, but the disk could not be reached. That is good news... The disabled disk might have had a loose cable though, and be un-responsive, and acted exactly as you described. You might try it on another cable before sending it in for RMA.
July 3, 201115 yr Author Thanks, Joe. Yes, after the initial panic wore off, I did a bit more reading and a loose cable came up as a possibility. The system is installed in a Norco RPC-4224 case and the drive was connected via an SAS cable to a Supermicro AOC-SASLP-MV8. The other 3 drives on that cable seem to be working fine and I have since moved the replacement drive into the original slot. It seems to be working fine there. I put the problem drive in a backup computer and, after running a SMART short test, obtained a report for it. The test seems to indicate read failure - am I reading that right? Is the next step to run a preclear or just RMA? Cheers SMART Attributes Data Structure revision number: 16 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 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 204 164 021 Pre-fail Always - 4791 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1179 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 093 093 000 Old_age Always - 5772 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 - 56 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 20 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3075 194 Temperature_Celsius 0x0022 119 103 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 3 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 3 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 - 13 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 Short offline Completed: read failure 90% 5772 3531113007 SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
July 3, 201115 yr It shows 3 unreadable sectors that are pending re-allocation when they are next written. Those would NOT have cause the disk to get taken off-line. (Since you have drive trays, a loose connector to the tray would take a disk off-line if it cannot be written) The "short" and "long" tests will abort on the first un-readable sector they encounter. It does not mean the disk is bad, as most large disks have several thousand sectors available as spares to be used is one needs to be re-allocated. A pre-clear will read all the sectors, hopefully finding all that are un-readable, then write them all, hopefully re-allocating any previously found, then read them all again too ensure all can be read. It is your best next step.
July 4, 201115 yr Author Hi Joe, Below is the result of the preclear. Anything to be concerned about here? Device Model: WDC WD20EARS-00MVWB0 SMART Attributes Data Structure revision number: 16 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 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 230 164 021 Pre-fail Always - 3500 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1183 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 5800 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 - 60 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 24 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3076 194 Temperature_Celsius 0x0022 122 103 000 Old_age Always - 28 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 200 200 000 Old_age Offline - 3 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 - 13 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 Short offline Completed: read failure 90% 5772 3531113007 SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0):
July 4, 201115 yr Hi Joe, Below is the result of the preclear. Anything to be concerned about here? Device Model: WDC WD20EARS-00MVWB0 SMART Attributes Data Structure revision number: 16 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 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 230 164 021 Pre-fail Always - 3500 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1183 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 5800 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 - 60 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 24 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3076 194 Temperature_Celsius 0x0022 122 103 000 Old_age Always - 28 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 200 200 000 Old_age Offline - 3 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 - 13 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 Short offline Completed: read failure 90% 5772 3531113007 SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): Yes, you did not post the output of the preclear. You posted a SMART report. Based on it, it appears the three sectors were not re-allocated, but written in place to their original sectors. Other than that, all looks fine.
July 4, 201115 yr Author Sorry, of the 3 reports in the preclear folder I chose the "preclear_finish" one. Here is the "preclear_rpt" from the same folder. ========================================================================1.11 == invoked as: ./preclear_disk.sh -a /dev/sda == WDC WD20EARS-00MVWB0 == Disk /dev/sda has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:31:34 (73 MB/s) == Last Cycle's Zeroing time : 6:24:50 (86 MB/s) == Last Cycle's Post Read Time : 14:08:48 (39 MB/s) == Last Cycle's Total Time : 28:06:19 == == Total Elapsed Time 28:06:19 == == Disk Start Temperature: 28C == == Current Disk Temperature: 28C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Up_Time = 230 203 21 ok 3500 Seek_Error_Rate = 100 200 0 ok 0 No SMART attributes are FAILING_NOW 3 sectors were pending re-allocation before the start of the preclear. 3 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, a change of -3 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================
July 5, 201115 yr Nothing looks particularly concerning here. We have seen these pending sectors clear without being reallocated before, particularly with new drives, and there have not been any adverse effect. I would keep an eye on the offline_uncorrectable and mult_zone_error_rate. At their current levels it does not appear a problem, but non-zeros for these is not that common. If they keep rising you should post back. But the main thing we look for in these smart reports is reallocated sectors and pending sectors. And yours are both zero, which is a good place to be!
July 5, 201115 yr Author Thanks so much for the analysis, bjp999. I may just use this drive as a cache drive for the time being, as the former cache was used as the replacement drive. Cheers
July 5, 201114 yr Author If this issue happens again, what is the best way to deal with errors caused by a loose connection? I initially tried plugging the problem drive into an empty slot in the case, but after powering on again and assigning it to the proper position, there was still the red dot beside the drive. Should I have then run a parity check to allow the array to see the drive as healthy? Sorry, I still have so much to learn. Cheers
July 5, 201114 yr When a drive appears to fail, unRaid will kick it out of the array and begin simulating it. If you find the problem was not the drive but a loose cable or something, there are two ways to recover: 1 - allow unRaid to rebuild the contents of the disk to the same (or a different disk). This requires unRaid to "forget" the disk failed if you want it back on the same disk. To accomplish this, you need to stop the array, unassign the red balled disk from the array, and then start the array. You can then stop the array again, reassign the disk to the array, and unRaid will see this as a new disk and offer to rebuild onto it. 2 - there is a procedure commonly referred to as the "trust" (or "trust my parity") procedure that enables you to, in essence, force the drive back into the array. Read about it on the wiki, but also realized the "set invalidslot" command needed for this to work is broken in recent 5.0 betas. Procedure 1 above takes a while to complete, and is best if you have written data to the disk while it was being simulated. Procedure 2 is faster and best if the problem was detected immediately and no data has been written to that disk in simulated mode.
July 5, 201114 yr Procedure 2 is faster and best if the problem was detected immediately and no data has been written to that disk in simulated mode. But remember, the drive was kicked out of the array (made invalid) when a write to it failed. Therefore, it is GUARANTEED to have had something that was not written to the disk. You'll have to judge if it might have been important. It is prudent to run a file system check as it could have been part of the file-system structure being updated, and it might now be corrupted on the physical disk since the write failed. (but correct on the simulated disk)
July 5, 201114 yr Author Thanks for the suggestions regarding how to proceed if this happens again. After putting the precleared disk back into the system last night as the cache drive, I started a noncorrect parity check. I woke up this morning to find 8 parity errors. The syslog is attached. Also, I obtained smart reports for every drive - all seemed fine except for disk 12 which reported a raw_read_error_rate of 1. Disk 5 and 9 also reported runtime_bad_block of 6 and 7 respectively. What should be my next step? - to run a regular parity check to correct the errors? syslog.txt
July 5, 201114 yr Thanks for the suggestions regarding how to proceed if this happens again. After putting the precleared disk back into the system last night as the cache drive, I started a noncorrect parity check. I woke up this morning to find 8 parity errors. The syslog is attached. Also, I obtained smart reports for every drive - all seemed fine except for disk 12 which reported a raw_read_error_rate of 1. Disk 5 and 9 also reported runtime_bad_block of 6 and 7 respectively. What should be my next step? - to run a regular parity check to correct the errors? I'd run a correcting fix now, then I'd wait a week or so, then upgrade to 4.7.1, or 5.0beta8, and then fix them again. There is a bug fix that will help prevent them going forward (apparently, they can occur when adding a new disk) The SMART errors you are reporting are RAW errors, meaningful only to the manufacturer of the drive. Unless the NORMALIZED VALUE is nearing the FAILURE THRESHOLD FOR THAT attribute is there anything to be concerned about.
July 6, 201114 yr Author A correcting parity check resolved the errors, and a second one confirmed it. I'll upgrade to the new version of unRaid when it is released, before adding any more disks. Cheers
Archived
This topic is now archived and is closed to further replies.