April 26, 201412 yr Last checked on Sat Apr 26 11:19:58 2014 MDT (today), finding 0 errors. ? Duration: 16 hours, 13 minutes, 29 seconds. Average speed: 68.5 MB/sec On the Hard drive list Disc 5 has 22 errors but Parity check found 0 errors tail -n 40 -f /var/log/syslog Apr 26 08:03:53 Tower kernel: sd 2:0:0:0: [sdb] Apr 26 08:03:53 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08 Apr 26 08:03:53 Tower kernel: sd 2:0:0:0: [sdb] Apr 26 08:03:53 Tower kernel: Sense Key : 0x3 [current] [descriptor] Apr 26 08:03:53 Tower kernel: Descriptor sense data with sense descriptors (in hex): Apr 26 08:03:53 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 01 Apr 26 08:03:53 Tower kernel: 5b 41 ea 08 Apr 26 08:03:53 Tower kernel: sd 2:0:0:0: [sdb] Apr 26 08:03:53 Tower kernel: ASC=0x11 ASCQ=0x4 Apr 26 08:03:53 Tower kernel: sd 2:0:0:0: [sdb] CDB: Apr 26 08:03:53 Tower kernel: cdb[0]=0x88: 88 00 00 00 00 01 5b 41 e7 50 00 00 03 68 00 00 Apr 26 08:03:53 Tower kernel: end_request: I/O error, dev sdb, sector 5826013704 Apr 26 08:03:53 Tower kernel: ata2: EH complete Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013640 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013648 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013656 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013664 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013672 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013680 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013688 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013696 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013704 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013712 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013720 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013728 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013736 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013744 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013752 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013760 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013768 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013776 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013784 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013792 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013800 Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013808 Apr 26 08:53:56 Tower kernel: mdcmd (48): spindown 5 Apr 26 11:19:58 Tower kernel: md: sync done. time=58409sec Apr 26 11:19:58 Tower kernel: md: recovery thread sync completion status: 0 Apr 26 12:05:00 Tower kernel: mdcmd (49): spindown 0 Apr 26 12:05:00 Tower kernel: mdcmd (50): spindown 4 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 - 33 3 Spin_Up_Time 0x0027 178 178 021 Pre-fail Always - 6066 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 436 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 083 083 000 Old_age Always - 13107 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 - 45 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 30 193 Load_Cycle_Count 0x0032 166 166 000 Old_age Always - 103526 194 Temperature_Celsius 0x0022 133 119 000 Old_age Always - 17 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 - 1 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 - 12 What do i do? is the drive bad? thanks
April 27, 201412 yr Author i checked the logs folder but its not there and i have since rebooted the system and the logs are new now and the old one didn't save. I can do another parity check if that will help get the logs again. I have that one 3tb drive that red balled but looks ok maybe i replace this drive with that and do a preclear on it?
April 27, 201412 yr Author its this drive that red balled http://lime-technology.com/forum/index.php?topic=33070.0 i pre cleared it and looks ok i think i will remove disc5 and put this in and let it rebuild and do a parity test then pre clear disk5 and see if its okay. Is that a good idea? this is the 3tb drive from that link 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 - 1 3 Spin_Up_Time 0x0027 176 152 021 Pre-fail Always - 8183 4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3284 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 080 080 000 Old_age Always - 14785 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 - 42 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 27 193 Load_Cycle_Count 0x0032 187 187 000 Old_age Always - 40146 194 Temperature_Celsius 0x0022 121 109 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 - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 6 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 1 == WDC WD30EZRX-00MMMB0 WD-WCAWZ1857328 == Disk /dev/sdf has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 9:42:49 (85 MB/s) == Last Cycle's Zeroing time : 8:28:48 (98 MB/s) == Last Cycle's Post Read Time : 24:06:49 (34 MB/s) == Last Cycle's Total Time : 42:19:33 == == Total Elapsed Time 42:19:33 == == Disk Start Temperature: 22C == == Current Disk Temperature: 31C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Up_Time = 176 155 21 ok 8183 Seek_Error_Rate = 100 200 0 ok 0 Temperature_Celsius = 121 129 0 ok 31 No SMART attributes are FAILING_NOW 1 sector was pending re-allocation before the start of the preclear. 1 sector was 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 -1 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. ============================================================================
April 28, 201412 yr Very similar situation tom mine here http://lime-technology.com/forum/index.php?topic=33016.0 Interestingly, my "problems" are also with WD30EZRX drives. Wonder if there's a possible kernel <-> drive "glitch".
April 30, 201412 yr Author Very similar situation tom mine here http://lime-technology.com/forum/index.php?topic=33016.0 Interestingly, my "problems" are also with WD30EZRX drives. Wonder if there's a possible kernel <-> drive "glitch". yea that's weird but from my drive it looks like it red balled because of the UDMA_CRC_Error_Count something to do with the cables i re pluged it took out disk 5 and i rebuild the data, right now i am waiting for parity verify then i will preclear disk5 to see why its making those errors.
May 3, 201412 yr Author okay it finally finished pre clearing disc5 some things that changed Offline_Uncorrectable used to be 1 and is 0 now Raw_Read_Error_Rate was 33 is now 46 here is the result from pre clear == invoked as: ./preclear_disk.sh /dev/sdb == WDC WD30EZRX-00DC0B0 WD-WMC1T0564002 == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 8:48:45 (94 MB/s) == Last Cycle's Zeroing time : 7:18:18 (114 MB/s) == Last Cycle's Post Read Time : 21:10:18 (39 MB/s) == Last Cycle's Total Time : 37:18:23 == == Total Elapsed Time 37:18:23 == == Disk Start Temperature: 19C == == Current Disk Temperature: 24C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 0 ok 0 Temperature_Celsius = 126 131 0 ok 24 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 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, the number of sectors pending re-allocation did not change. 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. ============================================================================ Final SMART report 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 - 46 3 Spin_Up_Time 0x0027 180 178 021 Pre-fail Always - 5975 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 446 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 082 082 000 Old_age Always - 13252 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 - 48 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 33 193 Load_Cycle_Count 0x0032 166 166 000 Old_age Always - 103848 194 Temperature_Celsius 0x0022 126 119 000 Old_age Always - 24 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 - 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 - 6 SMART Error Log Version: 1 ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 7413 hours (308 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 c8 08 00 e0 Error: UNC at LBA = 0x000008c8 = 2248 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 c8 08 00 e0 08 00:07:13.496 READ DMA ca 00 08 90 08 00 e0 08 00:07:13.496 WRITE DMA ca 00 08 98 08 00 e0 08 00:07:13.496 WRITE DMA ca 00 08 a0 08 00 e0 08 00:07:13.494 WRITE DMA ca 00 08 a8 08 00 e0 08 00:07:13.493 WRITE DMA SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 2873 - 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. is that what is causing the errors to show next to the drive? Raw_Read_Error_Rate and Seek_Error_Rate and how come Unraid doesn't care it cant read a sector? Apr 26 08:03:53 Tower kernel: md: disk5 read error, sector=5826013640 or is it trying to read it fails and then tries again and succeed so it shows up as a error but it doesn't red ball it>? what do you think is the drive okay to use?
Archived
This topic is now archived and is closed to further replies.