Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i am having SATA 500gb hdd which is having problem. the problem is with header which has started making noise. I have checked smartctl and it's result=Failed. But still all data on HDD is accessible.
You will (probably) be better off running the rsync one at a time. Then they won't interfere with each other, forcing the disk heads all over the place. Two are status "D", which means they are waiting on I/O to the disk. Could be either disk.
I am asking because I recently had a failing ssd which started giving random errors. I found advice with a google search which recommended using dd from a live cd:
dd if=/dev/sda1 of=/media/large_ext_drive/sda1.img bs=16M
I then run fsck against the image since it seems like a bad idea to use this on a failing drive.
fsck.ext4 -pvf /media/large_ext_drive/sda1.img
I mounted the image file with:
mount -o loop -t ext4 /media/large_ext_drive/sda1.img /mnt/original
I finally used rsync to clone the contents of /mnt/original to a new drive, made the appropriate changes to fstab & installed grub.
Using dd for forensic work is an excellent use. Particularly if you intend to operate on the image as you did. So yes the OP could have created images on sdb1 then recovered from them.
Didn't seem likely that was the intent - it I was mistaken I'm happy to recant.
This is not forensic use, this is a rescue operation. I highly recommend to use ddrescue for that. dd and rsync will have problems with failing drives, ddrescue will skip failing sectors and continue to copy readable parts of the disk. After copying those it will return to try to read the unreadable sectors. This method is better for rescue operations, since all readable parts are copied before stressing the disk with repeatedly trying to read the unreadable parts.