samir_aguiar wrote:
Well, actually you're right, I'm not familiar with Linux systems.
In that case, you have been very lucky that your guess of dd_rescue command just failed, instead of doing something that would overwrite your data. As I said before, this is
not the sort of work where guessing is a good idea, if you care about your data.
samir_aguiar wrote:
What can I do to be sure which is my bad drive and which is not?
You would need to learn some Linux - start with reading about "dmesg"
samir_aguiar wrote:
I don't really know the commands, if you can guide me or if I need to install another Linux it would be fine.
Unfortunately for you, I am too busy with paid work, to give the level of help which you would need for free. IMHO you will have to find someone else who is less busy to help you, or pay for professional help.
Your system configuration is also unclear to me, from your description - I
think you have the "problem" disk now in a USB case (that is not usually the best configuration - direct SATA attach for a failing disk gives more control over retries etc.), and you say you have bought another disk of the same size (500GB) as the "problem" disk. However it seems you have installed Windows onto that replacement disk. Therefore you cannot clone the whole "problem" disk onto the replacement disk and
also keep any data which is now on the replacement disk.
As Ana (
poehere) also explained, the cloning process is just the first stage (and often you need to have some skills with your cloning tool to get the best result: it is not necessarily a "press and go" technique). After that has been done, you need
more spare disk space (at least the size of the disk space actually
used for files on the "problem disk"), to hold the recovered files after you run (your choice of) data recovery software (like R-Studio etc. etc.) on the clone image.
So although your system configuration is not clear to me, it
seems to me that you don't have enough empty (scratch) disk space to complete this process. As always, doing DIY recovery has risks, and using professional disk imaging equipment may be more successful than using DIY tools - it's your data, so it's your choice.
samir_aguiar wrote:
I just wanted to recover some files which were on partition D:\, but I think the drive lost its partition information... Also, both drives (the working one and the bad one) are 500 GB, would that make it harder to create a clone?
As I said, your full system config now (e.g. what is installed on the replacement disk, and whether you have more spare disks etc.) is not clear to me. Read my comments above - they might answer your question. To make things simple for you, I would definitely suggest that you clone the whole disk, and not just one partition.
samir_aguiar wrote:
What's the difference between that command and using Norton Ghost, for example?
Norton Ghost is not designed to cope with any unreadable sectors - no extra retries are done, no change of block size, no option for reverse copy (at least not in the versions I have seen). I think some versions can be told to ignore sectors with CRC errors (instead of aborting the copy, which is the default behaviour I've seen in the past), but Ghost will still give a worse result on any flaky disk, than even primitive software like dd_rescue etc.
I'm glad I was able to answer some of your questions, but you have now received all the time which I can spend on this issue at the moment. Good luck.