MultiDrive – free backup, clone & wipe disk utility from Atola Technology

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  Page 1 of 1
  [ 8 posts ] 
  Previous topic | Next topic 
Author Message
peterf81
 Post subject: Click noise - Linux detects d drive - need advice (WD20EARX)
PostPosted: March 26th, 2013, 11:18 
Offline

Joined: March 26th, 2013, 11:08
Posts: 9
Location: Slovakistan
Hello,

guys I would like to ask you for advice on my HDD. Data recovery company says head and surface probably bad, made me offer for recovery for cca 1500$ USD. For me currently too much. On HDD are my personal data, I would pay 300$ for recovery maximum.

HDD is WD20EARX 2TB, it was in external USB3 enclosure "HP Simple Save 2TB" . Hdd was not detected after reboot . Also there was electricity outage / spike on that day (the lights in my room started to flicker for cca 2 seconds, reaaaally heavy flickering )

HDD makes clicking sound when connected .

BIOS mostly freezes on HDD detection, other times in detected the HDD (but OS would not load), next time it did not detect but continued booting . Etc, its random .

In linux I have a lot more info. HDD makes click sound, also when i run fdisk /dev/sdc then i can list correct partitionj (there is one). But it responds very slow . Also I can mount but when listing files it stops, but i got some output from the directory structure, when i unpluged the hdd while 'ls' was still frozen .

