Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Problem WD WD30EZRX

March 3rd, 2014, 19:22

Hello, suddenly my 3TB WD30EZRX is dead, but the problem is strange, this disk is without operating system

When I start windows 8 with another disk, the operating system never come up completely with his desktop and I can't access to hard disk management

The real strange is when I start windows on a recovery distro on usb key, the led of hard disk never stop blinkin, the light it's seems alway on and also in this case operating system don't start.

So I try to access to disk with linux and only I time I get this smart parameter, other times it's seems doesn't respond

Here below smartctl log:

smartctl 6.0 2012-10-10 r3643 [i686-linux-3.5.3-pmagic] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green (AF)
Device Model: WDC WD30EZRX-22DC0B0
Serial Number: WD-WCCXXXXXXXXX
LU WWN Device Id: 5 0014ee 2b39c81f8
Firmware Version: 80.00A80
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Mon Mar 3 23:50:40 2014 UTC
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: (42300) 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: ( 424) 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 199 199 051 Pre-fail Always - 1059
3 Spin_Up_Time 0x0027 192 175 021 Pre-fail Always - 5383
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 233
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 - 174
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 - 233
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 92
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1860
194 Temperature_Celsius 0x0022 116 112 000 Old_age Always - 34
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 54
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
ATA Error Count: 4189 (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 4189 occurred at disk power-on lifetime: 74 hours (3 days + 2 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 a0 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 a0 00 00:07:09.698 SET FEATURES [Enable write cache]
ef 02 00 00 00 00 a0 00 00:07:08.577 SET FEATURES [Enable write cache]
ef 02 00 00 00 00 a0 00 00:07:08.431 SET FEATURES [Enable write cache]

Error 4188 occurred at disk power-on lifetime: 74 hours (3 days + 2 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 a0 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 a0 00 00:07:08.577 SET FEATURES [Enable write cache]
ef 02 00 00 00 00 a0 00 00:07:08.431 SET FEATURES [Enable write cache]
ef 02 00 00 00 00 a0 00 00:07:07.312 SET FEATURES [Enable write cache]

Error 4187 occurred at disk power-on lifetime: 74 hours (3 days + 2 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 a0 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 a0 00 00:07:08.431 SET FEATURES [Enable write cache]
ef 02 00 00 00 00 a0 00 00:07:07.312 SET FEATURES [Enable write cache]
ef 02 00 00 00 00 a0 00 00:07:06.189 SET FEATURES [Enable write cache]

Error 4186 occurred at disk power-on lifetime: 74 hours (3 days + 2 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 a0 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 a0 00 00:07:07.312 SET FEATURES [Enable write cache]
ef 02 00 00 00 00 a0 00 00:07:06.189 SET FEATURES [Enable write cache]
ef 02 00 00 00 00 a0 00 00:07:05.070 SET FEATURES [Enable write cache]

Error 4185 occurred at disk power-on lifetime: 74 hours (3 days + 2 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 a0 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 a0 00 00:07:06.189 SET FEATURES [Enable write cache]
ef 02 00 00 00 00 a0 00 00:07:05.070 SET FEATURES [Enable write cache]
ef 02 00 00 00 00 a0 00 00:07:03.947 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% 172 6376374
# 2 Short offline Completed: read failure 90% 172 6376368
# 3 Short offline Completed without error 00% 0 -

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.


What do you suggest almost to recover my data?

Thanks in advance

Re: Problem WD WD30EZRX

March 4th, 2014, 3:02

Drive either has media issues or a duff head, it seems to me. Both of which will cause the drive to degrade further the more you tinker with it :-(

If you value data, seek pro assistance.

Re: Problem WD WD30EZRX

March 5th, 2014, 9:26

thank you for reply, but exist a powerfull tool to recover data?

Re: Problem WD WD30EZRX

March 5th, 2014, 9:34

darioit wrote:thank you for reply, but exist a powerfull tool to recover data?

Yes, the Pros will use them on your drive when you take it to them.
It is called a clean room, and other things are specialised tools and years of knowledge.

Unless you are going to spend months learning and many many times what it would cost for a DR Pro to recover your data, Then a Pro is your option.

There are some fixes that are DIY, but this isn't one of them. Sorry mate

Re: Problem WD WD30EZRX

March 5th, 2014, 9:41

Of course! A clean room, head removal tools, and a specialized technician are required to repair the damage before access to data is restored. You might want to contact Blackst on this forum who has all the necessary tools.

Re: Problem WD WD30EZRX

March 5th, 2014, 10:21

darioit, you have PM

Re: Problem WD WD30EZRX

March 6th, 2014, 12:37

Sorry but the day before smart was perfect and after only 74 hours life is damaged? How is it possible?

In the same day I have other 2 disks with many sector reallocated and after a low level format that disks was perfect.

It's possible that damage is due to overvolt or others problem coming from pc?
Post a reply