September 15, 201213 yr Sep 15 03:50:14 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Sep 15 03:50:14 Tower kernel: ata3.00: failed command: SMART (Minor Issues) Sep 15 03:50:14 Tower kernel: ata3.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Sep 15 03:50:14 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Sep 15 03:50:14 Tower kernel: ata3.00: status: { DRDY } (Drive related) Sep 15 03:50:14 Tower kernel: ata3: hard resetting link (Minor Issues) Sep 15 03:50:15 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Sep 15 03:50:15 Tower kernel: ata3.00: configured for UDMA/133 (Drive related) Sep 15 03:50:15 Tower kernel: ata3: EH complete (Drive related) this seems to pop up when the mover is running, which i guess is the only time i write to the array since all shares use cache disk. 5.0-rc5-r8168 3 data drives, 1 parity. ata3 = disk1 = sdd = WD30EZRS synccheck on Sept 1 completed without errors and in normal timeframe.
September 16, 201213 yr Author smartctl -a -d ata /dev/sdd (disk1) 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 === Device Model: WDC WD30EZRS-00J99B0 Serial Number: WD-WCAWZ0399187 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,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: Sun Sep 16 10:41:10 2012 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: (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: (50160) 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 149 148 021 Pre-fail Always - 9525 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 56 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 100 100 000 Old_age Always - 671 10 Spin_Retry_Count 0x0032 100 253 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 - 14 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 9 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 68 194 Temperature_Celsius 0x0022 128 110 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 - 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.
September 16, 201213 yr Drive looks good. That leaves everything else . Things to try in no particular order: Power, SATA, backplane. Replace and/or move the SATA connection. Check the power connection. Replace any power splitters.
September 16, 201213 yr Author the sync check passed with 0 errors, at an average of 78MB/sec. what is this error exactly? it says smart error which tells me its not i/o or mechanical related. if a few smart commands dont work is it the end of the world?
September 16, 201213 yr It's not. And if it's not causing any performance or function problems then don't worry about it. I'd keep an eye on it. Is this the cache drive? Is the array written only by the mover?
September 17, 201213 yr Author its disk1 actually, and this occurs when the mover ran the last couple of nights, but not last night, or any other time before. i have been moving a lot of data lately though. performance is still normal and no other issues happening. will monitor.
September 22, 201213 yr Author well it happened again during mover (remember all shares use cache so mover is the only thing that writes to the actual array). one time this happened it was copying a movie from cache to disk1. i recently watched said movie and it had freezes in it which i have never had before. i think this corrupted the file during move. what a pita, this is a newly returned rma'd WD drive.
September 26, 201213 yr Author well, i've narrowed this to either a bad mobo sata port or a bad slot in my 6month old IcyDock 3-in-2. will test with a spare drive to narrow it down, would hate to lose either, but would rather have a bad slot in the icydock then a dead mobo port
September 29, 201213 yr You have already had good advice, but I'll just add a comment. I've never seen this error before, and have to say it's rather uninformative! There are a number of SMART commands, and we are not told which one failed, or whether it was the act of trying to communicate with the drive's SMART system that failed. There is no error return here, and all other flags are zero, no issue indicated. All we know therefore is that some command related to SMART took too long to respond! I would ignore it, unless you see or suspect something wrong. Since you do have some suspicions about transfer corruption, I would either try some CRC or similar checks, on source and destination files, or if you have some experience with DOS, try using the FC command, or other file compare tool.
September 30, 201213 yr Author It for sure screwed up data because one of the movies was skipping / freezing. tracing it back shows this error happened during copy of that movie. it happened again the other night. but with a twist.... Sep 29 06:55:59 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Sep 29 06:55:59 Tower kernel: ata4.00: failed command: IDENTIFY DEVICE (Minor Issues) Sep 29 06:55:59 Tower kernel: ata4.00: cmd ec/00:00:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Sep 29 06:55:59 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) Sep 29 06:55:59 Tower kernel: ata4.00: status: { DRDY } (Drive related) Sep 29 06:55:59 Tower kernel: ata4: hard resetting link (Minor Issues) Sep 29 06:56:00 Tower kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related) Sep 29 06:56:00 Tower kernel: ata4.00: configured for UDMA/33 (Drive related) Sep 29 06:56:00 Tower kernel: ata4: EH complete (Drive related) IDENTIFY DEVICE....i've read this is bad.. RMA already started. only happens during writing operations to the drive too. drive was on a different mobo port, diff cable, diff slot in hot swap bay so its definitely the drive. so atleast i didnt lose a slot/port after all!
September 30, 201213 yr Author well, turns out ATA4 is the parity drive really frustrated with the lack of quality from some parts (either WD, IcyDock). also, unRAID needs to better cross reference ata#, sdx, diskx, mdx for end users to make diagnostics easier.
September 30, 201213 yr This should help: http://www.phuket-data-wizards.com/blog/2011/07/16/matching-linux-ata-numbers-to-the-device-names/
October 1, 201213 yr Author thanks, I'll play around with that tonight when i get home. regardless though, unRAID is all about DATA and DRIVES, it should really handle errors more gracefully. Perhaps a plugin called DriveDiag is needed for all these tools/tricks, etc... if I had the skills / time i'd do it, but i dont. i discovered what drive it was by stopping the array cleanly, then powering off the drive via the IcyDock cage and inspect the syslog for messages. when i powered off the bottom cage (parity slot) ATA4 errors popped up.
October 1, 201213 yr There is a linux app that will do this with pretty output. Its been requested for inclusion in the nest release
April 19, 201313 yr There is a linux app that will do this with pretty output. Its been requested for inclusion in the nest release Did anything happen with this? It would be helpful.
Archived
This topic is now archived and is closed to further replies.