In linux, when i hot plug the HDD, dmesg says :
Code:
....
[  128.358715] eth0: no IPv6 routers present
[  593.823289] ata3: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
[  593.823295] ata3: irq_stat 0x00400040, connection status changed
[  593.823298] ata3: SError: { PHYRdyChg 10B8B DevExch }
[  593.823305] ata3: hard resetting link
[  594.575967] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  594.576292] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
[  594.576302] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff880211068550), AE_NOT_FOUND (20110623/psparse-536)
[  594.577145] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
[  594.577155] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff880211068550), AE_NOT_FOUND (20110623/psparse-536)
[  594.577172] ata3.00: configured for UDMA/100
[  594.588936] ata3: EH complete
[  609.737323] ata3: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
[  609.737328] ata3: irq_stat 0x00400040, connection status changed
[  609.737332] ata3: SError: { PHYRdyChg 10B8B DevExch }
[  609.737337] ata3: hard resetting link
[  610.488987] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  610.489309] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
[  610.489319] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff880211068550), AE_NOT_FOUND (20110623/psparse-536)
[  610.490139] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
[  610.490149] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff880211068550), AE_NOT_FOUND (20110623/psparse-536)
[  610.490166] ata3.00: configured for UDMA/100
[  610.501776] ata3: EH complete
[  620.116352] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4050002 action 0xe frozen
[  620.116357] ata2: irq_stat 0x00000040, connection status changed
[  620.116360] ata2: SError: { RecovComm PHYRdyChg CommWake DevExch }
[  620.116367] ata2: hard resetting link
[  623.972324] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  628.967611] ata2.00: qc timeout (cmd 0xec)
[  628.967621] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[  628.967627] ata2: hard resetting link
[  634.322572] ata2: link is slow to respond, please be patient (ready=0)
[  638.966201] ata2: COMRESET failed (errno=-16)
[  638.966207] ata2: hard resetting link
[  644.321160] ata2: link is slow to respond, please be patient (ready=0)
[  648.964791] ata2: COMRESET failed (errno=-16)
[  648.964798] ata2: hard resetting link
[  654.319724] ata2: link is slow to respond, please be patient (ready=0)
[  660.697733] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  669.602176] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
[  669.602186] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802110684d8), AE_NOT_FOUND (20110623/psparse-536)
[  674.596647] ata2.00: qc timeout (cmd 0x27)
[  674.596656] ata2.00: failed to read native max address (err_mask=0x4)
[  674.596659] ata2.00: HPA support seems broken, skipping HPA handling
[  674.596664] ata2: limiting SATA link speed to 3.0 Gbps
[  674.596669] ata2: hard resetting link
[  679.951625] ata2: link is slow to respond, please be patient (ready=0)
[  684.595250] ata2: COMRESET failed (errno=-16)
[  684.595257] ata2: hard resetting link
[  689.950195] ata2: link is slow to respond, please be patient (ready=0)
[  694.593828] ata2: COMRESET failed (errno=-16)
[  694.593834] ata2: hard resetting link
[  699.948781] ata2: link is slow to respond, please be patient (ready=0)
[  708.620625] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  708.639851] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
[  708.639861] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802110684d8), AE_NOT_FOUND (20110623/psparse-536)
[  708.639934] ata2.00: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133
[  708.639937] ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[  708.643312] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
[  708.643321] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802110684d8), AE_NOT_FOUND (20110623/psparse-536)
[  708.912256] ata2.00: configured for UDMA/133
[  708.912267] ata2: EH complete
[  708.912387] scsi 1:0:0:0: Direct-Access     ATA      WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5
[  708.912587] sd 1:0:0:0: Attached scsi generic sg3 type 0
[  708.912596] sd 1:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[  708.912600] sd 1:0:0:0: [sdc] 4096-byte physical blocks
[  708.912783] sd 1:0:0:0: [sdc] Write Protect is off
[  708.912788] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[  708.912921] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  708.931314]  sdc: sdc1
[  708.932093] sd 1:0:0:0: [sdc] Attached SCSI disk
[  748.247353] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  748.247359] ata2.00: failed command: SMART
[  748.247366] ata2.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0
[  748.247367]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  748.247370] ata2.00: status: { DRDY }
[  748.247376] ata2: hard resetting link
[  753.602280] ata2: link is slow to respond, please be patient (ready=0)
[  758.245911] ata2: COMRESET failed (errno=-16)
[  758.245918] ata2: hard resetting link
[  763.600899] ata2: link is slow to respond, please be patient (ready=0)
[  768.244539] ata2: COMRESET failed (errno=-16)
[  768.244546] ata2: hard resetting link
[  773.599485] ata2: link is slow to respond, please be patient (ready=0)
[  789.208775] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  789.450786] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
[  789.450795] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802110684d8), AE_NOT_FOUND (20110623/psparse-536)
[  789.454856] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
[  789.454865] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802110684d8), AE_NOT_FOUND (20110623/psparse-536)
[  789.455508] ata2.00: configured for UDMA/133
[  789.455525] ata2: EH complete
[  856.626647] ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[  856.626652] ata2.00: irq_stat 0x40000008
[  856.626656] ata2.00: failed command: READ FPDMA QUEUED
[  856.626663] ata2.00: cmd 60/08:00:00:a1:40/00:00:e0:00:00/40 tag 0 ncq 4096 in
[  856.626664]          res 41/04:00:00:a1:40/00:00:e0:00:00/40 Emask 0x401 (device error) <F>
[  856.626676] ata2.00: status: { DRDY ERR }
[  856.626678] ata2.00: error: { ABRT }
[  856.633951] ata2.00: configured for UDMA/133
[  856.633963] ata2: EH complete
[  873.803500] ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[  873.803504] ata2.00: irq_stat 0x40000008
[  873.803508] ata2.00: failed command: READ FPDMA QUEUED
[  873.803514] ata2.00: cmd 60/08:00:00:a1:40/00:00:e0:00:00/40 tag 0 ncq 4096 in
[  873.803515]          res 41/04:00:00:a1:40/00:00:e0:00:00/40 Emask 0x401 (device error) <F>
[  873.803518] ata2.00: status: { DRDY ERR }
[  873.803520] ata2.00: error: { ABRT }
[  873.810833] ata2.00: configured for UDMA/133
[  873.810853] ata2: EH complete
[  876.168014] ata2.00: exception Emask 0x10 SAct 0x1 SErr 0x4090000 action 0xe frozen
[  876.168019] ata2.00: irq_stat 0x00400040, connection status changed
[  876.168022] ata2: SError: { PHYRdyChg 10B8B DevExch }
[  876.168025] ata2.00: failed command: READ FPDMA QUEUED
[  876.168031] ata2.00: cmd 60/08:00:00:a1:40/00:00:e0:00:00/40 tag 0 ncq 4096 in
[  876.168032]          res 40/00:04:00:a1:40/00:00:e0:00:00/40 Emask 0x10 (ATA bus error)
[  876.168035] ata2.00: status: { DRDY }
[  876.168040] ata2: hard resetting link
[  876.890281] ata2: SATA link down (SStatus 0 SControl 320)
[  881.885540] ata2: hard resetting link
[  882.205252] ata2: SATA link down (SStatus 0 SControl 320)
[  882.205269] ata2: limiting SATA link speed to 1.5 Gbps
[  887.200550] ata2: hard resetting link
[  887.520246] ata2: SATA link down (SStatus 0 SControl 310)
[  887.520255] ata2.00: disabled
[  887.520273] sd 1:0:0:0: [sdc]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  887.520278] sd 1:0:0:0: [sdc]  Sense Key : Aborted Command [current] [descriptor]
[  887.520283] Descriptor sense data with sense descriptors (in hex):
[  887.520285]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[  887.520295]         e0 40 a1 00
[  887.520299] sd 1:0:0:0: [sdc]  Add. Sense: No additional sense information
[  887.520303] sd 1:0:0:0: [sdc] CDB: Read(10): 28 00 e0 40 a1 00 00 00 08 00
[  887.520313] end_request: I/O error, dev sdc, sector 3762331904
[  887.520318] Buffer I/O error on device sdc1, logical block 470291232
[  887.520335] ata2: EH complete
[  887.520343] ata2.00: detaching (SCSI 1:0:0:0)
[  887.521778] sd 1:0:0:0: [sdc] Synchronizing SCSI cache
[  887.521809] sd 1:0:0:0: [sdc]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  887.521813] sd 1:0:0:0: [sdc] Stopping disk
[  887.521821] sd 1:0:0:0: [sdc] START_STOP FAILED
[  887.521823] sd 1:0:0:0: [sdc]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK


