September 12, 201213 yr Hello! I've been doing some cleaning-up on my array moving/deleting files when this happened: Sep 12 08:22:19 Tower login[14171]: ROOT LOGIN on `pts/0' from `192.168.1.194' (Logins) Sep 12 08:33:42 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:42 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:42 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:42 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:42 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:42 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:42 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:42 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:42 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:45 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:45 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:45 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:45 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:45 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:45 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:45 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:45 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:45 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:47 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:47 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:47 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:47 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:47 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:47 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:47 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:47 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:47 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:50 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:50 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:50 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:50 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:50 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:50 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:50 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:50 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:50 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:53 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:53 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:53 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:53 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:53 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:53 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:53 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:53 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:53 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:56 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Sep 12 08:33:56 Tower kernel: ata5.00: irq_stat 0x40000001 (Drive related) Sep 12 08:33:56 Tower kernel: ata5.00: failed command: READ DMA (Minor Issues) Sep 12 08:33:56 Tower kernel: ata5.00: cmd c8/00:b8:8f:9b:00/00:00:00:00:00/e0 tag 0 dma 94208 in (Drive related) Sep 12 08:33:56 Tower kernel: res 51/40:a7:9f:9b:00/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Sep 12 08:33:56 Tower kernel: ata5.00: status: { DRDY ERR } (Drive related) Sep 12 08:33:56 Tower kernel: ata5.00: error: { UNC } (Errors) Sep 12 08:33:56 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Sep 12 08:33:56 Tower kernel: sd 5:0:0:0: [sdf] Unhandled sense code (Drive related) Sep 12 08:33:56 Tower kernel: sd 5:0:0:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08 (System) Sep 12 08:33:56 Tower kernel: sd 5:0:0:0: [sdf] Sense Key : 0x3 [current] [descriptor] (Drive related) Sep 12 08:33:56 Tower kernel: Descriptor sense data with sense descriptors (in hex): Sep 12 08:33:56 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Sep 12 08:33:56 Tower kernel: 00 00 9b 9f Sep 12 08:33:56 Tower kernel: sd 5:0:0:0: [sdf] ASC=0x11 ASCQ=0x4 (Drive related) Sep 12 08:33:56 Tower kernel: sd 5:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 00 00 9b 8f 00 00 b8 00 (Drive related) Sep 12 08:33:56 Tower kernel: end_request: I/O error, dev sdf, sector 39839 (Errors) Sep 12 08:33:56 Tower kernel: ata5: EH complete (Drive related) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39776/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39784/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39792/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39800/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39808/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39816/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39824/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39832/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39840/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39848/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39856/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39864/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39872/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39880/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39888/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39896/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39904/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39912/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39920/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39928/1, count: 1 (Errors) Sep 12 08:33:56 Tower kernel: md: disk1 read error (Errors) Sep 12 08:33:56 Tower kernel: handle_stripe read error: 39936/1, count: 1 (Errors) Should I be worried about this HDD? I've done short smart test with this result: smartctl -a -d ata /dev/sdf smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA1279668 Firmware Version: 51.0AB51 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: Wed Sep 12 09:22:28 2012 CEST 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (38160) 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 171 167 021 Pre-fail Always - 6416 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1557 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 079 079 000 Old_age Always - 15541 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 - 56 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 16 193 Load_Cycle_Count 0x0032 197 197 000 Old_age Always - 11308 194 Temperature_Celsius 0x0022 114 109 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 200 200 000 Old_age Offline - 2 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 - 2 SMART Error Log Version: 1 ATA Error Count: 6 (device log contains only the most recent five errors) 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 6 occurred at disk power-on lifetime: 15540 hours (647 days + 12 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 b8 9f 9b 00 e0 Error: UNC 184 sectors at LBA = 0x00009b9f = 39839 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 b8 8f 9b 00 e0 08 31d+16:09:43.324 READ DMA ef 10 02 00 00 00 a0 08 31d+16:09:43.324 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 31d+16:09:43.320 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 31d+16:09:43.320 SET FEATURES [set transfer mode] Error 5 occurred at disk power-on lifetime: 15540 hours (647 days + 12 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 b8 9f 9b 00 e0 Error: UNC 184 sectors at LBA = 0x00009b9f = 39839 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 b8 8f 9b 00 e0 08 31d+16:09:40.567 READ DMA ef 10 02 00 00 00 a0 08 31d+16:09:40.567 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 31d+16:09:40.563 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 31d+16:09:40.563 SET FEATURES [set transfer mode] Error 4 occurred at disk power-on lifetime: 15540 hours (647 days + 12 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 b8 9f 9b 00 e0 Error: UNC 184 sectors at LBA = 0x00009b9f = 39839 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 b8 8f 9b 00 e0 08 31d+16:09:37.809 READ DMA ef 10 02 00 00 00 a0 08 31d+16:09:37.809 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 31d+16:09:37.805 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 31d+16:09:37.805 SET FEATURES [set transfer mode] Error 3 occurred at disk power-on lifetime: 15540 hours (647 days + 12 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 b8 9f 9b 00 e0 Error: UNC 184 sectors at LBA = 0x00009b9f = 39839 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 b8 8f 9b 00 e0 08 31d+16:09:35.052 READ DMA ef 10 02 00 00 00 a0 08 31d+16:09:35.052 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 31d+16:09:35.048 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 31d+16:09:35.048 SET FEATURES [set transfer mode] Error 2 occurred at disk power-on lifetime: 15540 hours (647 days + 12 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 b8 9f 9b 00 e0 Error: UNC 184 sectors at LBA = 0x00009b9f = 39839 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 b8 8f 9b 00 e0 08 31d+16:09:32.295 READ DMA ef 10 02 00 00 00 a0 08 31d+16:09:32.295 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 31d+16:09:32.291 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 31d+16:09:32.291 SET FEATURES [set transfer mode] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 15541 - 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. What do these errors mean? Is it OK to use this drive or should I replace it? Is my data safe? I'm not sure but I think "at disk power-on lifetime: 15540 hours (647 days + 12 hours)" I was deleting files from this HDD (don't know if that even matters). Please advise.
September 12, 201213 yr Replace asap. Then can run a preclear on it to see if it will still run safely. Check warranty and rma if possible (and failed preclear) Sent from my SGH-I727R using Tapatalk 2
September 12, 201213 yr Your disk reported a "media error" (UNC Error) Basically, a sector where the data on it did not match the checksum at the end of that same sector. It tried multiple times to read it, but failed. It eventually reported the "read" failure to unRAID. That resulted in the "read stripe error" unRAID, in response, read all your other disks and re-constructed the data that was on the bad sector. That was then used in your file deletion operation to keep the directory entries correct. In addition, that same correct data was written to the un-readable sector. That seems to have been re-written, in place, and was successful by the disk. (It would have marked the sector as pending re-allocation, but your SMART report shows no sectors as pending re-allocation, nor any re-allocated.) Basically, the issue is corrected. Keep an eye out for future errors. Run a non-correcting parity check. It should find and fix any additional un-readable sectors. I do not think the disk needs to be replaced. The "short" test you performed completed without errors. # 1 Short offline Completed without error 00% 15541 Joe L.
September 12, 201213 yr Author Thank you both! I'll watch this drive closely and as soon as get some money I'll buy replacement and preclear the old one at least 3 times to check if I can keep using it in my unRAID.
Archived
This topic is now archived and is closed to further replies.