Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

HDD failure for Western Digital Caviar Green 2TB drive.


  • Please log in to reply
12 replies to this topic

#1 Illusion13

Illusion13

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:07 PM

Posted 07 December 2014 - 05:55 PM

Few days ago I was downloading stuff on torrent and the torrents were failing cause there was I/O device error. It seems that I can still view the files in explorer, opening small files will work, opening large files especially videos seems to work but if you try to foward in parts of the video there will be significant slow and sometimes crashing of the video player.

 

I've tried to do a chkdsk, it identified 8kb in bad sector. I tried to do a surface scan and it only went half way after something like 30 hours of it running, so I gave up. It did however fix 4 or 5 files that had bad sectors. Now the drive still seems to be really sluggish when I tried to watch files from it,

 

I downloaded western digital's data lifeguard diagnostic tool, but when it scans for drives available, it doesnt detect my 2tb drive as a physical drive, but it does show up on the logical drives. Did I not set this up properly in the first place? My 2TB drive had files in it already when I set up my new computer, and its been a few months since I've used it this way with no problems...

 

Any idea what to do with this?


Edited by Illusion13, 07 December 2014 - 06:17 PM.


BC AdBot (Login to Remove)

 


#2 JohnC_21

JohnC_21

  • Members
  • 24,295 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:07 AM

Posted 07 December 2014 - 07:56 PM

Try running a HDD test using Gsmartcontrol. http://gsmartcontrol.sourceforge.net/home/

#3 Illusion13

Illusion13
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:07 PM

Posted 07 December 2014 - 08:44 PM

Tried to run the short 2 minute test and it says read failure....

 

I dont really know how to read the errors... Should I save a copy and upload it here?



#4 Illusion13

Illusion13
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:07 PM

Posted 07 December 2014 - 08:45 PM

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win7(64)-sp1] (sf-5.43-1)
Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (Adv. Format)
Device Model:     WDC WD20EARS-22MVWB0
Serial Number:    WD-WMAZA4735687
LU WWN Device Id: 5 0014ee 0581cb943
Firmware Version: 51.0AB51
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical (offset 512 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:    Sun Dec 07 17:42:28 2014 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:  (0x82)    Offline data collection activity
                    was completed without error.
                    Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 121)    The previous self-test completed having
                    the read element of the test failed.
Total time to complete Offline
data collection:         (38580) 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:      ( 372) minutes.
Conveyance self-test routine
recommended polling time:      (   5) minutes.
SCT capabilities:            (0x3035)    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   148   148   051    Pre-fail  Always       -       18157
  3 Spin_Up_Time            0x0027   253   167   021    Pre-fail  Always       -       1941
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1378
  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   074   074   000    Old_age   Always       -       19399
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       602
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       32
193 Load_Cycle_Count        0x0032   149   149   000    Old_age   Always       -       153521
194 Temperature_Celsius     0x0022   117   087   000    Old_age   Always       -       33
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   197   197   000    Old_age   Always       -       1195
198 Offline_Uncorrectable   0x0030   197   197   000    Old_age   Offline      -       1081
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   168   168   000    Old_age   Offline      -       8610

