June 25, 201115 yr I've seen a couple of occurrences of this recently for ata2. Is it something I should start worrying about, and what's the best thing I can do to check further: Jun 20 03:48:38 The-Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jun 20 03:48:38 The-Vault kernel: ata2.00: BMDMA stat 0x24 Jun 20 03:48:38 The-Vault kernel: ata2.00: failed command: READ DMA EXT Jun 20 03:48:38 The-Vault kernel: ata2.00: cmd 25/00:08:40:00:10/00:00:9a:00:00/e0 tag 0 dma 4096 in Jun 20 03:48:38 The-Vault kernel: res 51/40:00:40:00:10/40:00:9a:00:00/e0 Emask 0x9 (media error) Jun 20 03:48:38 The-Vault kernel: ata2.00: status: { DRDY ERR } Jun 20 03:48:38 The-Vault kernel: ata2.00: error: { UNC } Jun 20 03:48:38 The-Vault kernel: ata2.00: configured for UDMA/133 Jun 20 03:48:38 The-Vault kernel: ata2: EH complete Jun 20 03:48:41 The-Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jun 20 03:48:41 The-Vault kernel: ata2.00: BMDMA stat 0x24 Jun 20 03:48:41 The-Vault kernel: ata2.00: failed command: READ DMA EXT Jun 20 03:48:41 The-Vault kernel: ata2.00: cmd 25/00:08:40:00:10/00:00:9a:00:00/e0 tag 0 dma 4096 in Jun 20 03:48:41 The-Vault kernel: res 51/40:00:40:00:10/40:00:9a:00:00/e0 Emask 0x9 (media error) Jun 20 03:48:41 The-Vault kernel: ata2.00: status: { DRDY ERR } Jun 20 03:48:41 The-Vault kernel: ata2.00: error: { UNC } Jun 20 03:48:41 The-Vault kernel: ata2.00: configured for UDMA/133 Jun 20 03:48:41 The-Vault kernel: ata2: EH complete Jun 20 03:48:44 The-Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jun 20 03:48:44 The-Vault kernel: ata2.00: BMDMA stat 0x24 Jun 20 03:48:44 The-Vault kernel: ata2.00: failed command: READ DMA EXT Jun 20 03:48:44 The-Vault kernel: ata2.00: cmd 25/00:08:40:00:10/00:00:9a:00:00/e0 tag 0 dma 4096 in Jun 20 03:48:44 The-Vault kernel: res 51/40:00:40:00:10/40:00:9a:00:00/e0 Emask 0x9 (media error) Jun 20 03:48:44 The-Vault kernel: ata2.00: status: { DRDY ERR } Jun 20 03:48:44 The-Vault kernel: ata2.00: error: { UNC } Jun 20 03:48:44 The-Vault kernel: ata2.00: configured for UDMA/133 Jun 20 03:48:44 The-Vault kernel: ata2: EH complete Jun 20 03:48:47 The-Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jun 20 03:48:47 The-Vault kernel: ata2.00: BMDMA stat 0x24 Jun 20 03:48:47 The-Vault kernel: ata2.00: failed command: READ DMA EXT Jun 20 03:48:47 The-Vault kernel: ata2.00: cmd 25/00:08:40:00:10/00:00:9a:00:00/e0 tag 0 dma 4096 in Jun 20 03:48:47 The-Vault kernel: res 51/40:00:40:00:10/40:00:9a:00:00/e0 Emask 0x9 (media error) Jun 20 03:48:47 The-Vault kernel: ata2.00: status: { DRDY ERR } Jun 20 03:48:47 The-Vault kernel: ata2.00: error: { UNC } Jun 20 03:48:47 The-Vault kernel: ata2.00: configured for UDMA/133 Jun 20 03:48:47 The-Vault kernel: ata2: EH complete Jun 20 03:48:50 The-Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jun 20 03:48:50 The-Vault kernel: ata2.00: BMDMA stat 0x24 Jun 20 03:48:50 The-Vault kernel: ata2.00: failed command: READ DMA EXT Jun 20 03:48:50 The-Vault kernel: ata2.00: cmd 25/00:08:40:00:10/00:00:9a:00:00/e0 tag 0 dma 4096 in Jun 20 03:48:50 The-Vault kernel: res 51/40:00:40:00:10/40:00:9a:00:00/e0 Emask 0x9 (media error) Jun 20 03:48:50 The-Vault kernel: ata2.00: status: { DRDY ERR } Jun 20 03:48:50 The-Vault kernel: ata2.00: error: { UNC } Jun 20 03:48:50 The-Vault kernel: ata2.00: configured for UDMA/133 Jun 20 03:48:50 The-Vault kernel: ata2: EH complete Jun 20 03:48:54 The-Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jun 20 03:48:54 The-Vault kernel: ata2.00: BMDMA stat 0x24 Jun 20 03:48:54 The-Vault kernel: ata2.00: failed command: READ DMA EXT Jun 20 03:48:54 The-Vault kernel: ata2.00: cmd 25/00:08:40:00:10/00:00:9a:00:00/e0 tag 0 dma 4096 in Jun 20 03:48:54 The-Vault kernel: res 51/40:00:40:00:10/40:00:9a:00:00/e0 Emask 0x9 (media error) Jun 20 03:48:54 The-Vault kernel: ata2.00: status: { DRDY ERR } Jun 20 03:48:54 The-Vault kernel: ata2.00: error: { UNC } Jun 20 03:48:54 The-Vault kernel: ata2.00: configured for UDMA/133 Jun 20 03:48:54 The-Vault kernel: sd 2:0:0:0: [sdc] Unhandled sense code Jun 20 03:48:54 The-Vault kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 Jun 20 03:48:54 The-Vault kernel: sd 2:0:0:0: [sdc] Sense Key : 0x3 [current] [descriptor] Jun 20 03:48:54 The-Vault kernel: Descriptor sense data with sense descriptors (in hex): Jun 20 03:48:54 The-Vault kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Jun 20 03:48:54 The-Vault kernel: 9a 10 00 40 Jun 20 03:48:54 The-Vault kernel: sd 2:0:0:0: [sdc] ASC=0x11 ASCQ=0x4 Jun 20 03:48:54 The-Vault kernel: sd 2:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 9a 10 00 40 00 00 08 00 Jun 20 03:48:54 The-Vault kernel: end_request: I/O error, dev sdc, sector 2584739904 Jun 20 03:48:54 The-Vault kernel: ata2: EH complete Jun 20 03:48:54 The-Vault kernel: md: disk2 read error Jun 20 03:48:54 The-Vault kernel: handle_stripe read error: 2584739840/2, count: 1 I did also see it once, for ata3, but that only spat out one set of messages, and didn't end with the read error messages: Jun 20 11:08:17 The-Vault kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jun 20 11:08:17 The-Vault kernel: ata3.00: BMDMA stat 0x25 Jun 20 11:08:17 The-Vault kernel: ata3.00: failed command: READ DMA EXT Jun 20 11:08:17 The-Vault kernel: ata3.00: cmd 25/00:98:e8:81:be/00:03:99:00:00/e0 tag 0 dma 471040 in Jun 20 11:08:17 The-Vault kernel: res 51/40:97:e4:84:be/40:00:99:00:00/e0 Emask 0x9 (media error) Jun 20 11:08:17 The-Vault kernel: ata3.00: status: { DRDY ERR } Jun 20 11:08:17 The-Vault kernel: ata3.00: error: { UNC } Jun 20 11:08:17 The-Vault kernel: ata3.00: configured for UDMA/133 Jun 20 11:08:17 The-Vault kernel: ata3: EH complete BTW. This is running beta7, and the drives are all WDC_WD20EADS. Cheers.
June 25, 201115 yr disk2 has reported some un-readable sectors which it is reporting as: UNC (un-correctable media errors) Get a smart report for disk2. It will let you know of the health of the drive. smartctl -a /dev/sdc Odds are you'll see some re-allocated sectors, or sectors pending re-allocation. Did you pre-clear that disk using the preclear_disk.sh script? (just curious)
June 25, 201115 yr Author No, unfortunately I didn't run preclear. root@The-Vault:~# smartctl -a /dev/sdc 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 === Model Family: Western Digital Caviar Green family Device Model: WDC WD20EADS-00S2B0 Serial Number: WD-WCAVY0364634 Firmware Version: 04.05G04 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: Exact ATA specification draft version not indicated Local Time is: Sat Jun 25 12:18:25 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: (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: (43500) 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: (0x303f) SCT Status supported. SCT Error Recovery Control 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 162 147 021 Pre-fail Always - 8891 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 169 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 086 086 000 Old_age Always - 10553 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 - 70 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 64 193 Load_Cycle_Count 0x0032 132 132 000 Old_age Always - 204364 194 Temperature_Celsius 0x0022 125 099 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 - 1 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 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Conveyance offline Completed without error 00% 6356 - 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. Cheers.
Archived
This topic is now archived and is closed to further replies.