WD HDD is not detected

[rgirish]

Hi Guys,

I am novice but I need your help solving this.

I have this NAS Linkstation pro PRO LSV20TL model and one day due to power interruption it went down. Now when I try to start it it give me only red LED blink. It blinks 7 times red and then pause and then it blinks again. I contacted Buffalo inc and they said that means its a problem with HDD.

NOw I have taken the Hardrive out from Linkstation and put it in enclosure. When I connect it to laptop it spins for a while with its tick sound and then the tick sound stop then it get shown up in the device manager. Its not shown in the diskmgmt tool. I want to get my data back but its not detected on windows.

Then I tried on parted magic, testdata shows HDD but after analysis it doesnt show any partitions.

can someone please suggest? is it something HDD is not able to reach to starting point? why does it spin initially with tick tick sound and when sound stops after 2-3 minute then only show up in device manage/testdisk.

what are the chances of getting my data back? please suggest the way and which software is recommended.

Thank you

[pcimage]

Clicking and spin down 99/100 times means internal issues.

[rgirish]

Testdisk scans through all sectors lba etc but in the show no partition, it also says how many bad sectors thats means probably data is there, what are the chances of getting the data? Any tool that can?

[data-medics]

If the drive isn't spinning, then no software can read any sectors from it. Nor any tool for that matter.

You have to address the hardware issues first. If the data is wort spending ~$1000CAD then I'd say you should seek out a professional data recovery place such as this one: www.recoveryforce.com

Nothing you can do without proper tools, clean room, training in a case like this.

[rgirish]

Drive spins, I didnt say it does not, Its just that initially the spin is bit noisy ......testdisk scan the LBA's

[pcimage]

Misunderstood your post, I read it as the drive stops.

In that case, if you accept the DIY risks (I.e. You could cause irrreversable damage preventing future pro attempts) then you could clone they drive with some non-windows tool (I,e, dd_rescue or media tools pro) and then run something like UFS Explorer on the clone to try and recover the data.

[shahij]

Drive spins, I didnt say it does not, Its just that initially the spin is bit noisy ......testdisk scan the LBA's

If it detects, but still clicks, it's assumed there is/are media damage/bad sectors, or weak/bad head. It's recommended to go for Professional Service if data is irreplaceable! If you want DIY, then follow pcimage, but these has big pitfalls in such situation, the recovery chance may get low at the same time, there is/are possibility that your attempt might degrade the drive further, also increases the cost of recovery at the end whenever taken to Decent service after your retry.

[pcimage]

Drive spins, I didnt say it does not, Its just that initially the spin is bit noisy ......testdisk scan the LBA's

If it detects, but still clicks, it's assumed there is/are media damage/bad sectors, or weak/bad head. It's recommended to go for Professional Service if data is irreplaceable! If you want DIY, then follow pcimage, but these has big pitfalls in such situation, the recovery chance may get low at the same time, there is/are possibility that your attempt might degrade the drive further, also increases the cost of recovery at the end whenever taken to Decent service after your retry.

Exactly so.

Proper recovery shouldn't be too expensive as it stands now, but excessive tampering/DIY may well increase the cost for pro recovery exponentially at the least, or render it non recoverable in the worst case.

[rgirish]

i boot my laptop on knoppix and attached hdd on cavalry bridge and fired some commands you mentioned in the post. here is the output

knoppix@Microknoppix:/tmp$ file -s /dev/sdd*
/dev/sdd: ERROR: sticky cannot read `/dev/sdd' (Input/output error)
/dev/sdd1: writable, no read permission
/dev/sdd10: writable, no read permission
/dev/sdd11: writable, no read permission
/dev/sdd12: writable, no read permission
/dev/sdd13: writable, no read permission
/dev/sdd14: writable, no read permission
/dev/sdd15: writable, no read permission
/dev/sdd2: writable, no read permission
/dev/sdd3: writable, no read permission
/dev/sdd4: writable, no read permission
/dev/sdd5: writable, no read permission
/dev/sdd6: writable, no read permission
/dev/sdd7: writable, no read permission
/dev/sdd8: writable, no read permission
/dev/sdd9: writable, no read permission


knoppix@Microknoppix:/tmp$ ls -l /dev/sdd*
brw-rw---T 1 root floppy 8, 48 Mar 8 22:09 /dev/sdd
brw-rw---- 1 root disk 8, 49 Mar 8 21:26 /dev/sdd1
brw-rw---- 1 root disk 8, 58 Mar 8 21:26 /dev/sdd10
brw-rw---- 1 root disk 8, 59 Mar 8 21:26 /dev/sdd11
brw-rw---- 1 root disk 8, 60 Mar 8 21:26 /dev/sdd12
brw-rw---- 1 root disk 8, 61 Mar 8 21:26 /dev/sdd13
brw-rw---- 1 root disk 8, 62 Mar 8 21:26 /dev/sdd14
brw-rw---- 1 root disk 8, 63 Mar 8 21:26 /dev/sdd15
brw-rw---- 1 root disk 8, 50 Mar 8 21:26 /dev/sdd2
brw-rw---- 1 root disk 8, 51 Mar 8 21:26 /dev/sdd3
brw-rw---- 1 root disk 8, 52 Mar 8 21:26 /dev/sdd4
brw-rw---- 1 root disk 8, 53 Mar 8 21:26 /dev/sdd5
brw-rw---- 1 root disk 8, 54 Mar 8 21:26 /dev/sdd6
brw-rw---- 1 root disk 8, 55 Mar 8 21:26 /dev/sdd7
brw-rw---- 1 root disk 8, 56 Mar 8 21:26 /dev/sdd8
brw-rw---- 1 root disk 8, 57 Mar 8 21:26 /dev/sdd9

knoppix@Microknoppix:/tmp$ sudo mount -t xfs /dev/sdd2 lst10
mount: /dev/sdd2 is not a valid block device



so it looks like i cant mount anything ... any idea or suggestion ?

[brunof]

rgirish, i would try some tools like smartctl(linux) or diskchekup for windows (http://www.passmark.com/products/diskcheckup.htm) and verify the healthy of disk.
Later I think you could give a try for ddrescue.
Ps:The dmesg command may show you more info #dmesg | grep sdd

Regards,
Bruno.