mike Posted May 11, 2011 Share Posted May 11, 2011 I have Time Machine on my laptop set to back up to an AFP share on disk4. Yesterday I noticed it was backing up very slow so I checked the syslog and saw a ton of errors. I then started a parity check (which is still going, 22 hours later) and the errors are constantly streaming as shown below and on the attached syslog. So far the parity check shows zero sync errors found but the rate is 200KB/sec at 96%. I have done no other troubleshooting, nor know where to start. Please advise. Thanks! May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151256/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151264/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151272/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151280/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151288/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151296/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151304/2, count: 1 May 10 17:45:15 unraid kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 10 17:45:15 unraid kernel: ata1.00: irq_stat 0x40000001 May 10 17:45:15 unraid kernel: ata1.00: failed command: READ DMA EXT May 10 17:45:15 unraid kernel: ata1.00: cmd 25/00:a8:e8:8c:1d/00:02:d2:00:00/e0 tag 0 dma 348160 in May 10 17:45:15 unraid kernel: res 51/40:67:18:8e:1d/00:01:d2:00:00/e0 Emask 0x9 (media error) May 10 17:45:15 unraid kernel: ata1.00: status: { DRDY ERR } May 10 17:45:15 unraid kernel: ata1.00: error: { UNC } May 10 17:45:15 unraid kernel: ata1.00: configured for UDMA/133 May 10 17:45:15 unraid kernel: ata1: EH complete May 10 17:45:18 unraid kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 10 17:45:18 unraid kernel: ata1.00: irq_stat 0x40000001 May 10 17:45:18 unraid kernel: ata1.00: failed command: READ DMA EXT May 10 17:45:18 unraid kernel: ata1.00: cmd 25/00:a8:e8:8c:1d/00:02:d2:00:00/e0 tag 0 dma 348160 in May 10 17:45:18 unraid kernel: res 51/40:97:e8:8c:1d/00:02:d2:00:00/e0 Emask 0x9 (media error) May 10 17:45:18 unraid kernel: ata1.00: status: { DRDY ERR } May 10 17:45:18 unraid kernel: ata1.00: error: { UNC } May 10 17:45:18 unraid kernel: ata1.00: configured for UDMA/133 May 10 17:45:18 unraid kernel: ata1: EH complete syslog-2011-05-10-2.txt.zip Quote Link to comment
prostuff1 Posted May 11, 2011 Share Posted May 11, 2011 get a smart report on the drive so we can see if the drive is failing or not. Also check the cable and power connections to make sure nothing got dislodged. See the troubleshooting link in my sig. Quote Link to comment
Joe L. Posted May 11, 2011 Share Posted May 11, 2011 I have Time Machine on my laptop set to back up to an AFP share on disk4. Yesterday I noticed it was backing up very slow so I checked the syslog and saw a ton of errors. I then started a parity check (which is still going, 22 hours later) and the errors are constantly streaming as shown below and on the attached syslog. So far the parity check shows zero sync errors found but the rate is 200KB/sec at 96%. I have done no other troubleshooting, nor know where to start. Please advise. Thanks! May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151256/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151264/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151272/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151280/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151288/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151296/2, count: 1 May 10 17:45:12 unraid kernel: md: disk4 read error May 10 17:45:12 unraid kernel: handle_stripe read error: 3525151304/2, count: 1 May 10 17:45:15 unraid kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 10 17:45:15 unraid kernel: ata1.00: irq_stat 0x40000001 May 10 17:45:15 unraid kernel: ata1.00: failed command: READ DMA EXT May 10 17:45:15 unraid kernel: ata1.00: cmd 25/00:a8:e8:8c:1d/00:02:d2:00:00/e0 tag 0 dma 348160 in May 10 17:45:15 unraid kernel: res 51/40:67:18:8e:1d/00:01:d2:00:00/e0 Emask 0x9 (media error) May 10 17:45:15 unraid kernel: ata1.00: status: { DRDY ERR } May 10 17:45:15 unraid kernel: ata1.00: error: { UNC } May 10 17:45:15 unraid kernel: ata1.00: configured for UDMA/133 May 10 17:45:15 unraid kernel: ata1: EH complete May 10 17:45:18 unraid kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 10 17:45:18 unraid kernel: ata1.00: irq_stat 0x40000001 May 10 17:45:18 unraid kernel: ata1.00: failed command: READ DMA EXT May 10 17:45:18 unraid kernel: ata1.00: cmd 25/00:a8:e8:8c:1d/00:02:d2:00:00/e0 tag 0 dma 348160 in May 10 17:45:18 unraid kernel: res 51/40:97:e8:8c:1d/00:02:d2:00:00/e0 Emask 0x9 (media error) May 10 17:45:18 unraid kernel: ata1.00: status: { DRDY ERR } May 10 17:45:18 unraid kernel: ata1.00: error: { UNC } May 10 17:45:18 unraid kernel: ata1.00: configured for UDMA/133 May 10 17:45:18 unraid kernel: ata1: EH complete "UNC" media errors are almost always un-readable sectors on the hard disk. A smart report will show sectors pending re-allocation, or sectors already re-allocated, of both. It might just be a few sectors (and on large disks there are usually several thousand spare used for re-allocation) or it might be getting worse over time. smartctl -d ata -a /dev/sdX where sdX = the three letter drive designation for your drive. Quote Link to comment
mike Posted May 11, 2011 Author Share Posted May 11, 2011 Thanks for the troubleshooting link! It looks like I have bad sectors on this drive. I already put in an RMA claim with WD. While I wait for the replacement, is my data at risk? From what I understand, it's okay as long as I don't have another drive failure. root@unraid:/boot# smartctl -a -d ata /dev/sda smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA0043421 Firmware Version: 50.0AB50 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed May 11 17:41:11 2011 EDT 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (36600) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status 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 083 083 051 Pre-fail Always - 61683 3 Spin_Up_Time 0x0027 161 160 021 Pre-fail Always - 6941 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 479 5 Reallocated_Sector_Ct 0x0033 189 189 140 Pre-fail Always - 83 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 3833 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 - 31 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 18 193 Load_Cycle_Count 0x0032 177 177 000 Old_age Always - 69073 194 Temperature_Celsius 0x0022 114 106 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 142 142 000 Old_age Always - 58 197 Current_Pending_Sector 0x0032 197 196 000 Old_age Always - 1193 198 Offline_Uncorrectable 0x0030 200 198 000 Old_age Offline - 151 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 099 000 Old_age Offline - 29 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% 3818 86260408 # 2 Short offline Completed: read failure 70% 3818 3905899488 # 3 Short offline Aborted by host 90% 3818 - # 4 Short offline Completed: read failure 70% 3818 3905899496 # 5 Short offline Completed without error 00% 1443 - 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
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.