Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Iäm now logged in from knoppix. I did a big mistake while downloading Knoppix iso file. i had downloaded the deutch version instead of the english. All keyboard controls are jumbled now.So i have kept a english iso file for download.
Meanwhile , could u help me how to obtain dd(underscore)rescue from the knoppix terminal ? Couldnt find anything from the net.
From above page:
The best solution - both faster and more efficient - seems to be Antonio Diaz's 'ddrescue' (ddrescue): http://savannah.gnu.org/projects/ddrescue/
# download ddrescue
wget http://download.savannah.gnu.org/rel...ue-1.8.tar.bz2
# extract the source code
tar xjf ddrescue-1.8.tar.bz2
# compile ddrescue
cd ddrescue-1.8
./configure && make
# first, grab most of the error-free areas in a hurry:
./ddrescue -n /dev/old_disk /dev/new_disk rescued.log
# then try to recover as much of the dicy areas as possible:
./ddrescue -r 1 /dev/old_disk /dev/new_disk rescued.log
-----------------------
Check in knoppix whether you are root by the command: whoami
You should be root for most system tasks.
Check whether /dev/sdb exists in your system by the command: ls -l /dev/sd*
If sdb exists then I think you can proceed. (The disk does not have to be mounted for ddrescue to work).
I like following commands from the page I mentioned; these are simpler:
# first, grab most of the error-free areas in a hurry:
./ddrescue -n /dev/old_disk /dev/new_disk rescued.log
# then try to recover as much of the dicy areas as possible:
./ddrescue -r 1 /dev/old_disk /dev/new_disk rescued.log
Try them if command given by unSpawn does not work. But in above commands a clean disk (new_disk) should be available. In your case the defective disk may be sdb (old_disk) and you will have to have a new disk (may be a flash drive or external hard disk) which may be sdc. So the first command will become:
./ddrescue -n /dev/sdb /dev/sdc rescued.log
This thread is in software section, where most users are not looking for recovery problems. You may put a new thread in general section, giving link to this thread- so that more users/experts can see and help you.
I switched to root user and did fdisk -l but yet the sdb disk is not being detected.After all the purchases and setup, will everything be in vain ? Please give your valuable suggestion.
Also the disk was detected by BIOS.
I have also posted a link to the thread in Linux General as advised by rng.
- Run 'sudo fdisk -l' to verify both disks are attached and verify disk size. If same order is kept your desktop disk (size 250GB) will be /dev/sda.
The sdb wasn´t listed but on checking with ls command got the sdb listed.
Quote:
- Create a mount point for your ("D :") NTFS partition to write to: 'sudo mkdir /recovery'.
- Mount it: 'sudo ntfs-3g -o noatime,nocompression /dev/sda5 /recovery'.
done
Quote:
Else:
- open another terminal window and run 'sudo tail -f /tail -f /var/log/messages'. This should show you any warnings the kernel emits.
Got the following error -
tail: "/ tail" can not be opened for reading: No such file or directory
tail: "/ var / log / messages" can not be opened for reading: No such file or directory
Hello. This is the current progress displayed. Sorry for bloating the posts, but the attachment link was´t working. Iam worried about the succxfer and errxfer values..!!
Quote:
root@Microknoppix:~# dd_rescue -s 90G -l /recovery/dd_rescue.log -o /recovery/badblocks.log -f -v /dev/sdb /recovery/image.dd 2>&1 | tee /recovery/progress.log
dd_rescue: (info): about to transfer 0.0 kBytes from /dev/sdb to /recovery/image.dd
dd_rescue: (info): blocksizes: soft 65536, hard 512
dd_rescue: (info): starting positions: in 94371840.0k, out 94371840.0k
dd_rescue: (info): Logfile: /recovery/dd_rescue.log, Maxerr: 0
dd_rescue: (info): Reverse: no , Trunc: no , interactive: no
dd_rescue: (info): abort on Write errs: no , spArse write: if err
dd_rescue: (info): ipos: 94371840.0k, opos: 94371840.0k, xferd: 0.0k
errs: 0, errxfer: 0.0k, succxfer: 0.0k
+curr.rate: 0kB/s, avg.rate: 0kB/s, avg.load: 0.0%
dd_rescue: (info): problems at ipos 94371840.0k: Input/output error
fall back to smaller blocksize
dd_rescue: (info): ipos: 94371840.0k, opos: 94371840.0k, xferd: 0.0k
* errs: 0, errxfer: 0.0k, succxfer: 0.0k
+curr.rate: 0kB/s, avg.rate: 0kB/s, avg.load: 0.0%
dd_rescue: (warning): /dev/sdb (94371840.0k): Input/output error!
Once image file is made:
to check: sudo fsck -y /mnt/hdb1/hda1_rescue.img
to mount recovered file: sudo mount -o loop /mnt/hdb1/hda1_rescue.img /mnt/rescued
But you are right that these values are of concern:
succxfer: 0.0k
+curr.rate: 0kB/s, avg.rate: 0kB/s, avg.load: 0.0%
I´m atttaching the latest update from the dd_rescue which has been running for more than 17 hours. It has onlz processed 483k size files out of which all are error and no success.
It is obviously not working. I think you should interrupt it by control-C and try above mentioned commands which are simpler:
# first, grab most of the error-free areas in a hurry:
./ddrescue -n /dev/old_disk /dev/new_disk rescued.log
# then try to recover as much of the dicy areas as possible:
./ddrescue -r 1 /dev/old_disk /dev/new_disk rescued.log
There is a program called dd_rhelp (see links above) which works thru ddrescue but has simpler commands. Go through the links given above and try. I have limited experience in this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.