Arch Linux

Vortex375

Member

Registered: 2009-02-24

Posts: 61

Hard drive broken?

My system just froze with the HDD-LED constantly on. After a couple of seconds it recovered and continued to run like normal. I found this in the logs:

 kernel: ata1.00: exception Emask 0x0 SAct 0x7e000006 SErr 0x0 action 0x6 frozen
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [138B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [138B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [139B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [139B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [139B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [139B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [139B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [139B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1: hard resetting link
 kernel: ata1: softreset failed (device not ready)
 kernel: ata1: applying PMP SRST workaround and retrying
 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
 kernel: ata1.00: configured for UDMA/133
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: sd 0:0:0:0: [sda] Unhandled error code
 kernel: sd 0:0:0:0: [sda]  
 kernel: Result: hostbyte=0x00 driverbyte=0x06
 kernel: sd 0:0:0:0: [sda] CDB: 
 kernel: cdb[0]=0x2a: 2a 00 08 61 10 00 00 04 00 00
 kernel: end_request: I/O error, dev sda, sector 140578816
 kernel: Buffer I/O error on device sda6, logical block 1529600
 kernel: Buffer I/O error on device sda6, logical block 1529601
 kernel: Buffer I/O error on device sda6, logical block 1529602
 kernel: Buffer I/O error on device sda6, logical block 1529603
 kernel: Buffer I/O error on device sda6, logical block 1529604
 kernel: Buffer I/O error on device sda6, logical block 1529605
 kernel: Buffer I/O error on device sda6, logical block 1529606
 kernel: Buffer I/O error on device sda6, logical block 1529607
 kernel: Buffer I/O error on device sda6, logical block 1529608
 kernel: Buffer I/O error on device sda6, logical block 1529609
 kernel: Buffer I/O error on device sda6, logical block 1529610
 kernel: Buffer I/O error on device sda6, logical block 1529611
 kernel: Buffer I/O error on device sda6, logical block 1529612
 kernel: Buffer I/O error on device sda6, logical block 1529613
 kernel: Buffer I/O error on device sda6, logical block 1529614
 kernel: Buffer I/O error on device sda6, logical block 1529615
 kernel: Buffer I/O error on device sda6, logical block 1529616
 kernel: Buffer I/O error on device sda6, logical block 1529617
 kernel: Buffer I/O error on device sda6, logical block 1529618
 kernel: Buffer I/O error on device sda6, logical block 1529619
 kernel: Buffer I/O error on device sda6, logical block 1529620
 kernel: Buffer I/O error on device sda6, logical block 1529621
 kernel: Buffer I/O error on device sda6, logical block 1529622
 kernel: Buffer I/O error on device sda6, logical block 1529623
 kernel: Buffer I/O error on device sda6, logical block 1529624
 kernel: Buffer I/O error on device sda6, logical block 1529625
 kernel: Buffer I/O error on device sda6, logical block 1529626
 kernel: Buffer I/O error on device sda6, logical block 1529627
 kernel: Buffer I/O error on device sda6, logical block 1529628
 kernel: Buffer I/O error on device sda6, logical block 1529629
 kernel: Buffer I/O error on device sda6, logical block 1529630
 kernel: Buffer I/O error on device sda6, logical block 1529631
 kernel: Buffer I/O error on device sda6, logical block 1529632
 kernel: Buffer I/O error on device sda6, logical block 1529633
 kernel: Buffer I/O error on device sda6, logical block 1529634
 kernel: Buffer I/O error on device sda6, logical block 1529635
 kernel: Buffer I/O error on device sda6, logical block 1529636
 kernel: Buffer I/O error on device sda6, logical block 1529637
 kernel: Buffer I/O error on device sda6, logical block 1529638
 kernel: Buffer I/O error on device sda6, logical block 1529639
 kernel: Buffer I/O error on device sda6, logical block 1529640
 kernel: Buffer I/O error on device sda6, logical block 1529641
 kernel: Buffer I/O error on device sda6, logical block 1529642
 kernel: Buffer I/O error on device sda6, logical block 1529643
 kernel: Buffer I/O error on device sda6, logical block 1529644
 kernel: Buffer I/O error on device sda6, logical block 1529645
 kernel: Buffer I/O error on device sda6, logical block 1529646
 kernel: Buffer I/O error on device sda6, logical block 1529647
 kernel: Buffer I/O error on device sda6, logical block 1529648
 kernel: Buffer I/O error on device sda6, logical block 1529649
 kernel: Buffer I/O error on device sda6, logical block 1529650
 kernel: Buffer I/O error on device sda6, logical block 1529651
 kernel: Buffer I/O error on device sda6, logical block 1529652
 kernel: Buffer I/O error on device sda6, logical block 1529653
 kernel: Buffer I/O error on device sda6, logical block 1529654
 kernel: Buffer I/O error on device sda6, logical block 1529655
 kernel: Buffer I/O error on device sda6, logical block 1529656
 kernel: Buffer I/O error on device sda6, logical block 1529657
 kernel: Buffer I/O error on device sda6, logical block 1529658
 kernel: Buffer I/O error on device sda6, logical block 1529659
 kernel: Buffer I/O error on device sda6, logical block 1529660
 kernel: Buffer I/O error on device sda6, logical block 1529661
 kernel: Buffer I/O error on device sda6, logical block 1529662
 kernel: Buffer I/O error on device sda6, logical block 1529663
 kernel: Buffer I/O error on device sda6, logical block 1529664
 kernel: Buffer I/O error on device sda6, logical block 1529665
 kernel: Buffer I/O error on device sda6, logical block 1529666
 kernel: Buffer I/O error on device sda6, logical block 1529667
 kernel: Buffer I/O error on device sda6, logical block 1529668
 kernel: Buffer I/O error on device sda6, logical block 1529669
 kernel: Buffer I/O error on device sda6, logical block 1529670
 kernel: Buffer I/O error on device sda6, logical block 1529671
(many more of these ...)
 kernel: Buffer I/O error on device sda6, logical block 1529726
 kernel: Buffer I/O error on device sda6, logical block 1529727
 kernel: EXT4-fs warning (device sda6): ext4_end_bio:319: I/O error writing to inode 5510429 (offset 66060288 size 524288 starting block 17572480)
 kernel: sd 0:0:0:0: [sda] Unhandled error code
 kernel: sd 0:0:0:0: [sda]  
 kernel: Result: hostbyte=0x00 driverbyte=0x06
 kernel: sd 0:0:0:0: [sda] CDB: 
 kernel: cdb[0]=0x2a: 2a 00 08 61 14 00 00 04 00 00
 kernel: end_request: I/O error, dev sda, sector 140579840
 kernel: Buffer I/O error on device sda6, logical block 1529728
 kernel: Buffer I/O error on device sda6, logical block 1529729
 kernel: Buffer I/O error on device sda6, logical block 1529730
 kernel: Buffer I/O error on device sda6, logical block 1529731
 kernel: Buffer I/O error on device sda6, logical block 1529732
 kernel: Buffer I/O error on device sda6, logical block 1529733
 kernel: Buffer I/O error on device sda6, logical block 1529734
 kernel: Buffer I/O error on device sda6, logical block 1529735
 kernel: Buffer I/O error on device sda6, logical block 1529736
 kernel: Buffer I/O error on device sda6, logical block 1529737
 kernel: Buffer I/O error on device sda6, logical block 1529738
 kernel: Buffer I/O error on device sda6, logical block 1529739
 kernel: Buffer I/O error on device sda6, logical block 1529740
(again many more of these ...)
 kernel: Buffer I/O error on device sda6, logical block 1529854
 kernel: Buffer I/O error on device sda6, logical block 1529855
 kernel: EXT4-fs warning (device sda6): ext4_end_bio:319: I/O error writing to inode 5510429 (offset 66584576 size 524288 starting block 17572608)
 kernel: ata1: EH complete
 kernel: ata1.00: exception Emask 0x0 SAct 0x7c000000 SErr 0x0 action 0x6 frozen
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [139B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [139B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [139B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [139B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
 kernel: [139B blob data]
 kernel: ata1.00: status: { DRDY }
 kernel: ata1: hard resetting link
 kernel: ata1: softreset failed (device not ready)
 kernel: ata1: applying PMP SRST workaround and retrying
 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
 kernel: ata1.00: configured for UDMA/133
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1.00: device reported invalid CHS sector 0
 kernel: ata1: EH complete

That doesn't look so good.The hard drive is a Western Digital WD20EZRX Green 2TB which is only about a month old!
Is it broken? Should I try to get a replacement?

EDIT: Oh no, it just happened again. After a half minute freeze the system continues as if nothing happened.

Last edited by Vortex375 (2013-02-10 18:34:36)

sano

Member

Registered: 2012-02-11

Posts: 114

Re: Hard drive broken?

Did you check if smartctl reports any problems?

Vortex375

Member

Registered: 2009-02-24

Posts: 61

Re: Hard drive broken?

Here is the output of smartctl -a:

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD20EZRX-00DC0B0
Serial Number:    WD-WMC1T0715165
LU WWN Device Id: 5 0014ee 0ae1d9573
Firmware Version: 80.00A80
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sun Feb 10 21:03:49 2013 CET
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:  (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:                (26160) 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:        ( 265) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x70b5) 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   173   171   021    Pre-fail  Always       -       6341
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       92
  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       -       317
 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       -       92
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       9
193 Load_Cycle_Count        0x0032   197   197   000    Old_age   Always       -       9216
194 Temperature_Celsius     0x0022   121   113   000    Old_age   Always       -       29
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.

I don't see anything alarming - except the high Load Cycle Count. I read on the net that certain WD drives have a firmware flaw that causes this. But could the drive really be damaged after just a month of use? What are typical values for Load Cycle Count after a month of use?

anonymous_user

Member

Registered: 2009-08-28

Posts: 3,059

Re: Hard drive broken?

I have a 6-month old (estimate) Western Digital RE4 and my Load Cycle Count is only 481.

Vortex375

Member

Registered: 2009-02-24

Posts: 61

Re: Hard drive broken?

Ok, I read up a bit more on the issue. Then I installed idle3-tools and disabled the idle timer. Hopefully that will stop the LCCs from increasing.

Still, the drive should be ways away from it's maximum Load Cycle Count, so it shouldn't die on me already.

I opened up my computer case and found there was an SATA cable plugged into the motherboard's controller with no drive attached. I probably forgot to unplug it from the motherboard after removing the old drive. Could that have caused any problems? After disabling the idle3 timer and removing the cable I haven't had any freezes yet.

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: Hard drive broken?

I opened up my computer case and found there was an SATA cable plugged into the motherboard's controller with no drive attached. I probably forgot to unplug it from the motherboard after removing the old drive. Could that have caused any problems? After disabling the idle3 timer and removing the cable I haven't had any freezes yet.

I cannot see this as being any different than having a SATA port connected to one of those eSATA adapters, and having nothing attached to it... but that is just pure speculation.