Can someone please give me advice if I can recover some data .

Thanks .


Peter
Top
 Profile  
 
lcoughey
 Post subject: Re: Click noise - Linux detects d drive - need advice (WD20E
PostPosted: March 26th, 2013, 11:34 
Offline
User avatar

Joined: February 9th, 2009, 16:13
Posts: 2574
Location: Ontario, Canada
If you want your data recovered with certainty, stop and send to a reputable lab. If they can recover the data without changing the heads, the price should be a lot less than $1500. However, if they cannot recover the data without changing the heads, there is absolutely nothing you can do on your own.

Talk to the lab in advance and make sure that they know your budgetary constraints and see if they are willing to physically assess and try to recover your data within you price limits. If after their physical assessment, the price is too high, knock your socks off with DIY procedures.

_________________
Luke
Recovery Force Data Recovery
Top
 Profile  
 
labtech
 Post subject: Re: Click noise - Linux detects d drive - need advice (WD20E
PostPosted: March 26th, 2013, 11:35 
Offline

Joined: August 18th, 2010, 17:35
Posts: 3669
Location: Massachusetts, USA
Sorry, but humbly the answer is no. Professional help is needed. And it better be a real pro as these drives are difficult to recover. Send them the external enclosure as well the data may be encrypted via hardware.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts
Top
 Profile  
 
peterf81
 Post subject: Re: Click noise - Linux detects d drive - need advice (WD20E
PostPosted: March 26th, 2013, 11:39 
Offline

Joined: March 26th, 2013, 11:08
Posts: 9
Location: Slovakistan
lcoughey wrote:
If you want your data recovered with certainty, stop and send to a reputable lab. If they can recover the data without changing the heads, the price should be a lot less than $1500. However, if they cannot recover the data without changing the heads, there is absolutely nothing you can do on your own.

Talk to the lab in advance and make sure that they know your budgetary constraints and see if they are willing to physically assess and try to recover your data within you price limits. If after their physical assessment, the price is too high, knock your socks off with DIY procedures.


Well they offered me discount (hey would treat it like a low priority job), it would last like 3 months (thats is not a problem for me) and save only the data i specified . But it was still like $900USD after discount.Not worth it for me . I better buy a robotic vacuum cleaner for that money since we have 2 cats :D

So I want to try DIY . I planned go and buy another 2TB drive (probably Seagate) and try to clone with Linux Rescue, thats what i read on internet . I hope all 2TB drives are same size, and the partition will fit on the new HDD . But you say I have only little hope to save data ?

Cannot afford $900USD right now --- it is more than my monthly income currently :\
Top
 Profile  
 
peterf81
 Post subject: Re: Click noise - Linux detects d drive - need advice (WD20E
PostPosted: March 27th, 2013, 15:42 
Offline

Joined: March 26th, 2013, 11:08
Posts: 9
Location: Slovakistan
Spildit wrote:
I think that according to your description you will need lots of luck for the drive to clone without the need of changing the heads ..... But miracles happen sometimes .... as long as the possibility for it to happen is not equal to 0.


Ddrescue cloning works first 150MB very fast, then it slows down but cca 800MB are rescued, then it stops with errsize: 1999 GB .

Code:
root@ubuntu:/mnt# ddrescue --no-split -r 2 -v /dev/sdd1 /mnt/seagate/wd.rescue /mnt/seagate/wd.logfile


About to copy 2 TBytes from /dev/sdd1 to /mnt/seagate/wd.rescue
    Starting positions: infile = 0 B,  outfile = 0 B
    Copy block size: 128 sectors
Sector size: 512  bytes
Max retries: 2   
Direct: no    Sparse: no    Split: no    Truncate: no

Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued:         0 B,  errsize:       0 B,  errors:       0
Current status
rescued:    30277 kB,  errsize:       0 B,  current rate:   30277 kB/s
rescued:   153944 kB,  errsize:       0 B,  current rate:    1421 kB/s
   ipos:   153944 kB,   errors:       0,    average rate:    1749 kB/s
rescued:   153964 kB,  errsize:    242 kB,  current rate:        0 B/s
rescued:   897949 kB,  errsize:   1999 GB,  current rate:     520 kB/s
   ipos:        2 TB,   errors:       2,    average rate:     899 kB/s
   opos:        2 TB,     time from last successful read:       0 s
Finished                       
root@ubuntu:/mnt#



Also with reverse mode I rescued 200MB from the end of drive .

Do you think a PCB swap help in this case -- how can i be sure it is mechanical issue ?
Top
 Profile  
 
peterf81
 Post subject: Re: Click noise - Linux detects d drive - need advice (WD20E
PostPosted: April 1st, 2013, 12:23 
Offline

Joined: March 26th, 2013, 11:08
Posts: 9
Location: Slovakistan
Spildit wrote:
If you can actualy read data from the start and from the end of the drive (check with hex editor to see if it actualy copy data or not) then pcb is working fine and swaping will make things worse as the problem is elswere, and no, you can't swap heads just because on youtube it apears to be a simple task. You will end up without data !
Send the drive to a pro. It's not a DIY case...


I did again some ddrescue attempts, mhdd did not detect drive .

Now drive stopped clicking --- but now partition is not detected at all and now it does not spin up at all and makes sound like this : http://www10.online-convert.com/download-file/5f1b0f956e9e8c97ee153ceed85ccd97/converted-3c261cd9.wav

Did it finally dieded ?
Top
 Profile  
 
peterf81
 Post subject: Re: Click noise - Linux detects d drive - need advice (WD20E
PostPosted: April 1st, 2013, 12:31 
Offline

Joined: March 26th, 2013, 11:08
Posts: 9
Location: Slovakistan
I think the drive is finished now which is good because I really had dilemma if I should spend 500$ (I found even a company for 350$ yesterday) for DR, because the data

-- maybe thousand pictures from various occasion from the last 10 years with people I will never meet again and places i will never visit again --

I lost them all . But it is all my fault, because i have at home DVD burner, empty DVDs, 5 harddrives --- but still I was lazy to back up them . Only explanation is the pictures were worthless for me --- or else I would back them up . So even I miss them, they do not deserve to be rescued --- because they were worthless for me for 10 years .

How much worth would be for you 1000 pictures from last 10 years ? From vacations, family and friends occasions, etc ...
Top
 Profile  
 
peterf81
 Post subject: Re: Click noise - Linux detects d drive - need advice (WD20E
PostPosted: April 1st, 2013, 15:29 
Offline

Joined: March 26th, 2013, 11:08
Posts: 9
Location: Slovakistan
Quote:
Save the drive.
Put the drive in a safe place.
If in the future you want to have it "recovered" you might send it in then.
As time passes by you will see life on a diferent way, and you might want to get those pictures back.
Also, as time passes by drives will be cheaper (hopefully) and one day there will be more and more data recovery specialists and prices will go down, especially when SSD starts to be the norm.....
Again, you can have the drive stored for some years without trouble and decide on recovering the files later.



This is very good advice . But if I want the drive replaced under warranty (it is only 15 months old) I have to send it to WD soon for replacement (or HP because it is HP usb3 external) :) so I have to decide again what to do . Anyway this is psychological issue not DR issue :)

But now I have a new idea --- I want to start my own DR business . First I buy cheap broken drive and try to fix them, or offer DR services for free without guarantee --- so I can learn about drives .

Then I ask a DR company if they want to emply me, I show them my skills .

And then I repair my own drive ! Do you think it could work out for me ?
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 1
  [ 8 posts ] 

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: napalm_atx and 37 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Switch to mobile style
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group