traumajohn said:
Hi, I tried the drive and the cradle on my laptop and had the same problem.
It detects it as a usb device and show it in Device manager active and
enabled but when I look into disk management I see it says unallocated. I can
not assign a drive letter and it doesn't say healthy just unallocated. I will
try to plug direct into my pc tonight and check.
Thanks,
JOhn
There is an example of a tool here, which attempts to recognize partitions
and repair the partition table. This particular web page, is giving a walk
through, of all the scenarios the tool might be able to fix. You don't go
through all that nonsense, if the thing isn't badly damaged.
http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step
For important data, data recovery requires some care. My procedure consists
of trying to back up the device, sector by sector, if possible first. Then,
if something goes wrong, there is still something to work with. (For that,
you can boot a Linux LiveCD and use the "dd" command, and there is also
a Windows port of dd available. What I don't know, is what happens if
bad sectors are detected during the transfer. I would not expect
exceptions to be handled well by a command like that.)
http://www.chrysocome.net/dd
(From a DOS prompt - dd if=/dev/hda of=/dev/hdb
This will copy drive hda to drive hdb. The naming convention is not the
same as "drive letters" or other things you're familiar with in Windows.
Using "dd --list" from the DOS prompt, will give the names of all
connected devices. Read the chrysocome web page for more information
about how the naming works. Real care must be used with this command,
as you can easily erase the wrong disk by accident when using it.)
The TestDisk tool is an "in-place" tool. It attempts to correct structures
directly on the affected disk. Such a method is not without risks. Other
recovery tools are "data scavengers". They try to recognize files on the
disk, rather than attempting a repair. There is an unending pile of $39.95
utilities of that sort. A potential advantage of that approach, is that
it may not necessarily attempt any write operations to the affected
disk.
For a scavenger, you should have enough disk space available
on another physical device, to hold the results of the scavenge. And
the files may not be in very good shape. A tool I used to use, names
the files file0001, file0002, and so on, so you have no idea what each
one contains, and some can contain fragments of files. You could conceivably
have more output files from a tool like that, than there were files on the
originating disk.
Another consideration, is the mechanical health of the disk itself.
In some cases, there are very few "start cycles" left in the disk, before
it becomes toast (and material for a real data recovery company). For example,
I had a disk which was showing signs of trouble. I was tired, so I decided
to go to bed, rather that fight with the thing. I turned on the disk the
next day, and it was inaccessible. Depending on the displayed symptoms,
the disk may not have much life left in it. In those cases, it is important
to plan a course of action which will result in the least stress to the
disk.
If you're not comfortable with recovery yourself, take the drive
to your IT staff and see what they can do for you.
Paul