3,240
edits
Changes
From SME Server
Jump to navigationJump to search→fifth step: get and run ddrutility
== Third step: run ddrescue ==
== Third step: run ddrescue ==
first pass to harvest all you can without forcing on failing sectors
ddrescue -v -n /dev/sdc1 sdb1.img sdb1.log
then you can get hard on it:
ddrescue -v --max-retries=3 /dev/sdc1 sdb1.img sdb1.log
== Fourth step: get and run ddrescueview ==
== Fourth step: get and run ddrescueview ==
Download and install in a bin dir, then chmod it
mkdir ~/bin; cp ddrescueview ~/bin
chmod +x ~/bin/ddrescueview
then get the graphic:
ddrescueview sdb1.log
== fifth step: get and run ddrutility ==
== fifth step: get and run ddrutility ==
first download and compile then install.
ddru_findbad sdb1.img sdb1.log
ddru_findbad sdb1.img sdb1.log
this command will then filter the output to know which files are corrupted, meaning on a badsector.
cat results_list.txt|grep -v 'File none'|sed -E 's/.*File (.*)$/\1/' >list
Be aware that there might also be some inodes lost for directories, meaning that your files are there but not at the intended place. You might need to dig more on that.
== sixth step: try to mount and recover ==
== sixth step: try to mount and recover ==