SMART Error Log Version: 1
ATA Error Count: 12620 (device log contains only the most recent five errors)
    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 12620 occurred at disk power-on lifetime: 19362 hours (806 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
  -- -- -- -- -- -- --
  04 61 00 00 00 00 00  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 02 00 00 00 00 00 00      01:37:53.328  SET FEATURES [Enable write cache]
  ef 02 00 00 00 00 00 00      01:37:53.213  SET FEATURES [Enable write cache]
  ef 02 00 00 00 00 00 00      01:37:53.097  SET FEATURES [Enable write cache]

Error 12619 occurred at disk power-on lifetime: 19362 hours (806 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
  -- -- -- -- -- -- --
  04 61 00 00 00 00 00  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 02 00 00 00 00 00 00      01:37:53.213  SET FEATURES [Enable write cache]
  ef 02 00 00 00 00 00 00      01:37:53.097  SET FEATURES [Enable write cache]
  ef 02 00 00 00 00 00 00      01:37:52.982  SET FEATURES [Enable write cache]

Error 12618 occurred at disk power-on lifetime: 19362 hours (806 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
  -- -- -- -- -- -- --
  04 61 00 00 00 00 00  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 02 00 00 00 00 00 00      01:37:53.097  SET FEATURES [Enable write cache]
  ef 02 00 00 00 00 00 00      01:37:52.982  SET FEATURES [Enable write cache]
  ef 02 00 00 00 00 00 00      01:37:52.867  SET FEATURES [Enable write cache]

Error 12617 occurred at disk power-on lifetime: 19362 hours (806 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
  -- -- -- -- -- -- --
  04 61 00 00 00 00 00  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 02 00 00 00 00 00 00      01:37:52.982  SET FEATURES [Enable write cache]
  ef 02 00 00 00 00 00 00      01:37:52.867  SET FEATURES [Enable write cache]
  ef 02 00 00 00 00 00 00      01:37:52.752  SET FEATURES [Enable write cache]

Error 12616 occurred at disk power-on lifetime: 19362 hours (806 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
  -- -- -- -- -- -- --
  04 61 00 00 00 00 00  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 02 00 00 00 00 00 00      01:37:52.867  SET FEATURES [Enable write cache]
  ef 02 00 00 00 00 00 00      01:37:52.752  SET FEATURES [Enable write cache]
  ef 02 00 00 00 00 00 00      01:37:52.638  SET FEATURES [Enable write cache]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     19399         382060128

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.



#5 JohnC_21

JohnC_21

  • Members
  • 24,295 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:07 AM

Posted 07 December 2014 - 10:06 PM

This attribute is of concern

 

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH   TYPE      UPDATED  WHEN_FAILED RAW_VALUE

Current_Pending_Sector      0x0032      197      197         000       Old_age     Always                                  1195

 

I believe you should copy any important data off the drive as soon as possible and get a new drive. Chkdsk should not take 30 hours.

 

Current Pending Sector Count S.M.A.R.T. parameter is a critical parameter and indicates the current count of unstable sectors (waiting for remapping). The raw value of this attribute indicates the total number of sectors waiting for remapping. Later, when some of these sectors are read successfully, the value is decreased. If errors still occur when reading some sector, the hard drive will try to restore the data, transfer it to the reserved disk area (spare area) and mark this sector as remapped.

 

After copying your data you can use Seatools for DOS. It will try to repair bad sectors. You may have to change the mode from AHCI to IDE in BIOS if the drive is not detected.

 

Tutorial

 

SeaTools for DOS Guide - Seagate

Edited by JohnC_21, 07 December 2014 - 10:08 PM.


#6 Illusion13

Illusion13
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:07 PM

Posted 07 December 2014 - 11:26 PM

So this remapping thing. When exactly does the HD do its work? What do I have to do to trigger a complete remap?

 

Should I just do the Seatools now... I doubt with the current read rate I can even get any files out... I mean sucks to lose ALL this stuff but as is I wonder how much of it is gone already... =.=



#7 JohnC_21

JohnC_21

  • Members
  • 24,295 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:07 AM

Posted 08 December 2014 - 08:24 AM

The remap can only happen if the sectors can be read if not, the pending sector count just increases which is bad. From Wiki

 

Count of "unstable" sectors (waiting to be remapped, because of unrecoverable read errors). If an unstable sector is subsequently read successfully, the sector is remapped and this value is decreased. Read errors on a sector will not remap the sector immediately (since the correct value cannot be read and so the value to remap is not known, and also it might become readable later); instead, the drive firmware remembers that the sector needs to be remapped, and will remap it the next time it's written.[35] However some drives will not immediately remap such sectors when written; instead the drive will first attempt to write to the problem sector and if the write operation is successful then the sector will be marked good (in this case, the "Reallocation Event Count" (0xC4) will not be increased). This is a serious shortcoming, for if such a drive contains marginal sectors that consistently fail only after some time has passed following a successful write operation, then the drive will never remap these problem sectors.

 

 

I am not sure when the HD will remap the sectors. Seatools for DOS I believe tries to repair sectors but this is doing the long test. I think the Seatools for DOS would be the last option after trying to recover your data if your read problems are as bad as you say.

 

Sometimes chkdsk can do more damage than it helps. I can't say if that happened in your case though.

 

You may have better luck reading the drive using linux. I would create a bootable disk of Partition Magic using another computer. The last free version is here. Boot to the desktop. Double click the File Manager and see if you can transfer the files to an external drive. Parted Magic has recovery tools on it but to make use of a linux recovery tool called dd-rescue, you would need another 2TB drive.

 

If you cannot recovery files with the File Manager, then the next option would be using Testdisk (included in PartedMagic). Post back the results of using the Parted Magic File Manager. If that does not work then we can try Testdisk.



#8 KaoticEvil

KaoticEvil

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:11:07 PM

Posted 08 December 2014 - 11:23 AM

I agree, definitely time to get a new drive and get any data that you want off that old one. Look at the "Type" column. Nearly all of them are Old Age.. and the ones that aren't are in pre-fail. That drive is dying, and most likely won't last much longer at all.



#9 hamluis

hamluis

    Moderator


  • Moderator
  • 56,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:07 PM

Posted 08 December 2014 - 03:30 PM

FWIW:  IME, hard drive I/O errors can result from loose connections (or bad IDE/SATA cable)...so I normally just disconnect all cables to hard drive then reconnect them and see if the I/O errors continue.

 

Louis



#10 KaoticEvil

KaoticEvil

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:11:07 PM

Posted 08 December 2014 - 03:35 PM

FWIW:  IME, hard drive I/O errors can result from loose connections (or bad IDE/SATA cable)...so I normally just disconnect all cables to hard drive then reconnect them and see if the I/O errors continue.

 

Louis

 

Also very true. Reconnecting cables never hurts. I might suggest also reconnecting the IDE/SATA cables on the motherboard end as well. Or even other cables, if you have them available.


Edited by KaoticEvil, 08 December 2014 - 03:35 PM.


#11 Illusion13

Illusion13
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:07 PM

Posted 08 December 2014 - 04:24 PM

How much is it usually to take it to a shop to try to do a scan of the disk? Is it worth the trouble?

 

And also, as most of you will probably understand, I am a mid 20s guy... There's a ton of stuff on that HDD that I would rather people not see that I have...


 

FWIW:  IME, hard drive I/O errors can result from loose connections (or bad IDE/SATA cable)...so I normally just disconnect all cables to hard drive then reconnect them and see if the I/O errors continue.

 

Louis

 

Also very true. Reconnecting cables never hurts. I might suggest also reconnecting the IDE/SATA cables on the motherboard end as well. Or even other cables, if you have them available.

 

Tried unplugging and replugging already. Though maybe I can try again and blow the SATA ports with compressed air too or something.

 

Also about the old age/pre-failure thing... Is that really what it says about my disk? Cause I just did the scan with my 120gb SSD and there's abunch of old age and pre-failure attribute too, but nothing was highlighted and I did a test and it completed with no errors. It wont even do a short test of the 2TB HDD....


Edited by Illusion13, 08 December 2014 - 04:49 PM.


#12 JohnC_21

JohnC_21

  • Members
  • 24,295 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:07 AM

Posted 08 December 2014 - 04:57 PM

You could try a different SATA cable but I doubt that would help. Try the Parted Magic disk and see if it can mount and read the drive.

#13 KaoticEvil

KaoticEvil

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:11:07 PM

Posted 08 December 2014 - 10:44 PM

I doubt if a different cable would help, but it's worth a try.. Same with blowing out the ports... And the old age/prefail are derived from the drive itself. It does happen that when the values aren't set by the drive (during the SMART test), that the reporting software misinterprets.

 

As far as scanning it goes, it depends on the shop. Myself, I would charge $40 for it, however that number is likely to vary GREATLY from shop to shop and location to location. If there is something on there that you *really* need, it might be worth it. But I would definitely get that drive replaced.

 

Regarding the stuff that you "would rather people not see that I have"... Any reputable shop isn't going to be going thru your data anyway. Just doing data recovery doesn't require actually looking at the files.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users