New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Should these I/O errors concern me?
raindog308
Administrator, Veteran
Saw this on my home Linux box's dmesg. Should I freak out?
The box has four two-disk mirrors - a pair of WD 250GBs for root, and then three pairs of WD Black for storage:
[11701214.651503] md: md0: data-check done. [11744796.070089] md: md6: data-check done. [11745112.247575] md: md5: data-check done. [11754308.149938] md: md4: data-check done. [12224216.822156] ata5.00: exception Emask 0x0 SAct 0x3e0 SErr 0x0 action 0x0 [12224216.822165] ata5.00: irq_stat 0x40000008 [12224216.822172] ata5.00: failed command: READ FPDMA QUEUED [12224216.822183] ata5.00: cmd 60/08:28:d8:9a:9d/00:00:d0:00:00/40 tag 5 ncq 4096 in res 41/40:00:d8:9a:9d/00:00:d0:00:00/00 Emask 0x409 (media error) [12224216.822188] ata5.00: status: { DRDY ERR } [12224216.822191] ata5.00: error: { UNC } [12224216.823754] ata5.00: configured for UDMA/133 [12224216.823776] sd 4:0:0:0: [sde] Unhandled sense code [12224216.823781] sd 4:0:0:0: [sde] [12224216.823784] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [12224216.823787] sd 4:0:0:0: [sde] [12224216.823790] Sense Key : Medium Error [current] [descriptor] [12224216.823796] Descriptor sense data with sense descriptors (in hex): [12224216.823798] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 [12224216.823813] d0 9d 9a d8 [12224216.823820] sd 4:0:0:0: [sde] [12224216.823824] Add. Sense: Unrecovered read error - auto reallocate failed [12224216.823828] sd 4:0:0:0: [sde] CDB: [12224216.823830] Read(16): 88 00 00 00 00 00 d0 9d 9a d8 00 00 00 08 00 00 [12224216.823848] end_request: I/O error, dev sde, sector 3499989720 [12224216.823854] md/raid1:md4: sde1: rescheduling sector 3499725528 [12224216.823879] ata5: EH complete [12224216.869466] md/raid1:md4: redirecting sector 3499725528 to other mirror: sdf1
# cat /proc/mdstat Personalities : [raid1] md6 : active raid1 sdh1[0] sdb1[1] 5860389888 blocks super 1.2 [2/2] [UU] bitmap: 0/44 pages [0KB], 65536KB chunk md5 : active raid1 sda1[0] sdg1[1] 5860389888 blocks super 1.2 [2/2] [UU] bitmap: 0/44 pages [0KB], 65536KB chunk md4 : active raid1 sdf1[0] sde1[1] 5860389888 blocks super 1.2 [2/2] [UU] bitmap: 0/44 pages [0KB], 65536KB chunk md0 : active raid1 sdd1[0] sdc1[1] 233899840 blocks super 1.0 [2/2] [UU] bitmap: 1/2 pages [4KB], 65536KB chunk unused devices:
# for disk in sda sdb sdc sdd sde sdf sdg sdh ; do smartctl -a /dev/$disk | grep overall-health ; done SMART overall-health self-assessment test result: PASSED SMART overall-health self-assessment test result: PASSED SMART overall-health self-assessment test result: PASSED SMART overall-health self-assessment test result: PASSED SMART overall-health self-assessment test result: PASSED SMART overall-health self-assessment test result: PASSED SMART overall-health self-assessment test result: PASSED SMART overall-health self-assessment test result: PASSED
sda:Device Model: WDC WD60EFRX-68MYMN1 sdb:Device Model: WDC WD60EFRX-68MYMN1 sdc:Device Model: WDC WD2500AAJS-00B4A0 sdd:Device Model: WDC WD2500AAJS-75M0A0 sde:Device Model: WDC WD60EFRX-68MYMN1 sdf:Device Model: WDC WD60EFRX-68MYMN1 sdg:Device Model: WDC WD60EFRX-68MYMN1 sdh:Device Model: WDC WD60EFRX-68MYMN1
# smartctl -a /dev/sde smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build) Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD60EFRX-68MYMN1 Serial Number: WD-WX11D259VU9E LU WWN Device Id: 5 0014ee 2613e4ae7 Firmware Version: 82.00A82 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5700 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Dec 19 18:34:46 2016 PST 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 5024) 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: ( 703) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303d) 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 201 200 021 Pre-fail Always - 8933 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 29 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 085 085 000 Old_age Always - 11377 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 - 29 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 22 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 5781 194 Temperature_Celsius 0x0022 113 101 000 Old_age Always - 39 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 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 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.
Comments
For some advice about smartctl see this https://www.lowendtalk.com/discussion/comment/1881875/#Comment_1881875
nice explanation http://www.sj-vs.net/forcing-a-hard-disk-to-reallocate-bad-sectors/
I would definitely be worried and would schedule a (long) test immediately on sde to confirm if it is a disk block error or some transport/other error (relatively benign and usually not permanent without any long term consequences).
I'm also very concerned that for over 11000 hours (that presumably you have been running the drive), you've not run even ONE test (as per the SMART logs). That is definitely bad practice and I would start scheduling regular short/long/offline tests immediately on all the drives.
It's a 6TB drive - so it's going to take a while (~10-12 hours or so?) to finish the test.
HTH.
Let the non-believer's sins be cleansed by the almighty power of SMARTCTL!
@Microlinux unless the drive completely dies before the test ends LOL
i did not saw any write errors, how old are your disks i mean when did you bought them ?
A short test should find any major problems quickly; even if it doesn't fail completely it'll show error counter log. If "Non-medium error count" is above 0, replace it.
Had 2 HGST SAS made in '16 fail after 6 months on separate occasions. Older not always bad when it comes to disks it seems; unpredictable at best. Smart/Mdadm tests/reporting can give better results when it comes to disk integrity.