April 1, 201214 yr Subsequent to my previous post about having 2 errors during a parity check, I noticed the following errors in my syslog, just above the parity check. I'm posting this seperately because I dont think they are related. Mar 31 14:45:04 TODD-Svr kernel: ata11.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0 (Errors) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: irq_stat 0x40000008 (Drive related) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: cmd 60/00:00:00:69:2e/01:00:95:00:00/40 tag 0 ncq 131072 in (Drive related) Mar 31 14:45:04 TODD-Svr kernel: res 51/40:5d:a3:69:2e/20:00:95:00:00/40 Emask 0x409 (media error) <F> (Errors) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: status: { DRDY ERR } (Drive related) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: error: { UNC } (Errors) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: configured for UDMA/133 (Drive related) Mar 31 14:45:04 TODD-Svr kernel: ata11: EH complete (Drive related) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0 (Errors) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: irq_stat 0x40000008 (Drive related) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: cmd 60/00:08:00:69:2e/01:00:95:00:00/40 tag 1 ncq 131072 in (Drive related) Mar 31 14:45:07 TODD-Svr kernel: res 51/40:5d:a3:69:2e/20:00:95:00:00/40 Emask 0x409 (media error) <F> (Errors) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: status: { DRDY ERR } (Drive related) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: error: { UNC } (Errors) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: configured for UDMA/133 (Drive related) Mar 31 14:45:07 TODD-Svr kernel: ata11: EH complete (Drive related) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 (Errors) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: irq_stat 0x40000008 (Drive related) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: cmd 60/00:00:00:69:2e/01:00:95:00:00/40 tag 0 ncq 131072 in (Drive related) Mar 31 14:45:10 TODD-Svr kernel: res 51/40:5d:a3:69:2e/20:00:95:00:00/40 Emask 0x409 (media error) <F> (Errors) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: status: { DRDY ERR } (Drive related) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: error: { UNC } (Errors) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: configured for UDMA/133 (Drive related) Mar 31 14:45:10 TODD-Svr kernel: ata11: EH complete (Drive related) I have two preclear operations running that are nearing the end of their cycle. One is for a drive I replaced a week ago due to an error and sector reallocation, so running pre-clear to test the drive. I "think" ata11 is that drive but not sure how to verify. I have 10 drives in my array including parity, so these drives are 11 and 12 in the list, and that specific drive is the 11th on the list. Can anyone help me with what the errors in the syslog mean, and how do I confirm it the drive I was concerned is bad anyway? This is already showing up in the mymain / smartview screen: » reallocated_sector_ct=1 » reallocated_event_count=1 » ata_error_count=5
April 1, 201214 yr Subsequent to my previous post about having 2 errors during a parity check, I noticed the following errors in my syslog, just above the parity check. I'm posting this seperately because I dont think they are related. Mar 31 14:45:04 TODD-Svr kernel: ata11.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0 (Errors) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: irq_stat 0x40000008 (Drive related) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: cmd 60/00:00:00:69:2e/01:00:95:00:00/40 tag 0 ncq 131072 in (Drive related) Mar 31 14:45:04 TODD-Svr kernel: res 51/40:5d:a3:69:2e/20:00:95:00:00/40 Emask 0x409 (media error) <F> (Errors) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: status: { DRDY ERR } (Drive related) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: error: { UNC } (Errors) Mar 31 14:45:04 TODD-Svr kernel: ata11.00: configured for UDMA/133 (Drive related) Mar 31 14:45:04 TODD-Svr kernel: ata11: EH complete (Drive related) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0 (Errors) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: irq_stat 0x40000008 (Drive related) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: cmd 60/00:08:00:69:2e/01:00:95:00:00/40 tag 1 ncq 131072 in (Drive related) Mar 31 14:45:07 TODD-Svr kernel: res 51/40:5d:a3:69:2e/20:00:95:00:00/40 Emask 0x409 (media error) <F> (Errors) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: status: { DRDY ERR } (Drive related) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: error: { UNC } (Errors) Mar 31 14:45:07 TODD-Svr kernel: ata11.00: configured for UDMA/133 (Drive related) Mar 31 14:45:07 TODD-Svr kernel: ata11: EH complete (Drive related) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 (Errors) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: irq_stat 0x40000008 (Drive related) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: cmd 60/00:00:00:69:2e/01:00:95:00:00/40 tag 0 ncq 131072 in (Drive related) Mar 31 14:45:10 TODD-Svr kernel: res 51/40:5d:a3:69:2e/20:00:95:00:00/40 Emask 0x409 (media error) <F> (Errors) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: status: { DRDY ERR } (Drive related) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: error: { UNC } (Errors) Mar 31 14:45:10 TODD-Svr kernel: ata11.00: configured for UDMA/133 (Drive related) Mar 31 14:45:10 TODD-Svr kernel: ata11: EH complete (Drive related) I have two preclear operations running that are nearing the end of their cycle. One is for a drive I replaced a week ago due to an error and sector reallocation, so running pre-clear to test the drive. I "think" ata11 is that drive but not sure how to verify. I have 10 drives in my array including parity, so these drives are 11 and 12 in the list, and that specific drive is the 11th on the list. Can anyone help me with what the errors in the syslog mean, and how do I confirm it the drive I was concerned is bad anyway? This is already showing up in the mymain / smartview screen: » reallocated_sector_ct=1 » reallocated_event_count=1 » ata_error_count=5 Impossible to help you without the full syslog. The posted segment is useless without the rest. Attach a zipped full syslog to your next post.
April 1, 201214 yr Author Impossible to help you without the full syslog. The posted segment is useless without the rest. Attach a zipped full syslog to your next post. Here it is, thanks. syslog-2012-04-01.txt
April 1, 201214 yr Author The disk I was pre-clearing over a concern with an error completed since posting the syslog. This is a 2nd log dump post completion of that drive's preclear. It shows a lot of red lines in the unmenu syslog at the end of the preclear. Other than reallocating the one sector, I don's see anything bad at the end of the preclear, but not sure what the log is saying here. syslog-2012-04-01_1.txt
April 1, 201214 yr Author Here are the results of a short smart test on that drive. Would you use this or keep it for a spare? SMART status Info for /dev/sdl 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 === Model Family: Hitachi Deskstar 7K2000 Device Model: Hitachi HDS722020ALA330 Serial Number: JK1174YAHLZZWW Firmware Version: JKAOA28A 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: ATA-8-ACS revision 4 Local Time is: Sun Apr 1 11:56:20 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: (0x85) Offline data collection activity was aborted 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: (20567) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. SCT capabilities: (0x003d) 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 0x000b 099 099 016 Pre-fail Always - 3 2 Throughput_Performance 0x0005 135 135 054 Pre-fail Offline - 95 3 Spin_Up_Time 0x0007 178 178 024 Pre-fail Always - 463 (Average 348) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 895 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 1 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 110 110 020 Pre-fail Offline - 40 9 Power_On_Hours 0x0012 098 098 000 Old_age Always - 16071 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 378 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1033 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1033 194 Temperature_Celsius 0x0002 166 166 000 Old_age Always - 36 (Lifetime Min/Max 16/63) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 1 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 5 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 5 occurred at disk power-on lifetime: 16050 hours (668 days + 18 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 5d a3 69 2e 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 00 69 2e 40 08 5d+12:22:12.864 READ FPDMA QUEUED ef 10 02 00 00 00 a0 08 5d+12:22:12.863 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 08 5d+12:22:12.862 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 5d+12:22:12.852 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 5d+12:22:12.851 SET FEATURES [set transfer mode] Error 4 occurred at disk power-on lifetime: 16050 hours (668 days + 18 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 5d a3 69 2e 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 00 69 2e 40 08 5d+12:21:56.080 READ FPDMA QUEUED 60 00 00 00 6a 2e 40 08 5d+12:21:56.080 READ FPDMA QUEUED ef 10 02 00 00 00 a0 08 5d+12:21:56.078 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 08 5d+12:21:56.077 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 5d+12:21:56.068 IDENTIFY DEVICE Error 3 occurred at disk power-on lifetime: 16050 hours (668 days + 18 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 5d a3 69 2e 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 00 6a 2e 40 08 5d+12:21:39.381 READ FPDMA QUEUED 60 00 00 00 69 2e 40 08 5d+12:21:39.375 READ FPDMA QUEUED 60 00 08 00 68 2e 40 08 5d+12:21:39.374 READ FPDMA QUEUED 60 00 00 00 67 2e 40 08 5d+12:21:39.368 READ FPDMA QUEUED 60 00 08 00 66 2e 40 08 5d+12:21:39.361 READ FPDMA QUEUED Error 2 occurred at disk power-on lifetime: 16045 hours (668 days + 13 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 5d a3 69 2e 00 Error: UNC 93 sectors at LBA = 0x002e69a3 = 3041699 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 00 68 2e e5 00 4d+07:46:09.671 READ DMA EXT 25 00 00 00 66 2e e5 00 4d+07:46:09.659 READ DMA EXT 25 00 00 00 64 2e e5 00 4d+07:46:09.646 READ DMA EXT 25 00 00 00 62 2e e5 00 4d+07:46:09.582 READ DMA EXT 25 00 00 00 60 2e e5 00 4d+07:46:09.561 READ DMA EXT Error 1 occurred at disk power-on lifetime: 16021 hours (667 days + 13 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 04 a3 69 2e 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 a7 68 2e 40 00 48d+01:28:06.691 READ FPDMA QUEUED 60 00 00 a7 66 2e 40 00 48d+01:28:06.684 READ FPDMA QUEUED 60 00 00 a7 64 2e 40 00 48d+01:28:06.677 READ FPDMA QUEUED 60 00 00 a7 62 2e 40 00 48d+01:28:06.669 READ FPDMA QUEUED 60 00 00 a7 61 2e 40 00 48d+01:28:06.623 READ FPDMA QUEUED 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% 16071 - # 2 Short offline Completed without error 00% 16018 - # 3 Short offline Completed without error 00% 16018 - # 4 Short offline Completed without error 00% 15196 - # 5 Short offline Completed without error 00% 10879 - # 6 Short offline Completed without error 00% 10879 - # 7 Short offline Completed without error 00% 10878 - # 8 Short offline Completed without error 00% 10878 - # 9 Short offline Completed without error 00% 10876 - #10 Short offline Completed without error 00% 10876 - #11 Short offline Completed without error 00% 10876 - #12 Short offline Completed without error 00% 10876 - #13 Short offline Completed without error 00% 12 - 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.
April 6, 201214 yr Author Any thoughts on whether or not this drive is safe or definitely not safe? I was thinking of using it in a non critical application.
April 7, 201214 yr Author The drive looks ok. Just keep an eye on the Current_Pending_Sector value. Thanks
Archived
This topic is now archived and is closed to further replies.