cyrnel Posted April 7, 2011 Share Posted April 7, 2011 This is a Dell SC440, unRAID pro 4.7, 5 data drives, one parity, one cache. I started Crashplan on it yesterday but there haven't been any hardware changes for the last week when I installed a larger cache drive. Syslog of boot attached. Things have been working great, other than my own split/minfree errors last week. Then yesterday I started to notice odd performance. Put it down to the tests I was running on backup software. Today I notice //tower shows everything green but my parity drive has 126 errors. (last parity check 5 days ago with zero errors) I believe this is the first time I've seen anything but zeroes in that error column. Syslog for today looks normal but yesterday has bad clowns: ------------------- Apr 6 12:46:36 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Apr 6 12:46:36 Tower kernel: ata5.00: BMDMA stat 0x65 (Drive related) Apr 6 12:46:36 Tower kernel: ata5.00: failed command: READ DMA EXT (Minor Issues) Apr 6 12:46:36 Tower kernel: ata5.00: cmd 25/00:00:a0:bd:90/00:04:cd:00:00/e0 tag 0 dma 524288 in (Drive related) Apr 6 12:46:36 Tower kernel: res 51/40:cf:c0:bd:90/40:03:cd:00:00/e0 Emask 0x9 (media error) (Errors) Apr 6 12:46:36 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Apr 6 12:46:36 Tower kernel: ata5.00: error: { UNC } (Errors) Apr 6 12:46:36 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Apr 6 12:46:36 Tower kernel: ata5.01: configured for UDMA/133 (Drive related) Apr 6 12:46:36 Tower kernel: ata5: EH complete (Drive related) Apr 6 12:46:38 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Apr 6 12:46:38 Tower kernel: ata5.00: BMDMA stat 0x65 (Drive related) Apr 6 12:46:38 Tower kernel: ata5.00: failed command: READ DMA EXT (Minor Issues) Apr 6 12:46:38 Tower kernel: ata5.00: cmd 25/00:00:a0:bd:90/00:04:cd:00:00/e0 tag 0 dma 524288 in (Drive related) Apr 6 12:46:38 Tower kernel: res 51/40:df:b0:bd:90/40:03:cd:00:00/e0 Emask 0x9 (media error) (Errors) Apr 6 12:46:38 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Apr 6 12:46:38 Tower kernel: ata5.00: error: { UNC } (Errors) Apr 6 12:46:38 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Apr 6 12:46:38 Tower kernel: ata5.01: configured for UDMA/133 (Drive related) Apr 6 12:46:38 Tower kernel: ata5: EH complete (Drive related) Apr 6 12:46:41 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Apr 6 12:46:41 Tower kernel: ata5.00: BMDMA stat 0x65 (Drive related) Apr 6 12:46:41 Tower kernel: ata5.00: failed command: READ DMA EXT (Minor Issues) Apr 6 12:46:41 Tower kernel: ata5.00: cmd 25/00:00:a0:bd:90/00:04:cd:00:00/e0 tag 0 dma 524288 in (Drive related) Apr 6 12:46:41 Tower kernel: res 51/40:df:b0:bd:90/40:03:cd:00:00/e0 Emask 0x9 (media error) (Errors) Apr 6 12:46:41 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Apr 6 12:46:41 Tower kernel: ata5.00: error: { UNC } (Errors) Apr 6 12:46:41 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Apr 6 12:46:41 Tower kernel: ata5.01: configured for UDMA/133 (Drive related) Apr 6 12:46:41 Tower kernel: ata5: EH complete (Drive related) Apr 6 12:46:44 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Apr 6 12:46:44 Tower kernel: ata5.00: BMDMA stat 0x65 (Drive related) Apr 6 12:46:44 Tower kernel: ata5.00: failed command: READ DMA EXT (Minor Issues) Apr 6 12:46:44 Tower kernel: ata5.00: cmd 25/00:00:a0:bd:90/00:04:cd:00:00/e0 tag 0 dma 524288 in (Drive related) Apr 6 12:46:44 Tower kernel: res 51/40:df:b0:bd:90/40:03:cd:00:00/e0 Emask 0x9 (media error) (Errors) Apr 6 12:46:44 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Apr 6 12:46:44 Tower kernel: ata5.00: error: { UNC } (Errors) Apr 6 12:46:44 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Apr 6 12:46:44 Tower kernel: ata5.01: configured for UDMA/133 (Drive related) Apr 6 12:46:44 Tower kernel: ata5: EH complete (Drive related) Apr 6 12:46:46 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Apr 6 12:46:46 Tower kernel: ata5.00: BMDMA stat 0x65 (Drive related) Apr 6 12:46:46 Tower kernel: ata5.00: failed command: READ DMA EXT (Minor Issues) Apr 6 12:46:46 Tower kernel: ata5.00: cmd 25/00:00:a0:bd:90/00:04:cd:00:00/e0 tag 0 dma 524288 in (Drive related) Apr 6 12:46:46 Tower kernel: res 51/40:df:b0:bd:90/40:03:cd:00:00/e0 Emask 0x9 (media error) (Errors) Apr 6 12:46:46 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Apr 6 12:46:46 Tower kernel: ata5.00: error: { UNC } (Errors) Apr 6 12:46:46 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Apr 6 12:46:46 Tower kernel: ata5.01: configured for UDMA/133 (Drive related) Apr 6 12:46:46 Tower kernel: ata5: EH complete (Drive related) Apr 6 12:46:49 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Apr 6 12:46:49 Tower kernel: ata5.00: BMDMA stat 0x65 (Drive related) Apr 6 12:46:49 Tower kernel: ata5.00: failed command: READ DMA EXT (Minor Issues) Apr 6 12:46:49 Tower kernel: ata5.00: cmd 25/00:00:a0:bd:90/00:04:cd:00:00/e0 tag 0 dma 524288 in (Drive related) Apr 6 12:46:49 Tower kernel: res 51/40:df:b0:bd:90/40:03:cd:00:00/e0 Emask 0x9 (media error) (Errors) Apr 6 12:46:49 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Apr 6 12:46:49 Tower kernel: ata5.00: error: { UNC } (Errors) Apr 6 12:46:49 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Apr 6 12:46:49 Tower kernel: ata5.01: configured for UDMA/133 (Drive related) Apr 6 12:46:49 Tower kernel: sd 5:0:0:0: [sde] Unhandled sense code (Drive related) Apr 6 12:46:49 Tower kernel: sd 5:0:0:0: [sde] Result: hostbyte=0x00 driverbyte=0x08 (System) Apr 6 12:46:49 Tower kernel: sd 5:0:0:0: [sde] Sense Key : 0x3 [current] [descriptor] (Drive related) Apr 6 12:46:49 Tower kernel: Descriptor sense data with sense descriptors (in hex): Apr 6 12:46:49 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Apr 6 12:46:49 Tower kernel: cd 90 bd b0 Apr 6 12:46:49 Tower kernel: sd 5:0:0:0: [sde] ASC=0x11 ASCQ=0x4 (Drive related) Apr 6 12:46:49 Tower kernel: sd 5:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 cd 90 bd a0 00 04 00 00 (Drive related) Apr 6 12:46:49 Tower kernel: end_request: I/O error, dev sde, sector 3448815024 (Errors) Apr 6 12:46:49 Tower kernel: ata5: EH complete (Drive related) Apr 6 12:46:49 Tower kernel: md: disk0 read error (Errors) Apr 6 12:46:49 Tower kernel: handle_stripe read error: 3448814960/0, count: 1 (Errors) Apr 6 12:46:49 Tower kernel: md: disk0 read error (Errors) ...last two lines repeat about 100 times with the location value incrementing by 8 each time... --------------- The fact it's only happening on ata5, no smart problems, and sequentially like this makes me scratch my head. Maybe the card? I wanted to get experienced feedback before doing anything. Of course this is just as I'm about to bring up my backup unRAID server. smartctl output for sde: ---------------- smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00J2GB0 Serial Number: WD-WCAYY0004579 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Apr 7 15:40:05 2011 PDT 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: (38760) 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: (0x3031) 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 159 156 021 Pre-fail Always - 9041 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1351 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 089 089 000 Old_age Always - 8359 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 - 22 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 5 193 Load_Cycle_Count 0x0032 165 165 000 Old_age Always - 105255 194 Temperature_Celsius 0x0022 125 114 000 Old_age Always - 27 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 - 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] 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. tower_syslog_boot.txt Quote Link to comment
cyrnel Posted April 8, 2011 Author Share Posted April 8, 2011 NOCORRECT parity check turned up zero problems and the disk errors have remained at 126. Any suggestions, like 100 SMART tests or...? I'd blame the cat if there was some way she could get to that drive. I'll pick up a spare drive today. Quote Link to comment
dgaschk Posted April 9, 2011 Share Posted April 9, 2011 After you replace the drive you could try to pre-clear it and see if it passes. Quote Link to comment
cyrnel Posted April 9, 2011 Author Share Posted April 9, 2011 Thanks. Will do. Nothing messes with confidence quite like an erratic batch of errors. 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.