shooga Posted March 7, 2013 Share Posted March 7, 2013 Getting these errors over and over again on my cache drive. Can anyone help me understand this? What does this signify? The drive is pretty new, so I'd like to figure out if I should RMA it. Thanks! Mar 6 22:21:24 Bunker kernel: ata4.00: cmd c8/00:08:50:1a:28/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) Mar 6 22:21:24 Bunker kernel: ata4.00: status: { DRDY ERR } (Drive related) Mar 6 22:21:24 Bunker kernel: ata4.00: error: { UNC } (Errors) Mar 6 22:21:30 Bunker kernel: ata4.00: configured for UDMA/100 (Drive related) Mar 6 22:21:30 Bunker kernel: ata4: EH complete (Drive related) Mar 6 22:21:33 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Mar 6 22:21:33 Bunker kernel: ata4.00: BMDMA2 stat 0xc0009 (Drive related) Mar 6 22:21:33 Bunker kernel: ata4.00: failed command: READ DMA (Minor Issues) Mar 6 22:21:33 Bunker kernel: ata4.00: cmd c8/00:08:50:1a:28/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) Mar 6 22:21:33 Bunker kernel: ata4.00: status: { DRDY ERR } (Drive related) Mar 6 22:21:33 Bunker kernel: ata4.00: error: { UNC } (Errors) Mar 6 22:21:39 Bunker kernel: ata4.00: configured for UDMA/100 (Drive related) Mar 6 22:21:39 Bunker kernel: ata4: EH complete (Drive related) Mar 6 22:21:42 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Mar 6 22:21:42 Bunker kernel: ata4.00: BMDMA2 stat 0xc0009 (Drive related) Mar 6 22:21:42 Bunker kernel: ata4.00: failed command: READ DMA (Minor Issues) Mar 6 22:21:42 Bunker kernel: ata4.00: cmd c8/00:08:50:1a:28/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) Mar 6 22:21:42 Bunker kernel: ata4.00: status: { DRDY ERR } (Drive related) Mar 6 22:21:42 Bunker kernel: ata4.00: error: { UNC } (Errors) Mar 6 22:21:48 Bunker kernel: ata4.00: configured for UDMA/100 (Drive related) Mar 6 22:21:48 Bunker kernel: ata4: EH complete (Drive related) Mar 6 22:22:07 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Mar 6 22:22:07 Bunker kernel: ata4.00: BMDMA2 stat 0xc0009 (Drive related) Mar 6 22:22:07 Bunker kernel: ata4.00: failed command: READ DMA (Minor Issues) Mar 6 22:22:07 Bunker kernel: ata4.00: cmd c8/00:08:80:1a:28/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) Mar 6 22:22:07 Bunker kernel: ata4.00: status: { DRDY ERR } (Drive related) Mar 6 22:22:07 Bunker kernel: ata4.00: error: { UNC } (Errors) Mar 6 22:22:12 Bunker kernel: ata4.00: configured for UDMA/100 (Drive related) Mar 6 22:22:12 Bunker kernel: ata4: EH complete (Drive related) Mar 6 22:22:15 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Mar 6 22:22:15 Bunker kernel: ata4.00: BMDMA2 stat 0xc0009 (Drive related) Mar 6 22:22:15 Bunker kernel: ata4.00: failed command: READ DMA (Minor Issues) Mar 6 22:22:15 Bunker kernel: ata4.00: cmd c8/00:08:80:1a:28/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) Mar 6 22:22:15 Bunker kernel: ata4.00: status: { DRDY ERR } (Drive related) Mar 6 22:22:15 Bunker kernel: ata4.00: error: { UNC } (Errors) Link to comment
Joe L. Posted March 7, 2013 Share Posted March 7, 2013 UNC errors are UN-Correctable media errors. It is where the data on a given sector does not match the affiliated checksum on that sector on the disk. The only way to know the health of the drive is to get a SMART report on the drive. smartctl -a /dev/sdX (where sdX = the three letter drive designation for the drive being reported on) Post the results, and we'll be able to provide guidance. Joe L. Link to comment
shooga Posted March 7, 2013 Author Share Posted March 7, 2013 Thanks Joe. What happens to those sectors with the errors? Also, can you recommend a guide to this stuff so I can stop bothering people with my newbie questions? Here's the SMART report: === 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: (16980) 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: ( 196) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) 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 179 179 021 Pre-fail Always - 4033 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 23 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 - 587 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 - 21 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 16 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 6 194 Temperature_Celsius 0x0022 119 113 000 Old_age Always - 28 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. Link to comment
shooga Posted March 7, 2013 Author Share Posted March 7, 2013 Actually, it looks like unMenu was incorrectly mapping syslog entries to the cache drive. In this case ata4 is actually a drive that is failing in a way that even I can understand Think I just need to get rid of this old drive that is failing and I should be all good. Thanks again! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.