No final das contas, tudo ficou muito simples após ler as duas páginas a seguir:

------------------------------------------------------------------------------------
a) “http://www.debianadmin.com/recover-data-from-a-damaged-hard-disk-using-dd_rhelp.html”:

dd_rhelp is a bash script that handles a very usefull program written in C which is called dd_rescue, it roughly act as the dd linux command with the caracteristic to
NOT stop when it falls on read/write errors.

=====> OBS.: Nesta página, eu descobri que o dd_rhelp era um “BASH SCRIPT”.

------------------------------------------------------------------------------------
b) “http://ubuntuforums.org/showthread.php?t=996717″:
([ubuntu] How to compile bash from an editor? - Ubuntu Forums.html)

Re: How to compile bash from an editor?
Last time on this one:

bash shell scripts are interpreted not compiled -- hence there is no reason to compile them.

If you want a personal .bash or .sh file, compose the file, save it, do the following:

chmod +x

Copy the file to your personal bin directory since this is in your path (you have to make the directory since its not included by default):
mkdir -p ~/bin

cp ~/bin/

Ok now you can run the shell script from the command line by simply typing

NO NEED TO COMPILE!!!

=====> OBS.: Nesta página, eu descobri que não é necessário (nem possível) compilar um bash script

-------------------------------------------------------------------------------------

Descompactei o arquivo dd_rhelp-0.1.2.tar.gz dentro da pasta dd_rhelp (que eu criei especificamente para guardar o .gz e vários .mht de páginas de dica).

Dentro da pasta dd_rhelp sugiu uma pasta chamada dd_rhelp-0.1.2.
Dentro da nova pasta havia um arquivo dd_rhelp (o Nautilus dizia que o tipo era “shell script”).
Copiei o arquivo dd_rhelp para a pasta /bin
Na pasta /bin, o Nautilus dizia que o tipo do arquivo era “unknow”.
Troquei o atributo “executable” do arquivo para true e o Nautilus passou a dizer que o tipo era “program”.
Obs.: o tipo do arquivo dd_rescue (que já estava em /bin é “executable”
A partir daí já era possível “executar” o dd_rhelp.

Veja o que eu fiz no Terminal:

$ cd /media/2N500XP/Down500XP/SoftDownload/UBUNTU/dd_rhelp/dd_rhelp-0.1.2 (change directory)
$ sudo cp dd_rhelp /bin (SuperUser usando o cp (copy))
$ sudo chmod +x dd_rhelp (SuperUser usando o chmod, que troca o atributo executable. Poderia ser também “sudo chmod 777 dd_rhelp”)
$ sudo dd_rhelp (Chamei o comando dd_rhelp)

Pronto ! Neste instante, o dd_rhelp respondeu:
Need 2 arguments…
usage: dd_rhelp {filename|device} {output-file} [{info}]
or dd_rhelp --help
or dd_rhelp --version

“INSTALADO !!!!!”

“dd_rhelp or GNU ddrescue will yield a complete disk image, faster but possibly with some errors. GNU ddrescue is generally much faster, as it is written entirely in C++, whereas dd_rhelp is a shell script acting as a frontend to dd_rescue. Both dd_rhelp and GNU ddrescue aim to copy data fast where there are no errors, then copy in smaller blocks and with retries where there are errors. GNU ddrescue is easy to use with default options, and can easily be downloaded and compiled on Linux-based Live CDs such as Knoppix, and can be used with SystemRescueCD.”
source:

Go to my harddrive died dot com putting all this together of course. Watch the videos, Scott Moulton is leading the industry in hardware data recovery. He explains how to do most data recoveries for under a 100$. I have personally followed his explanations and did platter swap, head swaps, pcb board swaps. In your case your plobably going to need to do a head swap. What ever you do don’t turn that HD on again, everytime you turn it on it is scratching more of your platters.

sudo dd_rhelp /dev/sda1 - | ssh username@machineip cat > “/datarecovery/backup.img”

I’m trying to copy from the hard drive dev/hdb (160gb ntfs) to media/Elements (500gb vfat external usb). I heard that vfat format could cause this to happen, any ideas how to get around it?

Cheers,

Kieran

robert@Humphrey:~/dd_rhelp-0.0.6$ sudo make install
make[1]: Entering directory `/home/robert/dd_rhelp-0.0.6′
test -z “/usr/local/bin” || mkdir -p -- . “/usr/local/bin”
/usr/bin/install -c ‘dd_rhelp’ ‘/usr/local/bin/dd_rhelp’
make[1]: Nothing to be done for `install-data-am’.
make[1]: Leaving directory `/home/robert/dd_rhelp-0.0.6′

Funny! So I looked at the makefile and sure enough, install-data-am is an empty reference. How did you guys get past this??

Thanks
Limbers

Although I should add that I also tried to use this on a physically damaged drive, and it naturally couldn’t do anything. I had to contact a few hard drive repair companies, and finally got in touch with one that worked well. Everyone was trying like mad to have me ship my drive without a quote! It was like a feeding frenzy! Fortunately I came across a company called Hard Drive . Good site, and the guy in charge really knew his stuff.

I just thought I should mention this, because although dd_rhelp is really good, in cases of physically damaged hard drives, it won’t help much.

Cal Janus
Tech Wizards LLC