Trying to get a 7200.11 to work
Posted 19 January 2013 - 02:42 PM
Posted 19 January 2013 - 03:00 PM
Check (have never tried it on an EXT3) DMDE:
for FAT/NTFS I find it an excellent tool (though not the easiest/most intuitive one around).
In any case BEFORE any attempt you should IMAGE the disk "as is" (possibly twice) with dd or similar.
If you search a bit in this same subforum you will easily find related thread talking of ddrescue/dd_rescue (Linux) or DataRescue DD (Windows).
Once you have the image(s) besides DMDE you may want to try directly TESTDISK, if it is a "simple" partition issue it will likely solve it, otherwise you are back to use "file based" recovery (that most probably - just like PHOTOREC) will have filenames lost .
There are post-processing tools for PHOTOREC output that help identify/verify (at least) the filetype and thus give the "right " extension, but the filename will be still lost.
If you are familiar with Linux there may be other tools for fixing/repairing an EXT 2 or 3 filesystem.
You also may want to have a go with this one (this should be the "simpler" to use - if the kind of damage is not too seious):
Posted 19 January 2013 - 04:56 PM
Posted 20 January 2013 - 03:45 AM
Well, you need another (much, much bigger) supply of patience.
If the drive "clicks" it means that it went beserk (as it's most common now) because of some "serious" error.
Attempting direct recovery from that device (i.e. as opposed to "from a copy/image") is a big risk and often, even if the "fix" worked the disk is NOT in a good state and access to it may be painfully slow and/or the presence of "bad sectors" or mis-mapping may be the cause of the slowness.
As said he advice is to image the disk (slowly or as slowly as the disk requires) and then work (quickly) on the image.
Well this is an assumption (in this case not supported by any evidence), if just the MBR and/or Partition table were corrupted, you would have no clicks and TESTDISK would have taken no more than a few minutes (unless a deep search would have become necessary).
Posted 20 January 2013 - 10:38 AM
Yep, which may also mean that what was recovered by the diskinternals run is simply "garbage" (or it may mean that having running the diskinternals tool on the original disk made it unreadable, due to overheating, simple wear and what not.
Try fully recovering (from the ones obtained by using the diskinternals tool) a few files that do have some metadata including filename.
MS Word .doc files - as an example - do store inside the file the name under which they were last saved, see:
It is also possible that DatarescueDD has some issues with the disk controller or with the environment you are running it in.
A "second opinion" (and a third, fourth, etc.) with other imaging tools is then needed.
You can also try to "image in sections" attempting both "forward" and "reverse" direction, see:
Posted 20 January 2013 - 11:12 AM
Posted 21 January 2013 - 04:35 PM
Posted 23 January 2013 - 07:57 AM
Posted 23 January 2013 - 09:35 AM
Posted 23 January 2013 - 10:32 AM
Shouldn't you be doing this under Linux? Or a Windows Guest on a Linux Host?
edit - more info -
How are you "accessing" it under Windows?
This post has been edited by submix8c: 23 January 2013 - 10:36 AM
Posted 24 January 2013 - 10:45 AM
- ← Barracuda ES.2 Spin but make 2 clicks and urresponsibe, terminal is no
- Hard Drive and Removable Media issues
- how to remove ata password in 7200.12 →