Shunz Posted July 14, 2015 Share Posted July 14, 2015 My 2nd redball in 3 months...! Its a Western Digital Red 6TB. Does the Power-Off_Retract_Count look normal? The value has been unchanged since May 18. Jul 10 21:37:18 unraid kernel: Plex New Transc[31703]: segfault at a6f280fc ip 08c9ecde sp bfab0738 error 4 in Plex New Transcoder[8048000+1078000] (Errors) Jul 10 22:23:37 unraid kernel: Plex New Transc[6755]: segfault at a5a540fc ip 08c9ecde sp bfa11818 error 4 in Plex New Transcoder[8048000+1078000] (Errors) Jul 10 22:30:33 unraid kernel: Plex New Transc[8644]: segfault at a822e0fc ip 08c9ecde sp bf86a5c8 error 4 in Plex New Transcoder[8048000+1078000] (Errors) Jul 10 23:34:05 unraid kernel: mdcmd (186): spindown 2 (Routine) Jul 10 23:54:05 unraid kernel: mdcmd (187): spindown 3 (Routine) Jul 11 01:06:05 unraid kernel: mpt2sas0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) (Drive related) Jul 11 01:06:05 unraid kernel: sd 1:0:1:0: [sdg] Device not ready (Drive related) Jul 11 01:06:05 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:05 unraid kernel: Result: hostbyte=0x00 driverbyte=0x08 (System) Jul 11 01:06:05 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:05 unraid kernel: Sense Key : 0x2 [current] Jul 11 01:06:05 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:05 unraid kernel: ASC=0x4 ASCQ=0x0 Jul 11 01:06:05 unraid kernel: sd 1:0:1:0: [sdg] CDB: (Drive related) Jul 11 01:06:05 unraid kernel: cdb[0]=0x88: 88 00 00 00 00 02 40 00 88 08 00 00 00 08 00 00 Jul 11 01:06:05 unraid kernel: end_request: I/O error, dev sdg, sector 9663711240 (Errors) Jul 11 01:06:05 unraid kernel: md: disk3 read error, sector=9663711176 (Errors) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] Device not ready (Drive related) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: Result: hostbyte=0x00 driverbyte=0x08 (System) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: Sense Key : 0x2 [current] Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: ASC=0x4 ASCQ=0x0 Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] CDB: (Drive related) Jul 11 01:06:16 unraid kernel: cdb[0]=0x8a: 8a 08 00 00 00 02 40 00 88 08 00 00 00 08 00 00 Jul 11 01:06:16 unraid kernel: end_request: I/O error, dev sdg, sector 9663711240 (Errors) Jul 11 01:06:16 unraid kernel: md: disk3 write error, sector=9663711176 (Errors) Jul 11 01:06:16 unraid kernel: md: recovery thread woken up ... (unRAID engine) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] Device not ready (Drive related) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: Result: hostbyte=0x00 driverbyte=0x08 (System) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: Sense Key : 0x2 [current] Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: ASC=0x4 ASCQ=0x0 Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] CDB: (Drive related) Jul 11 01:06:16 unraid kernel: cdb[0]=0x88: 88 00 00 00 00 02 47 54 0e a0 00 00 00 08 00 00 Jul 11 01:06:16 unraid kernel: end_request: I/O error, dev sdg, sector 9786625696 (Errors) Jul 11 01:06:16 unraid kernel: md: disk3 read error, sector=9786625632 (Errors) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] Device not ready (Drive related) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: Result: hostbyte=0x00 driverbyte=0x08 (System) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: Sense Key : 0x2 [current] Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: ASC=0x4 ASCQ=0x0 Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] CDB: (Drive related) Jul 11 01:06:16 unraid kernel: cdb[0]=0x88: 88 00 00 00 00 02 47 23 86 30 00 00 00 08 00 00 Jul 11 01:06:16 unraid kernel: end_request: I/O error, dev sdg, sector 9783445040 (Errors) Jul 11 01:06:16 unraid kernel: md: disk3 read error, sector=9783444976 (Errors) Jul 11 01:06:16 unraid kernel: md: recovery thread has nothing to resync (unRAID engine) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] Device not ready (Drive related) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: Result: hostbyte=0x00 driverbyte=0x08 (System) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: Sense Key : 0x2 [current] Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: ASC=0x4 ASCQ=0x0 Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] CDB: (Drive related) Jul 11 01:06:16 unraid kernel: cdb[0]=0x8a: 8a 08 00 00 00 02 47 54 0e a0 00 00 00 08 00 00 Jul 11 01:06:16 unraid kernel: end_request: I/O error, dev sdg, sector 9786625696 (Errors) Jul 11 01:06:16 unraid kernel: md: disk3 write error, sector=9786625632 (Errors) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] Device not ready (Drive related) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: Result: hostbyte=0x00 driverbyte=0x08 (System) Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: Sense Key : 0x2 [current] Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] (Drive related) Jul 11 01:06:16 unraid kernel: ASC=0x4 ASCQ=0x0 Jul 11 01:06:16 unraid kernel: sd 1:0:1:0: [sdg] CDB: (Drive related) Jul 11 01:06:16 unraid kernel: cdb[0]=0x8a: 8a 08 00 00 00 02 47 23 86 30 00 00 00 08 00 00 Jul 11 01:06:16 unraid kernel: end_request: I/O error, dev sdg, sector 9783445040 (Errors) Jul 11 01:06:16 unraid kernel: md: disk3 write error, sector=9783444976 (Errors) Device Model: WDC WD60EFRX-68MYMN1 LU WWN Device Id: 5 0014ee 2b5aeca78 Firmware Version: 82.00A82 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5700 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Wed Jul 15 00:49:27 2015 SGT SMART support is: Available - device has SMART capability. SMART support is: Enabled 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 228 200 021 Pre-fail Always - 7558 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 680 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 092 092 000 Old_age Always - 6554 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 - 33 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1493 194 Temperature_Celsius 0x0022 115 111 000 Old_age Always - 37 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 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Quote Link to comment
RobJ Posted July 14, 2015 Share Posted July 14, 2015 The SMART report looks fine, the Power-Off_Retract_Count VALUE is 200 which is perfect. This doesn't look like a drive problem, but a controller problem. The drive spun down fine, but then could not respond. It's not the first time we have seen similar behavior with SAS controllers using the mpt2sas module. Try updating the firmware for that controller. Perhaps others will have more ideas ... Edit: Also, I see this is in the v5 support section. You really should consider upgrading to v6, which will have upgraded drivers. Edit2: And changing to a v6 Docker for Plex should stop those segfaults in Plex. Quote Link to comment
Shunz Posted July 15, 2015 Author Share Posted July 15, 2015 Thanks Rob! I'm using a Supermicro X10SL7-F with an LSI 2308 SAS controller. There doesn't seem to be any firmware updates for the controller, but the board bios is up to date. Oh wow - I'm only reading it now - unRaid v6 has been officially stable since last month! Woohoo!!! Was waiting for that for a while! I'm gonna take some time to read up on v6 and the upgrading methods soon. The disk rebuild should take another half a day. Should I RMA this other WD Red? It is the previous drive that failed, and it is now unused. After taking notice of the UDMA_CRC_Error_Count, I've already replaced ALL SATA cables with short ones. === START OF INFORMATION SECTION === Device Model: WDC WD60EFRX-68MYMN1 LU WWN Device Id: 5 0014ee 20b26f3dc Firmware Version: 82.00A82 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5700 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Wed Jul 15 10:56:30 2015 SGT 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 4424) 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: ( 698) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303d) 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 - 0 3 Spin_Up_Time 0x0027 217 187 021 Pre-fail Always - 8108 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 498 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 094 094 000 Old_age Always - 4965 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 - 11 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 0 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1045 194 Temperature_Celsius 0x0022 116 110 000 Old_age Always - 36 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 170 000 Old_age Always - 3261 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 without error 00% 4295 - # 2 Short offline Completed without error 00% 4283 - # 3 Short offline Completed without error 00% 4283 - # 4 Extended offline Aborted by host 90% 4283 - 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. Quote Link to comment
SSD Posted July 15, 2015 Share Posted July 15, 2015 The CRC errors are typically caused by a cabling problem which can and will cause disks to red ball. In fact this is the most common reason that disks are kicked from arrays. If you have fixed that problem, the drive should be fine. Note that the CRC errors will never reduce, they should just not continue to rise. Quote Link to comment
RobJ Posted July 15, 2015 Share Posted July 15, 2015 Should I RMA this other WD Red? It is the previous drive that failed, and it is now unused. After taking notice of the UDMA_CRC_Error_Count, I've already replaced ALL SATA cables with short ones. Drive looks great, practically brand new, nothing 'failed' about it. Quote Link to comment
Shunz Posted July 15, 2015 Author Share Posted July 15, 2015 Thanks Rob, bjp999!! I guess I really need to take a good look at v6 soon...! Quote Link to comment
Shunz Posted July 15, 2015 Author Share Posted July 15, 2015 Did a quick read-through of the massive v6 upgrading guide and the v6 manual. Fwaaah! Some really amazing and long-awaited improvements - better file systems, streamlining (v5 feels generally patchwork by comparison), and dockers are probably my favorite ones right now. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.