May 13, 201412 yr Hi, I'm looking for some guidance on disk errors I'm seeing. I have an unRAID server built in February 2014 from all new parts: CASE - LIAN LI PC-Q25B Black Aluminum Mini-ITX Case MOBO - ASUS H87I-PLUS LGA 1150 Intel H87 Mini ITX Motherboard CPU - Intel Pentium G3220 Haswell 3.0GHz LGA 1150 54W Dual-Core CPU PSU - SILVERSTONE ST30SF 300W ATX12V 80+ BRONZE PSU RAM - G.SKILL Ripjaws X Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 Parity: WD 4 TB Red Data Drives: 2 X WD 4 TB Red Cache Drive: Samsung_SSD_840_PRO_Series, 128 GB Only plugins are Plex server and APC shutdown. UnRAID Plus Version 5.0.5 Drives pre cleared with no issues. My first parity check in March completed with no errors of any kind. Parity check a couple of weeks ago completed without any parity errors, but many disc read errors showed up for disk2 during the parity check. I continue to see occasional disk2 (only) read errors. I have changed the data cable and checked the power connection and still see errors. UnRAID still says “Parity is valid”. A recent syslog and SMART report for drive 2 is attached. Thanks! Jerry Syslog_SmartD2.zip
May 13, 201412 yr Hi, I'm looking for some guidance on disk errors I'm seeing. I have an unRAID server built in February 2014 from all new parts: CASE - LIAN LI PC-Q25B Black Aluminum Mini-ITX Case MOBO - ASUS H87I-PLUS LGA 1150 Intel H87 Mini ITX Motherboard CPU - Intel Pentium G3220 Haswell 3.0GHz LGA 1150 54W Dual-Core CPU PSU - SILVERSTONE ST30SF 300W ATX12V 80+ BRONZE PSU RAM - G.SKILL Ripjaws X Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 Parity: WD 4 TB Red Data Drives: 2 X WD 4 TB Red Cache Drive: Samsung_SSD_840_PRO_Series, 128 GB Only plugins are Plex server and APC shutdown. UnRAID Plus Version 5.0.5 Drives pre cleared with no issues. My first parity check in March completed with no errors of any kind. Parity check a couple of weeks ago completed without any parity errors, but many disc read errors showed up for disk2 during the parity check. I continue to see occasional disk2 (only) read errors. I have changed the data cable and checked the power connection and still see errors. UnRAID still says “Parity is valid”. A recent syslog and SMART report for drive 2 is attached. Thanks! Jerry Smart report looks fine but seeing some signs of a cabling issue. Suggest double checking the cable are secured.
May 13, 201412 yr Author Smart report looks fine but seeing some signs of a cabling issue. Suggest double checking the cable are secured. Thanks bjp999! I've tried two different data cables. Maybe I should try a different SATA connection on the motherboard? Or a different position in the "hot swap" rack? Jerry
May 13, 201412 yr The signs will never disappear from the SMART report. If they were fixed they were fixed. The signs are those disturbing looking errors near the bottom of the report and reported by myMain as AT_Error_Count. If no new ones show up you are good.
May 13, 201412 yr Author The signs will never disappear from the SMART report. If they were fixed they were fixed. The signs are those disturbing looking errors near the bottom of the report and reported by myMain as AT_Error_Count. If no new ones show up you are good. Changing cables and motherboard SATA ports is not reducing the errors observed when reading disk2. I copied a few folders from disk2 to a PC and created 4443 errors during the operation, as reported by the web GUI. There are also 4465 writes to the disk, which appear to be related to the errors since I wasn't writing anything at the time. Attached is the latest syslog and the Disk2 SMART report. Thanks for reviewing! Jerry Syslog-2014-05-13_Smart-D2.zip
May 14, 201412 yr Author The latest SMART tests are showing consistent failures for both the long and short tests. My other two drives complete the short test without error. It looks like it's time to replace Disk2, but I welcome any suggestions for further evaluation. Thanks, Jerry === START OF INFORMATION SECTION === Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4E0931092 LU WWN Device Id: 5 0014ee 25f16058b Firmware Version: 80.00A80 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Wed May 14 11:41:20 2014 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 118) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (55260) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 552) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. 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 - 899 3 Spin_Up_Time 0x0027 179 176 021 Pre-fail Always - 8050 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 174 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 098 098 000 Old_age Always - 1565 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 - 58 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 12 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 337 194 Temperature_Celsius 0x0022 123 117 000 Old_age Always - 29 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 - 20 SMART Error Log Version: 1 ATA Error Count: 2 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 2 occurred at disk power-on lifetime: 1488 hours (62 days + 0 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 08 c0 00 50 e8 Error: UNC 8 sectors at LBA = 0x085000c0 = 139460800 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 08 c0 00 50 e8 08 09:30:46.299 READ DMA c8 00 08 98 00 50 e8 08 09:30:44.304 READ DMA ca 00 08 70 00 50 e8 08 09:30:44.276 WRITE DMA Error 1 occurred at disk power-on lifetime: 1488 hours (62 days + 0 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 08 70 00 50 e8 Error: UNC 8 sectors at LBA = 0x08500070 = 139460720 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 08 70 00 50 e8 08 09:30:40.613 READ DMA 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 60% 1564 3518249448 # 2 Short offline Completed: read failure 10% 1564 3518357072 # 3 Extended offline Completed: read failure 90% 1552 1910312 # 4 Extended offline Completed: read failure 90% 1552 1854760 # 5 Extended offline Aborted by host 90% 1552 - # 6 Short offline Completed: read failure 70% 1552 3518358800 # 7 Short offline Completed without error 00% 1448 - # 8 Extended offline Completed: read failure 80% 1437 587130048 # 9 Extended offline Completed: read failure 90% 1429 65987880 #10 Extended offline Aborted by host 90% 1428 - #11 Short offline Completed without error 00% 1424 - 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.
May 16, 201412 yr Author I would RMA the drive but you could see if it passes a pre-clear first. I replaced the drive with an identical pre-cleared WD Red. The rebuild from parity was successful. A parity check showed zero parity errors and no read errors were generated during the check. Since I'm using the same cable and SATA port with the new drive as the old drive it was clearly the drive that was bad. I hooked up the bad drive to a Windows computer and ran the Western Digital Data LifeGuard diagnostics. While the initial SMART status says "Pass" the drive consistently fails both the long and short SMART tests in that setup as well. I think there is sufficient evidence that the drive can't be trusted with data. With the flawless performace of the unRAID array since replacing the drive I'm convinced the drive itself was the source of the read errors. I will initiate an RMA on the drive.
Archived
This topic is now archived and is closed to further replies.