Re: Help with ddrescue
Quoting German (gentger...@gmail.com): > On Tue, 12 May 2015 11:31:10 +0100 > Lisi Reisz wrote: > > On Tuesday 12 May 2015 11:18:34 German wrote: > > > On Tue, 12 May 2015 08:57:28 +0100 > > > Lisi Reisz wrote: > > > > On Tuesday 12 May 2015 01:15:20 German wrote: > > > > > Well, Wanderer, I got the drive cloned, it took three days, > > > > > with no positive results. > > > > > > > > What results did you expect? You cloned it. You now presumablty > > > > have a clone. You can now work on the clone. What else? > > > > > > > > USB is very slow. Might you be able to work on teh clone more > > > > directly? > > > > > > Great. And what this work involves? It involves taking ownership of the problem, looking round for tools to use, trying them out, seeing if they recover your data, deciding if you need to try other tools, how much you're prepared to pay for them, and so on. NTFS is a bit of a side-issue on a Debian User list, though it flattering to be called "experts". There may be better forums to post in if you get stuck. Grepping /var/lib/apt/lists/*Packages for ntfs doesn't turn up a lot, as might be expected. scrounge-ntfs has already been mentioned. Have you googled ntfs recovery yet? I see both free and paid-for tools there, and reviews of the such. > > People have made a lot of suggestions in this thread. > > Just rereading the thread, couldn't find any. What tools to use and how > to use them? No, well, the thread kind of stalled while you were persuaded to duplicate the drive. You asked "What will this duplication accomplish? What advantages if I am duplicate? After I duplicate the drive, what are my next steps?" and to the reply, you wrote "What will happen when I duplicate drive? Why is that failed drive is failed and duplicated drive might be repairable? If it's duplicated, it will be exactly the same, no? Confused. And bad drive is physically ok I think, it is just something wrong with file system. MTF?" Then we had the command format to discuss: "Where sdd is my failed drive. sdc is my spare drive. The correct procedure will be ddrescue if=/dev/sdd1 of=/dev/sdc ?" and later "ddrescue /dev/sdd /dev/sdc /dev/sda2/ddrescue.log will work?" (The answer is on the manpage, under "synopsis".) Now you have the disk cloned. This is when the real work begins. If you're lucky, it may go swimmingly and you'll recover lots. It may need a lot of decisions, backtracking and so forth. No one knows until you try. But you're going to have to read the instructions on using those tools carefully, and follow them. You may end up having to use tools that we don't have and in which Debian users don't have much interest. So you really need to drive the process forward yourself. It just requires a bit of confidence. And remember, you're working on a copy, so there's room for mistakes. Good luck! Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150512161026.GA8118@alum
Re: Help with ddrescue
On Tue, 12 May 2015 12:25:47 +0100 Lisi Reisz wrote: > On Tuesday 12 May 2015 11:38:18 German wrote: > > Just rereading the thread, couldn't find any. What tools to use and > > how to use them? > > You could start with the first two messages in the thread, other than > yours. Counting yours, the second and fourth: > > Gary Dale said: > "Next you can run whatever rescue software you like on the failed.img > file to see if you can recover anything. I usually start off with > something simple like fsck before trying testdisk." > > The Wanderer gave you a detailed recovery plan. Try reading what he > advised. I find I can't really just pick out one little sound bite - > but he also says to start with fsck. Just to add to this, take a look at the package "scrounge-ntfs": Description-en: Data recovery program for NTFS filesystems Utility that can rescue data from corrupted NTFS partitions writes the files retrieved to another working file system. AFAIK, there is no "fsck.ntfs". Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgpB8A1ajqQlK.pgp Description: OpenPGP digital signature
Re: Help with ddrescue
On Tuesday 12 May 2015 11:38:18 German wrote: > On Tue, 12 May 2015 11:31:10 +0100 > > Lisi Reisz wrote: > > On Tuesday 12 May 2015 11:18:34 German wrote: > > > On Tue, 12 May 2015 08:57:28 +0100 > > > > > > Lisi Reisz wrote: > > > > On Tuesday 12 May 2015 01:15:20 German wrote: > > > > > Well, Wanderer, I got the drive cloned, it took three days, > > > > > with no positive results. > > > > > > > > What results did you expect? You cloned it. You now presumablty > > > > have a clone. You can now work on the clone. What else? > > > > > > > > USB is very slow. Might you be able to work on teh clone more > > > > directly? > > > > > > > > Lisi > > > > > > Great. And what this work involves? > > > > People have made a lot of suggestions in this thread. > > > > Lisi > > Just rereading the thread, couldn't find any. What tools to use and how > to use them? You could start with the first two messages in the thread, other than yours. Counting yours, the second and fourth: Gary Dale said: "Next you can run whatever rescue software you like on the failed.img file to see if you can recover anything. I usually start off with something simple like fsck before trying testdisk." The Wanderer gave you a detailed recovery plan. Try reading what he advised. I find I can't really just pick out one little sound bite - but he also says to start with fsck. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505121225.47439.lisi.re...@gmail.com
Re: Help with ddrescue
On Tue, 12 May 2015 06:18:34 -0400 German wrote: > On Tue, 12 May 2015 08:57:28 +0100 > Lisi Reisz wrote: > > > On Tuesday 12 May 2015 01:15:20 German wrote: > > > Well, Wanderer, I got the drive cloned, it took three days, with > > > no positive results. > > > > What results did you expect? You cloned it. You now presumablty > > have a clone. You can now work on the clone. What else? > > > > USB is very slow. Might you be able to work on teh clone more > > directly? > > > > Lisi > > > > > > Great. And what this work involves? The original drive had a broken file system. You cloned it. "Cloning" means to make an identical copy. You now have a clone with a broken file system. That means that you can now try to fix the file system on that clone - avoiding to touch the original, possibly broken drive. Read through this thread again, now that you have something to work with. Many good suggestions have been made here. The error message you posted even suggests a fix: "NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important!" Why not start there? Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgpzgxY8cnjP0.pgp Description: OpenPGP digital signature
Re: Help with ddrescue
On Tue, 12 May 2015 11:31:10 +0100 Lisi Reisz wrote: > On Tuesday 12 May 2015 11:18:34 German wrote: > > On Tue, 12 May 2015 08:57:28 +0100 > > > > Lisi Reisz wrote: > > > On Tuesday 12 May 2015 01:15:20 German wrote: > > > > Well, Wanderer, I got the drive cloned, it took three days, > > > > with no positive results. > > > > > > What results did you expect? You cloned it. You now presumablty > > > have a clone. You can now work on the clone. What else? > > > > > > USB is very slow. Might you be able to work on teh clone more > > > directly? > > > > > > Lisi > > > > Great. And what this work involves? > > People have made a lot of suggestions in this thread. > > Lisi > > Just rereading the thread, couldn't find any. What tools to use and how to use them? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150512063818.6c891...@asterius.asterius.net
Re: Help with ddrescue
On Tuesday 12 May 2015 11:18:34 German wrote: > On Tue, 12 May 2015 08:57:28 +0100 > > Lisi Reisz wrote: > > On Tuesday 12 May 2015 01:15:20 German wrote: > > > Well, Wanderer, I got the drive cloned, it took three days, with no > > > positive results. > > > > What results did you expect? You cloned it. You now presumablty > > have a clone. You can now work on the clone. What else? > > > > USB is very slow. Might you be able to work on teh clone more > > directly? > > > > Lisi > > Great. And what this work involves? People have made a lot of suggestions in this thread. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505121131.10049.lisi.re...@gmail.com
Re: Help with ddrescue
On Tue, 12 May 2015 08:57:28 +0100 Lisi Reisz wrote: > On Tuesday 12 May 2015 01:15:20 German wrote: > > Well, Wanderer, I got the drive cloned, it took three days, with no > > positive results. > > What results did you expect? You cloned it. You now presumablty > have a clone. You can now work on the clone. What else? > > USB is very slow. Might you be able to work on teh clone more > directly? > > Lisi > > Great. And what this work involves? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150512061834.57347...@asterius.asterius.net
Re: Help with ddrescue
On Tuesday 12 May 2015 01:15:20 German wrote: > Well, Wanderer, I got the drive cloned, it took three days, with no > positive results. What results did you expect? You cloned it. You now presumablty have a clone. You can now work on the clone. What else? USB is very slow. Might you be able to work on teh clone more directly? Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505120857.28184.lisi.re...@gmail.com
Re: Help with ddrescue
On Fri, 08 May 2015 19:52:04 -0400 The Wanderer wrote: > On 05/08/2015 at 07:33 PM, German wrote: > > > On Fri, 08 May 2015 19:20:37 -0400 > > The Wanderer wrote: > > > >> On 05/08/2015 at 07:08 PM, German wrote: > > >>> That's what I got: > >>> > >>> spore@asterius:~$ lsblk > >>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > >>> sda 8:00 119.2G 0 disk > >>> ├─sda1 8:10 512M 0 part /boot/efi > >>> ├─sda2 8:20 111.3G 0 part / > >>> └─sda3 8:30 7.4G 0 part [SWAP] > >>> sdb 8:16 0 465.8G 0 disk > >>> sdc 8:32 0 1.8T 0 disk /media/spore/9F86-0131 > >>> sdd 8:48 0 1.8T 0 disk > >>> └─sdd1 8:49 0 1.8T 0 part > >>> > >>> Where sdd is my failed drive. sdc is my spare drive. The correct > >>> procedure will be ddrescue if=/dev/sdd1 of=/dev/sdc ? > >> > >> No. That might potentially work (except that, if I'm reading the > >> ddrescue man page correctly, the syntax is wrong), but it wouldn't > >> be correct. > >> > >> First, unmount /dev/sdc. > > Note for the record: The other steps will erase any data which is > presently on /dev/sdc. I figure you probably already know that, but I > just want to be explicit about it. > > >> Then do one of two things: > >> > >> 1) Create /dev/sdc1 (as an unformatted partition, using fdisk or > >> parted or whatever partitioning tool you choose), and then run > >> > >> ddrescue /dev/sdd1 /dev/sdc1 /any/path/you/want/ddrescue.log > >> > >> 2) run > >> > >> ddrescue /dev/sdd /dev/sdc /any/path/you/want/ddrescue.log > > > > Ok, I think I am getting closer. How big is a log file? > > The size of the log file depends on two things: the size of the data > source which is being copied/rescued, and the number of errors which > occur while attempting to read that data source. > > It can be very small, or it can be moderately large. Even in a > ridiculous case, however, I wouldn't expect it to be more than a few > hundred megs - unless the source drive is so bad that you're not going > to be getting any data back off of it anyway. > > > Can it be anywhere on all drives that have enough space? For > > instance: > > > > ddrescue /dev/sdd /dev/sdc /dev/sda2/ddrescue.log will work? > > Not quite. /dev/sda2/ is not a directory; it's a device node. > > Since /dev/sda2 is mounted to / (the root filesystem), the correct > equivalent to this command would be: > > ddrescue /dev/sdd /dev/sdc /ddrescue.log > > and although I wouldn't advise storing a log file in the root > directory, the command should work. > > The log file itself can be placed in any writable location which has > enough space. > Well, Wanderer, I got the drive cloned, it took three days, with no positive results. What to do? Forget about it and try to format? Error mounting /dev/sdc1 at /media/spore/FreeAgent GoFlex Drive: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sdc1" "/media/spore/FreeAgent GoFlex Drive"' exited with non-zero exit status 13: ntfs_mst_post_read_fixup_warn: magic: 0x09401dc4 size: 1024 usa_ofs: 43473 usa_count: 27729: Invalid argument Record 17625 has no FILE magic (0x9401dc4) Inode is corrupt (5): Input/output error Index root attribute missing in directory inode 5: Input/output error Failed to mount '/dev/sdc1': Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150511201520.3aa9a...@asterius.asterius.net
Re: Help with ddrescue
German wrote: > Bob Proulx wrote: > > ddrescue if=/dev/sdX of=/dev/sdY /var/tmp/rescuelogfile > > Hmm.. The Wanderer suggest that *if= and of=* is the wrong syntax. Argh! I have made two typos in the space of the last two messages. I can't believe I made a mistake this silly. > He says that this should be simple as this: > > ddrescue /dev/sdX /dev/sdY /path/to/logfile > > Who is right? The Wanderer is correct. The if= and of= is 'dd' syntax not 'ddrescue'. I goofed up the suggestion. With ddrescue there are three arguments, infile, outfile and logfile. When reading postings such as these one should always read the official documentation. That would clear all of it up authoritatively. For ddrescue here is the documentation online. http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html Bob signature.asc Description: Digital signature
Re: Help with ddrescue
On Fri, 08 May 2015 19:52:04 -0400 The Wanderer wrote: > On 05/08/2015 at 07:33 PM, German wrote: > > > On Fri, 08 May 2015 19:20:37 -0400 > > The Wanderer wrote: > > > >> On 05/08/2015 at 07:08 PM, German wrote: > > >>> That's what I got: > >>> > >>> spore@asterius:~$ lsblk > >>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > >>> sda 8:00 119.2G 0 disk > >>> ├─sda1 8:10 512M 0 part /boot/efi > >>> ├─sda2 8:20 111.3G 0 part / > >>> └─sda3 8:30 7.4G 0 part [SWAP] > >>> sdb 8:16 0 465.8G 0 disk > >>> sdc 8:32 0 1.8T 0 disk /media/spore/9F86-0131 > >>> sdd 8:48 0 1.8T 0 disk > >>> └─sdd1 8:49 0 1.8T 0 part > >>> > >>> Where sdd is my failed drive. sdc is my spare drive. The correct > >>> procedure will be ddrescue if=/dev/sdd1 of=/dev/sdc ? > >> > >> No. That might potentially work (except that, if I'm reading the > >> ddrescue man page correctly, the syntax is wrong), but it wouldn't > >> be correct. > >> > >> First, unmount /dev/sdc. > > Note for the record: The other steps will erase any data which is > presently on /dev/sdc. I figure you probably already know that, but I > just want to be explicit about it. > > >> Then do one of two things: > >> > >> 1) Create /dev/sdc1 (as an unformatted partition, using fdisk or > >> parted or whatever partitioning tool you choose), and then run > >> > >> ddrescue /dev/sdd1 /dev/sdc1 /any/path/you/want/ddrescue.log > >> > >> 2) run > >> > >> ddrescue /dev/sdd /dev/sdc /any/path/you/want/ddrescue.log > > > > Ok, I think I am getting closer. How big is a log file? > > The size of the log file depends on two things: the size of the data > source which is being copied/rescued, and the number of errors which > occur while attempting to read that data source. > > It can be very small, or it can be moderately large. Even in a > ridiculous case, however, I wouldn't expect it to be more than a few > hundred megs - unless the source drive is so bad that you're not going > to be getting any data back off of it anyway. > > > Can it be anywhere on all drives that have enough space? For > > instance: > > > > ddrescue /dev/sdd /dev/sdc /dev/sda2/ddrescue.log will work? > > Not quite. /dev/sda2/ is not a directory; it's a device node. > > Since /dev/sda2 is mounted to / (the root filesystem), the correct > equivalent to this command would be: > > ddrescue /dev/sdd /dev/sdc /ddrescue.log > > and although I wouldn't advise storing a log file in the root > directory, the command should work. > > The log file itself can be placed in any writable location which has > enough space. > UPDATE: Digging into it more, I found out Gentoo small tutorial and it was almost as you suggested, but with -f and -n flag. Here it is: Disk to Disk In this scenario the hard disk drive /dev/sdb is about to fail and we want to create an exact copy on a new hard disk drive /dev/sdc, which should be at least the same size as the source drive. First round, we just copy every block without read error and log the errors into /root/rescue.log Warning All data on /dev/sdc will be lost and also are the partitions or partition table, if any. root #ddrescue -f -n /dev/sdb /dev/sdc /root/rescue.log Second round, we copy only the bad blocks and try 3 times to read from source before we give up root #ddrescue -d -f -r3 /dev/sdb /dev/sdc /root/rescue.log Now the new drive could be mounted and the file system checked for corruption I am running ddrescue now for 7 hours. 595000 mb rescued. The speed fell off for some reason. In the beginning, it was about 54000, now just 6000. Have no idea why this is. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150509030944.284b7...@asterius.asterius.net
Re: Help with ddrescue
On Fri, 8 May 2015 17:15:51 -0400 German wrote: > On Fri, 8 May 2015 22:05:40 +0100 > Lisi Reisz wrote: > > > On Friday 08 May 2015 21:58:12 German wrote: > > > It's happened when I was > > > installing Lubuntu. > > > > Post hoc doesn't necessarily imply propter hoc. > > > > http://en.wikipedia.org/wiki/Post_hoc_ergo_propter_hoc > > > > Lisi > > > > > > You are philosopher. In meanwhile I think that that what caused the > problem. I also have internal drive which couldn't be mounted after > install of Lubuntu. Interesting enough, after installing Debian on the > same system, my internal drive became fully operational. :) About a week ago, I did a kernel upgrade. When I rebooted the system, X wouldn't run, and the mouse cursor was locked in position. I installed another kernel and rebooted. X came up fine, but the mouse still wouldn't work. I spent an hour digging through logs, unloading and loading modules and so on, before I determined it was the battery in the mouse[1]. What Lisi is saying is that just because two things happened at the same time, _does not mean_ that they are related. Petter [1] *groan* -- "I'm ionized" "Are you sure?" "I'm positive." pgpW3_DGxe8kN.pgp Description: OpenPGP digital signature
Re: Help with ddrescue
On 5/8/2015 5:28 PM, German wrote: On Fri, 08 May 2015 19:52:04 -0400 The Wanderer wrote: Not quite. /dev/sda2/ is not a directory; it's a device node. Since /dev/sda2 is mounted to / (the root filesystem), the correct equivalent to this command would be: ddrescue /dev/sdd /dev/sdc /ddrescue.log and although I wouldn't advise storing a log file in the root directory, the command should work. The log file itself can be placed in any writable location which has enough space. Thank you I started ddrescue and it is going somewhere. Probably will take 10 hours or more to complete. I'll let you know how it's all went. Thank you once more. It refused to work as we wanted and asked for --force option ( -f) Looks like I am late to the party and this part got sorted already. For future reference, for people helping, there was a previous thread... https://lists.debian.org/debian-user/2015/04/msg01639.html The problem disk is a Seagate GoFlex. Testdisk deep scan only listed the smaller FAT partition not the NTFS partition. Later, Seeker -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d9a8d.6040...@comcast.net
Re: Help with ddrescue
On 5/8/2015 10:20 AM, German wrote: On Fri, 08 May 2015 12:10:38 -0400 Gary Dale wrote: On 08/05/15 10:32 AM, German wrote: Hi list. Ok, now I have a spare 2TB USB drive where I can save .img file. Is that the right procedure? Do I have make a snapshot of failed drive and transfer it as a .img file to a spare drive, correct? R-studio for linux can display files of failed drive ( TestDisk coudn't do it ). So now I think I'll proceed. What is exact command to do it with ddrescue and what file system the spare drive has to be formated? Thank you very much! You can try ddrescue if=/dev/sdb1 of=failed.img where /dev/sdb1 would be the partition that you want to recover. Using 'dd' would be 'dd if=something of=something' ddrescue is 'ddrescue [options] [source] [destination] [logfile]' Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. So, if failed drive is for instance /dev/sdb and spare drive is for isntance /dev/sdc, the right command will be ddrescue if=/dev/sdb of=/dev/sdc/failed.img ? And also, you didn't answer this, what file system the a spare drive ahs to be formated? Thanks. First I would use fdisk to see the size of the drives, not all 2 terabyte drives will be identical in size fdisk -l -l tells fdisk to list the drives. If the destination is larger, no issues, if it is smaller, might still work but may lead to issues later on. Going directly from one device to another, you have to use the force option to overwrite the destination. ddrescue --force /dev/sdb /dev/sdc /home/someusername/ddrescue.log If you go to an image, then you would have to mount the location ahead of time and specify a filename. ddrescue /dev/sdb /mnt/sdc1/rescued.img /home/someusername/ddrescue.log Here is a link to a guide... https://www.technibble.com/guide-using-ddrescue-recover-data/ There is a possibility that going device to device ddrescue might get enough to make a working clone, but I would go into it with the assumption that either way you will need to run recovery software and have yet another drive to recover to. The disadvantage of running recovery software on a failing disk, is the more you do to the disk the higher the risk it will get worse. The advantage of creating an image or clone is that once you have a copy on a good drive can keep trying different recovery options without having to worry about the drive getting worse. The disadvantage is that you need space that is equal to the size of the old drive plus room for all the files you want to recover. Later, Seeker -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d8d5b.40...@comcast.net
Re: Help with ddrescue
On Fri, 08 May 2015 19:52:04 -0400 The Wanderer wrote: > On 05/08/2015 at 07:33 PM, German wrote: > > > On Fri, 08 May 2015 19:20:37 -0400 > > The Wanderer wrote: > > > >> On 05/08/2015 at 07:08 PM, German wrote: > > >>> That's what I got: > >>> > >>> spore@asterius:~$ lsblk > >>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > >>> sda 8:00 119.2G 0 disk > >>> ├─sda1 8:10 512M 0 part /boot/efi > >>> ├─sda2 8:20 111.3G 0 part / > >>> └─sda3 8:30 7.4G 0 part [SWAP] > >>> sdb 8:16 0 465.8G 0 disk > >>> sdc 8:32 0 1.8T 0 disk /media/spore/9F86-0131 > >>> sdd 8:48 0 1.8T 0 disk > >>> └─sdd1 8:49 0 1.8T 0 part > >>> > >>> Where sdd is my failed drive. sdc is my spare drive. The correct > >>> procedure will be ddrescue if=/dev/sdd1 of=/dev/sdc ? > >> > >> No. That might potentially work (except that, if I'm reading the > >> ddrescue man page correctly, the syntax is wrong), but it wouldn't > >> be correct. > >> > >> First, unmount /dev/sdc. > > Note for the record: The other steps will erase any data which is > presently on /dev/sdc. I figure you probably already know that, but I > just want to be explicit about it. > > >> Then do one of two things: > >> > >> 1) Create /dev/sdc1 (as an unformatted partition, using fdisk or > >> parted or whatever partitioning tool you choose), and then run > >> > >> ddrescue /dev/sdd1 /dev/sdc1 /any/path/you/want/ddrescue.log > >> > >> 2) run > >> > >> ddrescue /dev/sdd /dev/sdc /any/path/you/want/ddrescue.log > > > > Ok, I think I am getting closer. How big is a log file? > > The size of the log file depends on two things: the size of the data > source which is being copied/rescued, and the number of errors which > occur while attempting to read that data source. > > It can be very small, or it can be moderately large. Even in a > ridiculous case, however, I wouldn't expect it to be more than a few > hundred megs - unless the source drive is so bad that you're not going > to be getting any data back off of it anyway. > > > Can it be anywhere on all drives that have enough space? For > > instance: > > > > ddrescue /dev/sdd /dev/sdc /dev/sda2/ddrescue.log will work? > > Not quite. /dev/sda2/ is not a directory; it's a device node. > > Since /dev/sda2 is mounted to / (the root filesystem), the correct > equivalent to this command would be: > > ddrescue /dev/sdd /dev/sdc /ddrescue.log > > and although I wouldn't advise storing a log file in the root > directory, the command should work. > > The log file itself can be placed in any writable location which has > enough space. > Thank you I started ddrescue and it is going somewhere. Probably will take 10 hours or more to complete. I'll let you know how it's all went. Thank you once more. It refused to work as we wanted and asked for --force option ( -f) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508202815.04123...@asterius.asterius.net
Re: Help with ddrescue
On 05/08/2015 at 07:33 PM, German wrote: > On Fri, 08 May 2015 19:20:37 -0400 > The Wanderer wrote: > >> On 05/08/2015 at 07:08 PM, German wrote: >>> That's what I got: >>> >>> spore@asterius:~$ lsblk >>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >>> sda 8:00 119.2G 0 disk >>> ├─sda1 8:10 512M 0 part /boot/efi >>> ├─sda2 8:20 111.3G 0 part / >>> └─sda3 8:30 7.4G 0 part [SWAP] >>> sdb 8:16 0 465.8G 0 disk >>> sdc 8:32 0 1.8T 0 disk /media/spore/9F86-0131 >>> sdd 8:48 0 1.8T 0 disk >>> └─sdd1 8:49 0 1.8T 0 part >>> >>> Where sdd is my failed drive. sdc is my spare drive. The correct >>> procedure will be ddrescue if=/dev/sdd1 of=/dev/sdc ? >> >> No. That might potentially work (except that, if I'm reading the >> ddrescue man page correctly, the syntax is wrong), but it wouldn't be >> correct. >> >> First, unmount /dev/sdc. Note for the record: The other steps will erase any data which is presently on /dev/sdc. I figure you probably already know that, but I just want to be explicit about it. >> Then do one of two things: >> >> 1) Create /dev/sdc1 (as an unformatted partition, using fdisk or >> parted or whatever partitioning tool you choose), and then run >> >> ddrescue /dev/sdd1 /dev/sdc1 /any/path/you/want/ddrescue.log >> >> 2) run >> >> ddrescue /dev/sdd /dev/sdc /any/path/you/want/ddrescue.log > > Ok, I think I am getting closer. How big is a log file? The size of the log file depends on two things: the size of the data source which is being copied/rescued, and the number of errors which occur while attempting to read that data source. It can be very small, or it can be moderately large. Even in a ridiculous case, however, I wouldn't expect it to be more than a few hundred megs - unless the source drive is so bad that you're not going to be getting any data back off of it anyway. > Can it be anywhere on all drives that have enough space? For > instance: > > ddrescue /dev/sdd /dev/sdc /dev/sda2/ddrescue.log will work? Not quite. /dev/sda2/ is not a directory; it's a device node. Since /dev/sda2 is mounted to / (the root filesystem), the correct equivalent to this command would be: ddrescue /dev/sdd /dev/sdc /ddrescue.log and although I wouldn't advise storing a log file in the root directory, the command should work. The log file itself can be placed in any writable location which has enough space. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On Fri, 8 May 2015 17:22:11 -0600 Bob Proulx wrote: > German wrote: > > Bob Proulx wrote: > > > I think I read that you have one identically sized drive, yes? I > > > am not sure where you are sitting with regards to the other > > > suggestions. But at the least I would make one good backup as > > > soon as possible. And it seems that possibly you have the > > > capability at this time? > > > > Yes, I do have two identical 2TB drives. So, you are advising to > > make a back up. Something like ddrescue if=/dev/sdX of=/dev/sdY ? > > Again I am not sure of the status of things with you since there have > been many good suggestions in this discussion thread. You may be > halfway down a different path. But yes if I were having hardware > problems I would make a backup as soon as possible. (Actually I > already have backups all of the time. Backups are important.) > > Always use a log file with ddrescue. If I have both of those disks > mounted on a second system with its own disks then put the logfile on > the host system. That would be on the host system and not either the > source or target. > > ddrescue if=/dev/sdX of=/dev/sdY /var/tmp/rescuelogfile Hmm.. The Wanderer suggest that *if= and of=* is the wrong syntax. He says that this should be simple as this: ddrescue /dev/sdX /dev/sdY /path/to/logfile Who is right? > > If you had booted a livecd and wanted that logfile to be persistent > then mount up a USB storage device and store it there. > > ddrescue if=/dev/sdX of=/dev/sdY /media/usb1 > > Where /media/usb1 is an example of a mounted usb storage device. > Replace that string with the mount point of the usb device mounted on > your host system. > > I now read that perhaps it wasn't hardware problems. If the disk is > okay then the first thing I would do is to fsck it. But if the disk > is having hardware problems then I would copy a backup first. > > Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508193727.1667b...@asterius.asterius.net
Re: Help with ddrescue
On Fri, 08 May 2015 19:20:37 -0400 The Wanderer wrote: > On 05/08/2015 at 07:08 PM, German wrote: > > > On Fri, 8 May 2015 23:54:46 +0100 Lisi Reisz > > wrote: > > > >> On Friday 08 May 2015 23:07:34 German wrote: > >> > >>> Can I try to run fsck on the failed drive? > >> > >> They are *your* files. But given that you have actually got a > >> suitable disk, i would at least dd them first onto that. > > > > That's what I got: > > > > spore@asterius:~$ lsblk > > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > > sda 8:00 119.2G 0 disk > > ├─sda1 8:10 512M 0 part /boot/efi > > ├─sda2 8:20 111.3G 0 part / > > └─sda3 8:30 7.4G 0 part [SWAP] > > sdb 8:16 0 465.8G 0 disk > > sdc 8:32 0 1.8T 0 disk /media/spore/9F86-0131 > > sdd 8:48 0 1.8T 0 disk > > └─sdd1 8:49 0 1.8T 0 part > > > > Where sdd is my failed drive. sdc is my spare drive. The correct > > procedure will be ddrescue if=/dev/sdd1 of=/dev/sdc ? > > No. That might potentially work (except that, if I'm reading the > ddrescue man page correctly, the syntax is wrong), but it wouldn't be > correct. > > First, unmount /dev/sdc. > > Then do one of two things: > > 1) Create /dev/sdc1 (as an unformatted partition, using fdisk or > parted or whatever partitioning tool you choose), and then run > > ddrescue /dev/sdd1 /dev/sdc1 /any/path/you/want/ddrescue.log > > 2) run > > ddrescue /dev/sdd /dev/sdc /any/path/you/want/ddrescue.log Ok, I think I am getting closer. How big is a log file? Can it be anywhere on all drives that have enough space? For instance: ddrescue /dev/sdd /dev/sdc /dev/sda2/ddrescue.log will work? > > (Don't do both, of course.) > > Note that I did NOT specify the 'if=' and 'of=' syntax. That is > correct syntax for dd, but the ddrescue man page does not mention it, > and I believe that it is incorrect syntax for ddrescue. > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508193351.0a4f9...@asterius.asterius.net
Re: Help with ddrescue
Bob Proulx wrote: > ddrescue if=/dev/sdX of=/dev/sdY /media/usb1 > > Where /media/usb1 is an example of a mounted usb storage device. > Replace that string with the mount point of the usb device mounted on > your host system. Obviously I made a mistake there. Not to the mount directory but to a file upon it. ddrescue if=/dev/sdX of=/dev/sdY /media/usb1/rescuelogfile Bob signature.asc Description: Digital signature
Re: Help with ddrescue
German wrote: > Bob Proulx wrote: > > I think I read that you have one identically sized drive, yes? I am > > not sure where you are sitting with regards to the other suggestions. > > But at the least I would make one good backup as soon as possible. > > And it seems that possibly you have the capability at this time? > > Yes, I do have two identical 2TB drives. So, you are advising to make a > back up. Something like ddrescue if=/dev/sdX of=/dev/sdY ? Again I am not sure of the status of things with you since there have been many good suggestions in this discussion thread. You may be halfway down a different path. But yes if I were having hardware problems I would make a backup as soon as possible. (Actually I already have backups all of the time. Backups are important.) Always use a log file with ddrescue. If I have both of those disks mounted on a second system with its own disks then put the logfile on the host system. That would be on the host system and not either the source or target. ddrescue if=/dev/sdX of=/dev/sdY /var/tmp/rescuelogfile If you had booted a livecd and wanted that logfile to be persistent then mount up a USB storage device and store it there. ddrescue if=/dev/sdX of=/dev/sdY /media/usb1 Where /media/usb1 is an example of a mounted usb storage device. Replace that string with the mount point of the usb device mounted on your host system. I now read that perhaps it wasn't hardware problems. If the disk is okay then the first thing I would do is to fsck it. But if the disk is having hardware problems then I would copy a backup first. Bob signature.asc Description: Digital signature
Re: Help with ddrescue
On 05/08/2015 at 07:08 PM, German wrote: > On Fri, 8 May 2015 23:54:46 +0100 Lisi Reisz > wrote: > >> On Friday 08 May 2015 23:07:34 German wrote: >> >>> Can I try to run fsck on the failed drive? >> >> They are *your* files. But given that you have actually got a >> suitable disk, i would at least dd them first onto that. > > That's what I got: > > spore@asterius:~$ lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:00 119.2G 0 disk > ├─sda1 8:10 512M 0 part /boot/efi > ├─sda2 8:20 111.3G 0 part / > └─sda3 8:30 7.4G 0 part [SWAP] > sdb 8:16 0 465.8G 0 disk > sdc 8:32 0 1.8T 0 disk /media/spore/9F86-0131 > sdd 8:48 0 1.8T 0 disk > └─sdd1 8:49 0 1.8T 0 part > > Where sdd is my failed drive. sdc is my spare drive. The correct > procedure will be ddrescue if=/dev/sdd1 of=/dev/sdc ? No. That might potentially work (except that, if I'm reading the ddrescue man page correctly, the syntax is wrong), but it wouldn't be correct. First, unmount /dev/sdc. Then do one of two things: 1) Create /dev/sdc1 (as an unformatted partition, using fdisk or parted or whatever partitioning tool you choose), and then run ddrescue /dev/sdd1 /dev/sdc1 /any/path/you/want/ddrescue.log 2) run ddrescue /dev/sdd /dev/sdc /any/path/you/want/ddrescue.log (Don't do both, of course.) Note that I did NOT specify the 'if=' and 'of=' syntax. That is correct syntax for dd, but the ddrescue man page does not mention it, and I believe that it is incorrect syntax for ddrescue. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On Fri, 8 May 2015 23:54:46 +0100 Lisi Reisz wrote: > On Friday 08 May 2015 23:07:34 German wrote: > > Can I try to run fsck on the failed drive? > > They are *your* files. But given that you have actually got a > suitable disk, i would at least dd them first onto that. > > Lisi > > That's what I got: spore@asterius:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 119.2G 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:20 111.3G 0 part / └─sda3 8:30 7.4G 0 part [SWAP] sdb 8:16 0 465.8G 0 disk sdc 8:32 0 1.8T 0 disk /media/spore/9F86-0131 sdd 8:48 0 1.8T 0 disk └─sdd1 8:49 0 1.8T 0 part Where sdd is my failed drive. sdc is my spare drive. The correct procedure will be ddrescue if=/dev/sdd1 of=/dev/sdc ? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508190847.76259...@asterius.asterius.net
Re: Help with ddrescue
On Friday 08 May 2015 23:07:34 German wrote: > Can I try to run fsck on the failed drive? They are *your* files. But given that you have actually got a suitable disk, i would at least dd them first onto that. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505082354.46323.lisi.re...@gmail.com
Re: Help with ddrescue
On Fri, 08 May 2015 18:11:03 -0400 The Wanderer wrote: > On 05/08/2015 at 06:07 PM, German wrote: > > > On Fri, 08 May 2015 16:00:05 -0400 Gary Dale > > wrote: > > > >> On 08/05/15 02:56 PM, German wrote: > > >>> What will this duplication accomplish? What advantages if I am > >>> duplicate? After I duplicate the drive, what are my next steps? > > > >> With the drive duplicated, run fsck on the new drive. > > > > Can I try to run fsck on the failed drive? > > You can (or, rather, on the filesystem which is on that drive), but if > the drive really is physically failing, you will probably just make > the problems worse - and reduce the likelihood of successfully > recovering data off of it later. > > If the drive _isn't_ physically failing, however, then running fsck on > the filesystem is probably the first thing you should do. If you're > sure the drive itself is OK and the problem is with the filesystem, > I'm kind of surprised you didn't do that before you even contacted > the list in the first place. > I am not sure about anything. I just gather some information on how to recover my files. As I said, with R-studio ( linux commercial data recovery app) I could see all files and directory on failed drive. Ok. Could you please tell me how to do fsck on NTFS drive? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508182025.213a9...@asterius.asterius.net
Re: Help with ddrescue
On 05/08/2015 at 06:07 PM, German wrote: > On Fri, 08 May 2015 16:00:05 -0400 Gary Dale > wrote: > >> On 08/05/15 02:56 PM, German wrote: >>> What will this duplication accomplish? What advantages if I am >>> duplicate? After I duplicate the drive, what are my next steps? > >> With the drive duplicated, run fsck on the new drive. > > Can I try to run fsck on the failed drive? You can (or, rather, on the filesystem which is on that drive), but if the drive really is physically failing, you will probably just make the problems worse - and reduce the likelihood of successfully recovering data off of it later. If the drive _isn't_ physically failing, however, then running fsck on the filesystem is probably the first thing you should do. If you're sure the drive itself is OK and the problem is with the filesystem, I'm kind of surprised you didn't do that before you even contacted the list in the first place. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On Fri, 08 May 2015 16:00:05 -0400 Gary Dale wrote: > On 08/05/15 02:56 PM, German wrote: > > On Fri, 08 May 2015 14:48:47 -0400 > > Gary Dale wrote: > > > >> On 08/05/15 02:32 PM, German wrote: > >>> On Fri, 08 May 2015 14:23:39 -0400 > >>> The Wanderer wrote: > >>> > On 05/08/2015 at 02:16 PM, German wrote: > > > On Fri, 08 May 2015 13:40:01 -0400 The Wanderer > > wrote: > > > >> On 05/08/2015 at 01:20 PM, German wrote: > >>> Thanks, but some clarification is needed. Now I have two > >>> drives, failed and a spare. Both are 2TB in size. Failed > >>> drive probably has 1.6 TB data I'd like to recover. It has > >>> only one partition I suppose. > >> That's bad. > >> > >> If the drive has only one partition, it probably has a single > >> filesystem taking up all of its space. > >> > >> When you create a ddrescue image from that partition, the new > >> image will take up _at least as much_ space as the original > >> filesystem. That's not the 1.6TB of "used" space; it's the full > >> 2TB of "total" space. (Plus however much space is taken up by > >> the "index" file used by ddrescue while doing its work.) > >> > >> That means that if your two 2TB drives are actually the same > >> size, the "good" one will not have enough space to store the > >> image you need to rescue from the "bad" one. > > Thanks Wanderer. So, I have no chances with two drives the same > > capacity? Would you advise to wait when I can get more capacity > > drive and only then to proceed as to save some head ache? > Yes, that's what I'd do in your situation. A 2.5TB drive should > be more than enough; that would also let you store the > sdb_failed.ddrescuelog file on the same drive, if you need to, so > you don't have to worry about finding space for it elsewhere. > > > Once again, thanks for such a complete instructions. > I wouldn't call the directions I gave "complete"; there's a lot > of details you'll still have to work out on your own, because > they will depend on the exact details of your failure and the > recovery process. Still, they should at least provide you a good > starting point. > > Again, I would recommend that you install (and read the > documentation for) myrescue, and consider using that instead of > ddrescue. I've used both (as well as dd_rescue), but if memory > serves I've had better results with myrescue. > > >>> Thanks so much. I wait when I can get a bigger drive. Have a > >>> greatest day! > >>> > >>> > >> I think Wanderer may be overstating the problem a little. If the > >> two drives are exactly the same size, you can use ddrescue to > >> duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb > >> of=/dev/sdc). However this will limit you to recovering in place on > >> new drive. > > What will this duplication accomplish? What advantages if I am > > duplicate? After I duplicate the drive, what are my next steps? > With the drive duplicated, run fsck on the new drive. Can I try to run fsck on the failed drive? Hopefully the > file system will be repairable. If it isn't, you can run testdisk or > whatever to try to rescue files to another device (not the original, > bad drive). > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508180734.04bea...@asterius.asterius.net
Re: Help with ddrescue
On Fri, 8 May 2015 22:05:40 +0100 Lisi Reisz wrote: > On Friday 08 May 2015 21:58:12 German wrote: > > It's happened when I was > > installing Lubuntu. > > Post hoc doesn't necessarily imply propter hoc. > > http://en.wikipedia.org/wiki/Post_hoc_ergo_propter_hoc > > Lisi > > You are philosopher. In meanwhile I think that that what caused the problem. I also have internal drive which couldn't be mounted after install of Lubuntu. Interesting enough, after installing Debian on the same system, my internal drive became fully operational. :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508171551.2aa30...@asterius.asterius.net
Re: Help with ddrescue
On Fri, 8 May 2015 15:00:13 -0600 Bob Proulx wrote: > German wrote: > > Bob Proulx wrote: > > > There is an idea that I didn't see proposed as I read through this > > > thread. If one had three same sized drives then there is another > > > possibility. > > > > Problem I have now is the lack of money. I simply don't have money > > now to buy yet another drive. I took out one drive from my another > > system, bought usb external enclosure and thought I'll succeed. > > Hmm.. everything is just not as easy as it seems. > > I think I read that you have one identically sized drive, yes? I am > not sure where you are sitting with regards to the other suggestions. > But at the least I would make one good backup as soon as possible. > And it seems that possibly you have the capability at this time? Yes, I do have two identical 2TB drives. So, you are advising to make a back up. Something like ddrescue if=/dev/sdX of=/dev/sdY ? > > On the backup it might be possible (not sure how advised it would be) > but possible to mount it read-only and then read files from it. The > copy would have had errors and therefore the file system would > probably be somewhat damaged. But mounted read-only I presume there > would be no more changes to it. Might be possible to copy the files > that could be recovered from the read-only media off elsewhere over > the network or to other places. That might get you a lot of what you > need within the limits that you have. > > Good luck! > > Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508171020.8...@asterius.asterius.net
Re: Help with ddrescue
On Friday 08 May 2015 21:58:12 German wrote: > It's happened when I was > installing Lubuntu. Post hoc doesn't necessarily imply propter hoc. http://en.wikipedia.org/wiki/Post_hoc_ergo_propter_hoc Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505082205.40946.lisi.re...@gmail.com
Re: Help with ddrescue
On Friday 08 May 2015 21:51:17 German wrote: > Problem I have now is the lack of money. I simply don't have money now > to buy yet another drive. Well, you can use what you have got and risk it. Or you can wait a bit. Assuming that the financial situation might ease. But I would think carefully before doing anything that just might, however unlikely it be, but just might, destroy or damage your music files, if they are precious to you. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505082202.38563.lisi.re...@gmail.com
Re: Help with ddrescue
German wrote: > Bob Proulx wrote: > > There is an idea that I didn't see proposed as I read through this > > thread. If one had three same sized drives then there is another > > possibility. > > Problem I have now is the lack of money. I simply don't have money now > to buy yet another drive. I took out one drive from my another system, > bought usb external enclosure and thought I'll succeed. Hmm.. > everything is just not as easy as it seems. I think I read that you have one identically sized drive, yes? I am not sure where you are sitting with regards to the other suggestions. But at the least I would make one good backup as soon as possible. And it seems that possibly you have the capability at this time? On the backup it might be possible (not sure how advised it would be) but possible to mount it read-only and then read files from it. The copy would have had errors and therefore the file system would probably be somewhat damaged. But mounted read-only I presume there would be no more changes to it. Might be possible to copy the files that could be recovered from the read-only media off elsewhere over the network or to other places. That might get you a lot of what you need within the limits that you have. Good luck! Bob signature.asc Description: Digital signature
Re: Help with ddrescue
On Fri, 08 May 2015 16:51:20 -0400 The Wanderer wrote: > On 05/08/2015 at 04:34 PM, German wrote: > > > On Fri, 08 May 2015 16:27:22 -0400 The Wanderer > > wrote: > > >> What leads you to conclude that the drive is OK and the filesystem > >> is what is bad? What errors are you seeing, in what situations? > > > > Error mounting /dev/sdc1 at /media/spore/FreeAgent GoFlex Drive: > > Command-line `mount -t "ntfs" -o > > "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" > > "/dev/sdc1" "/media/spore/FreeAgent GoFlex Drive"' exited with > > non-zero exit status 13: ntfs_attr_pread_i: ntfs_pread failed: > > Input/output error Failed to read of MFT, mft=17625 count=1 br=-1: > > Input/output error Inode is corrupt (5): Input/output error Index > > root attribute missing in directory inode 5: Input/output error > > Failed to mount '/dev/sdc1': Input/output error > > "Input/output error" in this sort of context usually means that the > drive itself is failing, not the filesystem. (Or that something else > in the connection between the system and the drive is faulty; I've > seen it happen with bad SATA/IDE cables, and for that matter with > cables which were just loose.) > > Just to confirm, this happens on any mount attempt, correct? Yes, this happens on mount attempt. I still don't think that drive is failing and I think cables are ok too. It's happened when I was installing Lubuntu. During the install, install program obviously probed all available drives, and did something nasty to the drive. > > > NTFS is either inconsistent, or there is a hardware fault, or it's a > > SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on > > Windows then reboot into Windows twice. The usage of the /f > > parameter is very important! If the device is a SoftRAID/FakeRAID > > then first activate it and mount a different device under > > the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). > > Please see the 'dmraid' documentation for more details. > > If you have a suitable Windows system with which to try the suggested > 'chkdsk /f' and double reboot-into-Windows approach, you could do > that, but I wouldn't bet on it helping - and if the drive really is > failing, then trying to access the drive that way might make things > worse. > > I think it looks as if the drive really is failing, and the "separate, > larger drive" ddrescue/dd_rescue/myrescue approach is the right way to > go after all. > > (Also note that since the filesystem is on /dev/sdc1, you'll almost > certainly want to apply your ddrescue command to source that node, not > the higher-level /dev/sdc node. You _can_ recover the data from a copy > of /dev/sdc, but it's significantly less trivial.) > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508165812.723cb...@asterius.asterius.net
Re: Help with ddrescue
On Friday 08 May 2015 21:40:02 German wrote: > Well, data is pretty much precious to me. Studios flacs of rare and > hard to get music. Then I would take at least one copy, preferably two, and work on a copy. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505082155.43457.lisi.re...@gmail.com
Re: Help with ddrescue
On 05/08/2015 at 04:34 PM, German wrote: > On Fri, 08 May 2015 16:27:22 -0400 The Wanderer > wrote: >> What leads you to conclude that the drive is OK and the filesystem >> is what is bad? What errors are you seeing, in what situations? > > Error mounting /dev/sdc1 at /media/spore/FreeAgent GoFlex Drive: Command-line > `mount -t "ntfs" -o > "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" > "/dev/sdc1" "/media/spore/FreeAgent GoFlex Drive"' exited with non-zero exit > status 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error > Failed to read of MFT, mft=17625 count=1 br=-1: Input/output error > Inode is corrupt (5): Input/output error > Index root attribute missing in directory inode 5: Input/output error > Failed to mount '/dev/sdc1': Input/output error "Input/output error" in this sort of context usually means that the drive itself is failing, not the filesystem. (Or that something else in the connection between the system and the drive is faulty; I've seen it happen with bad SATA/IDE cables, and for that matter with cables which were just loose.) Just to confirm, this happens on any mount attempt, correct? > NTFS is either inconsistent, or there is a hardware fault, or it's a > SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows > then reboot into Windows twice. The usage of the /f parameter is very > important! If the device is a SoftRAID/FakeRAID then first activate > it and mount a different device under the /dev/mapper/ directory, (e.g. > /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation > for more details. If you have a suitable Windows system with which to try the suggested 'chkdsk /f' and double reboot-into-Windows approach, you could do that, but I wouldn't bet on it helping - and if the drive really is failing, then trying to access the drive that way might make things worse. I think it looks as if the drive really is failing, and the "separate, larger drive" ddrescue/dd_rescue/myrescue approach is the right way to go after all. (Also note that since the filesystem is on /dev/sdc1, you'll almost certainly want to apply your ddrescue command to source that node, not the higher-level /dev/sdc node. You _can_ recover the data from a copy of /dev/sdc, but it's significantly less trivial.) -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On Fri, 8 May 2015 14:41:24 -0600 Bob Proulx wrote: > The Wanderer wrote: > > Gary Dale wrote: > > > I think Wanderer may be overstating the problem a little. If the > > > two drives are exactly the same size, you can use ddrescue to > > > duplicate the failed drive onto the new drive (ddrescue > > > if=/dev/sdb of=/dev/sdc). However this will limit you to > > > recovering in place on new drive. > > > > In my experience, single-pass recovery like this does not work very > > reliably or very well; it also doesn't let you make the "backup > > copy" you originally suggested, which is a good idea if you have > > the space (though I never have had). > > I have never had *enough* disk space. Because I always need more! > > There is an idea that I didn't see proposed as I read through this > thread. If one had three same sized drives then there is another > possibility. Problem I have now is the lack of money. I simply don't have money now to buy yet another drive. I took out one drive from my another system, bought usb external enclosure and thought I'll succeed. Hmm.. everything is just not as easy as it seems. It isn't that unusual to have three drives of the same > size. One could then make two copies of the data. Copy the data from > the failing drive to a good same-sized drive. It would then be an > identical copy. Then take the failing drive and put it on the shelf > so as not to damage it further while trying to recover. Then make > another identical copy onto the third drive. At that point one of the > copies can be used for recovery experimentation and there would still > be a copy available for backup on the other drive. > > Also when making the first backup copy using ddrescue use a third > location for the ddrescue log file. I am assuming that a system has > been booted up for the rescue and has the failing disk and the target > disk attached. That means the host system has its own space available > for the copy. Use it for the log file. > > ddrescue /dev/sdX /dev/sdY /var/tmp/rescuelogfile > > Where /dev/sdX is the failing source drive, /dev/sdY is the spare > target drive, and /var/tmp/rescuelogfile is on the system hosting the > recovery effort with its own drives. If I had a spare drive of the > same size this would be what I would do to copy it. > > Then could do the same for the backup onto the working copy spare for > recovery. Or just use a normal dd there since presumably both of the > spares are good and error free. > > > It's technically possible, yes, but I wouldn't want to trust or > > rely on it in any case where the source device is potentially prone > > to failure - and in any scenario where it isn't, you're unlikely to > > want to use one of the *rescue tools in the first place. > > My experience has been that once a drive starts to produce hard > failures that it tends to become worse rather quickly. I would > perform the backup of it. There is no way to avoid it. But I would > try to avoid working the failing drive as much as possible until there > is as much recovered as possible. After having recovered as much as > is possible only then would I try any other work on the failing drive. > Because Murphy's Law usually means that it becomes worse quickly. But > after I had a good backup then trying other things such as other disk > recovery software and so forth is reasonable. Why not if the drive > has already failed otherwise? But again I would want a good backup > first. And do any recovery work on a different working copy of it. > > > (There's also the consideration of finding space for the ddrescue > > log file if you're restoring directly to the identical-size device; > > that file that may not be as important in some scenarios, but I > > wouldn't want to try to do such a rescue without one.) > > Agreed. The ddrescue log is critical. But a hosting system with both > drives mounted could use /var/tmp/rescuelog for space not on either of > the same-sized drives. > > > I certainly wouldn't say there are never times when direct > > device-to-device recovery like that is appropriate, but I haven't > > encountered one and I would not recommend it as a base-practices > > procedure. > > Storage recovery is definitely a problem that takes skill to produce > good results. It's a problem. There is no easy solution because the > decisions we make along the way all depend upon the knowledge and the > information available at that moment. It is really hard to document a > canonical procedure. Sometimes it just helps to be lucky. > > Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508165117.1b7eb...@asterius.asterius.net
Re: Help with ddrescue
The Wanderer wrote: > Gary Dale wrote: > > I think Wanderer may be overstating the problem a little. If the two > > drives are exactly the same size, you can use ddrescue to duplicate > > the failed drive onto the new drive (ddrescue if=/dev/sdb > > of=/dev/sdc). However this will limit you to recovering in place on > > new drive. > > In my experience, single-pass recovery like this does not work very > reliably or very well; it also doesn't let you make the "backup copy" > you originally suggested, which is a good idea if you have the space > (though I never have had). I have never had *enough* disk space. Because I always need more! There is an idea that I didn't see proposed as I read through this thread. If one had three same sized drives then there is another possibility. It isn't that unusual to have three drives of the same size. One could then make two copies of the data. Copy the data from the failing drive to a good same-sized drive. It would then be an identical copy. Then take the failing drive and put it on the shelf so as not to damage it further while trying to recover. Then make another identical copy onto the third drive. At that point one of the copies can be used for recovery experimentation and there would still be a copy available for backup on the other drive. Also when making the first backup copy using ddrescue use a third location for the ddrescue log file. I am assuming that a system has been booted up for the rescue and has the failing disk and the target disk attached. That means the host system has its own space available for the copy. Use it for the log file. ddrescue /dev/sdX /dev/sdY /var/tmp/rescuelogfile Where /dev/sdX is the failing source drive, /dev/sdY is the spare target drive, and /var/tmp/rescuelogfile is on the system hosting the recovery effort with its own drives. If I had a spare drive of the same size this would be what I would do to copy it. Then could do the same for the backup onto the working copy spare for recovery. Or just use a normal dd there since presumably both of the spares are good and error free. > It's technically possible, yes, but I wouldn't want to trust or rely on > it in any case where the source device is potentially prone to failure - > and in any scenario where it isn't, you're unlikely to want to use one > of the *rescue tools in the first place. My experience has been that once a drive starts to produce hard failures that it tends to become worse rather quickly. I would perform the backup of it. There is no way to avoid it. But I would try to avoid working the failing drive as much as possible until there is as much recovered as possible. After having recovered as much as is possible only then would I try any other work on the failing drive. Because Murphy's Law usually means that it becomes worse quickly. But after I had a good backup then trying other things such as other disk recovery software and so forth is reasonable. Why not if the drive has already failed otherwise? But again I would want a good backup first. And do any recovery work on a different working copy of it. > (There's also the consideration of finding space for the ddrescue log > file if you're restoring directly to the identical-size device; that > file that may not be as important in some scenarios, but I wouldn't want > to try to do such a rescue without one.) Agreed. The ddrescue log is critical. But a hosting system with both drives mounted could use /var/tmp/rescuelog for space not on either of the same-sized drives. > I certainly wouldn't say there are never times when direct > device-to-device recovery like that is appropriate, but I haven't > encountered one and I would not recommend it as a base-practices > procedure. Storage recovery is definitely a problem that takes skill to produce good results. It's a problem. There is no easy solution because the decisions we make along the way all depend upon the knowledge and the information available at that moment. It is really hard to document a canonical procedure. Sometimes it just helps to be lucky. Bob signature.asc Description: Digital signature
Re: Help with ddrescue
On Fri, 8 May 2015 21:35:56 +0100 Lisi Reisz wrote: > On Friday 08 May 2015 21:09:42 German wrote: > > What will happen when I duplicate drive? Why is that failed drive is > > failed and duplicated drive might be repairable? If it's > > duplicated, it will be exactly the same, no? > > Yes, that is the point. If there is something wrong with the disk > then every time you read it you may be making it worse. Every time > you read it it may be the last time you can. And it has your precious > data on. So TAKE A COPY WHILE YOU CAN. If the data are really > precious take two copies. > > Then work on a copy. If you are working on it, you may destroy it or > anyhow damage it. If you are doing it to the one and only original > that would matter. Do it to a copy. Make all the attempts you want > on the copy. You still have the original if something goes wrong. > > > Confused. And bad drive is physically ok > > I think, it is just something wrong with file system. > > You could still lose or damage the files in the process of recovery. > Besides, how sure are you that it is not the drive? How precious are > the data? > > > MTF? > ? Mean time to failure?? > > Lisi > > Well, data is pretty much precious to me. Studios flacs of rare and hard to get music. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508164002.718c5...@asterius.asterius.net
Re: Help with ddrescue
On Friday 08 May 2015 21:09:42 German wrote: > What will happen when I duplicate drive? Why is that failed drive is > failed and duplicated drive might be repairable? If it's duplicated, it > will be exactly the same, no? Yes, that is the point. If there is something wrong with the disk then every time you read it you may be making it worse. Every time you read it it may be the last time you can. And it has your precious data on. So TAKE A COPY WHILE YOU CAN. If the data are really precious take two copies. Then work on a copy. If you are working on it, you may destroy it or anyhow damage it. If you are doing it to the one and only original that would matter. Do it to a copy. Make all the attempts you want on the copy. You still have the original if something goes wrong. > Confused. And bad drive is physically ok > I think, it is just something wrong with file system. You could still lose or damage the files in the process of recovery. Besides, how sure are you that it is not the drive? How precious are the data? > MTF? ? Mean time to failure?? Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505082135.56101.lisi.re...@gmail.com
Re: Help with ddrescue
On Fri, 08 May 2015 16:27:22 -0400 The Wanderer wrote: > On 05/08/2015 at 04:09 PM, German wrote: > > > On Fri, 08 May 2015 16:00:05 -0400 Gary Dale > > wrote: > > > >> On 08/05/15 02:56 PM, German wrote: > > >>> What will this duplication accomplish? What advantages if I am > >>> duplicate? After I duplicate the drive, what are my next steps? > >> > >> With the drive duplicated, run fsck on the new drive. Hopefully > >> the file system will be repairable. If it isn't, you can run > >> testdisk or whatever to try to rescue files to another device (not > >> the original, bad drive). > > > > What will happen when I duplicate drive? Why is that failed drive is > > failed and duplicated drive might be repairable? If it's duplicated, > > it will be exactly the same, no? Confused. And bad drive is > > physically ok I think, it is just something wrong with file system. > > MTF? > > If the bad drive is physically OK, then ddrescue is probably not > needed. > > ddrescue, and the similar *rescue tools, are only for recovering as > much data as possible data when you can't use plain dd because the > drive itself is producing errors in some sectors. (You still can't > recover data from those sectors, but you can generally get the rest.) > > If the drive is OK but the filesystem is bad, then you need to use > other tools for data recovery. Exactly what those tools would be will > probably depend on what filesystem is involved; if fsck doesn't work, > then it will probably involve advanced manual techniques which we > (or, at least, I) could not talk you through via E-mail. > > If you want to copy the "bad" filesystem for analysis and/or > dissecting, then as long as the drive is OK, you should be able to do > it using plain dd - no need for ddrescue or any such thing. > > > What leads you to conclude that the drive is OK and the filesystem is > what is bad? What errors are you seeing, in what situations? > Error mounting /dev/sdc1 at /media/spore/FreeAgent GoFlex Drive: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sdc1" "/media/spore/FreeAgent GoFlex Drive"' exited with non-zero exit status 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Failed to read of MFT, mft=17625 count=1 br=-1: Input/output error Inode is corrupt (5): Input/output error Index root attribute missing in directory inode 5: Input/output error Failed to mount '/dev/sdc1': Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508163434.45a77...@asterius.asterius.net
Re: Help with ddrescue
On 05/08/2015 at 04:09 PM, German wrote: > On Fri, 08 May 2015 16:00:05 -0400 Gary Dale > wrote: > >> On 08/05/15 02:56 PM, German wrote: >>> What will this duplication accomplish? What advantages if I am >>> duplicate? After I duplicate the drive, what are my next steps? >> >> With the drive duplicated, run fsck on the new drive. Hopefully >> the file system will be repairable. If it isn't, you can run >> testdisk or whatever to try to rescue files to another device (not >> the original, bad drive). > > What will happen when I duplicate drive? Why is that failed drive is > failed and duplicated drive might be repairable? If it's duplicated, > it will be exactly the same, no? Confused. And bad drive is > physically ok I think, it is just something wrong with file system. > MTF? If the bad drive is physically OK, then ddrescue is probably not needed. ddrescue, and the similar *rescue tools, are only for recovering as much data as possible data when you can't use plain dd because the drive itself is producing errors in some sectors. (You still can't recover data from those sectors, but you can generally get the rest.) If the drive is OK but the filesystem is bad, then you need to use other tools for data recovery. Exactly what those tools would be will probably depend on what filesystem is involved; if fsck doesn't work, then it will probably involve advanced manual techniques which we (or, at least, I) could not talk you through via E-mail. If you want to copy the "bad" filesystem for analysis and/or dissecting, then as long as the drive is OK, you should be able to do it using plain dd - no need for ddrescue or any such thing. What leads you to conclude that the drive is OK and the filesystem is what is bad? What errors are you seeing, in what situations? -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On Fri, 08 May 2015 16:00:05 -0400 Gary Dale wrote: > On 08/05/15 02:56 PM, German wrote: > > On Fri, 08 May 2015 14:48:47 -0400 > > Gary Dale wrote: > > > >> On 08/05/15 02:32 PM, German wrote: > >>> On Fri, 08 May 2015 14:23:39 -0400 > >>> The Wanderer wrote: > >>> > On 05/08/2015 at 02:16 PM, German wrote: > > > On Fri, 08 May 2015 13:40:01 -0400 The Wanderer > > wrote: > > > >> On 05/08/2015 at 01:20 PM, German wrote: > >>> Thanks, but some clarification is needed. Now I have two > >>> drives, failed and a spare. Both are 2TB in size. Failed > >>> drive probably has 1.6 TB data I'd like to recover. It has > >>> only one partition I suppose. > >> That's bad. > >> > >> If the drive has only one partition, it probably has a single > >> filesystem taking up all of its space. > >> > >> When you create a ddrescue image from that partition, the new > >> image will take up _at least as much_ space as the original > >> filesystem. That's not the 1.6TB of "used" space; it's the full > >> 2TB of "total" space. (Plus however much space is taken up by > >> the "index" file used by ddrescue while doing its work.) > >> > >> That means that if your two 2TB drives are actually the same > >> size, the "good" one will not have enough space to store the > >> image you need to rescue from the "bad" one. > > Thanks Wanderer. So, I have no chances with two drives the same > > capacity? Would you advise to wait when I can get more capacity > > drive and only then to proceed as to save some head ache? > Yes, that's what I'd do in your situation. A 2.5TB drive should > be more than enough; that would also let you store the > sdb_failed.ddrescuelog file on the same drive, if you need to, so > you don't have to worry about finding space for it elsewhere. > > > Once again, thanks for such a complete instructions. > I wouldn't call the directions I gave "complete"; there's a lot > of details you'll still have to work out on your own, because > they will depend on the exact details of your failure and the > recovery process. Still, they should at least provide you a good > starting point. > > Again, I would recommend that you install (and read the > documentation for) myrescue, and consider using that instead of > ddrescue. I've used both (as well as dd_rescue), but if memory > serves I've had better results with myrescue. > > >>> Thanks so much. I wait when I can get a bigger drive. Have a > >>> greatest day! > >>> > >>> > >> I think Wanderer may be overstating the problem a little. If the > >> two drives are exactly the same size, you can use ddrescue to > >> duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb > >> of=/dev/sdc). However this will limit you to recovering in place on > >> new drive. > > What will this duplication accomplish? What advantages if I am > > duplicate? After I duplicate the drive, what are my next steps? > With the drive duplicated, run fsck on the new drive. Hopefully the > file system will be repairable. If it isn't, you can run testdisk or > whatever to try to rescue files to another device (not the original, > bad drive). > > What will happen when I duplicate drive? Why is that failed drive is failed and duplicated drive might be repairable? If it's duplicated, it will be exactly the same, no? Confused. And bad drive is physically ok I think, it is just something wrong with file system. MTF? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508160942.50070...@asterius.asterius.net
Re: Help with ddrescue
On 08/05/15 02:56 PM, German wrote: On Fri, 08 May 2015 14:48:47 -0400 Gary Dale wrote: On 08/05/15 02:32 PM, German wrote: On Fri, 08 May 2015 14:23:39 -0400 The Wanderer wrote: On 05/08/2015 at 02:16 PM, German wrote: On Fri, 08 May 2015 13:40:01 -0400 The Wanderer wrote: On 05/08/2015 at 01:20 PM, German wrote: Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of "used" space; it's the full 2TB of "total" space. (Plus however much space is taken up by the "index" file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the "good" one will not have enough space to store the image you need to rescue from the "bad" one. Thanks Wanderer. So, I have no chances with two drives the same capacity? Would you advise to wait when I can get more capacity drive and only then to proceed as to save some head ache? Yes, that's what I'd do in your situation. A 2.5TB drive should be more than enough; that would also let you store the sdb_failed.ddrescuelog file on the same drive, if you need to, so you don't have to worry about finding space for it elsewhere. Once again, thanks for such a complete instructions. I wouldn't call the directions I gave "complete"; there's a lot of details you'll still have to work out on your own, because they will depend on the exact details of your failure and the recovery process. Still, they should at least provide you a good starting point. Again, I would recommend that you install (and read the documentation for) myrescue, and consider using that instead of ddrescue. I've used both (as well as dd_rescue), but if memory serves I've had better results with myrescue. Thanks so much. I wait when I can get a bigger drive. Have a greatest day! I think Wanderer may be overstating the problem a little. If the two drives are exactly the same size, you can use ddrescue to duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb of=/dev/sdc). However this will limit you to recovering in place on new drive. What will this duplication accomplish? What advantages if I am duplicate? After I duplicate the drive, what are my next steps? With the drive duplicated, run fsck on the new drive. Hopefully the file system will be repairable. If it isn't, you can run testdisk or whatever to try to rescue files to another device (not the original, bad drive). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d15c5.3000...@torfree.net
Re: Help with ddrescue
On 05/08/2015 at 02:48 PM, Gary Dale wrote: > On 08/05/15 02:32 PM, German wrote: > >> On Fri, 08 May 2015 14:23:39 -0400 The Wanderer >> wrote: >>> Yes, that's what I'd do in your situation. A 2.5TB drive should >>> be more than enough; that would also let you store the >>> sdb_failed.ddrescuelog file on the same drive, if you need to, so >>> you don't have to worry about finding space for it elsewhere. >> Thanks so much. I wait when I can get a bigger drive. Have a >> greatest day! > > I think Wanderer may be overstating the problem a little. If the two > drives are exactly the same size, you can use ddrescue to duplicate > the failed drive onto the new drive (ddrescue if=/dev/sdb > of=/dev/sdc). However this will limit you to recovering in place on > new drive. In my experience, single-pass recovery like this does not work very reliably or very well; it also doesn't let you make the "backup copy" you originally suggested, which is a good idea if you have the space (though I never have had). It's technically possible, yes, but I wouldn't want to trust or rely on it in any case where the source device is potentially prone to failure - and in any scenario where it isn't, you're unlikely to want to use one of the *rescue tools in the first place. (There's also the consideration of finding space for the ddrescue log file if you're restoring directly to the identical-size device; that file that may not be as important in some scenarios, but I wouldn't want to try to do such a rescue without one.) > Hopefully the file system is repairable which will make this > possible. If the file system isn't, you need a third drive to hold > recovered files. That's another point, yes; if the filesystem isn't directly repairable, you may have to use forensic tools to dig in and recover data, and at that point it's just easier to work with a separate file IMO. I certainly wouldn't say there are never times when direct device-to-device recovery like that is appropriate, but I haven't encountered one and I would not recommend it as a base-practices procedure. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On Fri, 08 May 2015 14:48:47 -0400 Gary Dale wrote: > On 08/05/15 02:32 PM, German wrote: > > On Fri, 08 May 2015 14:23:39 -0400 > > The Wanderer wrote: > > > >> On 05/08/2015 at 02:16 PM, German wrote: > >> > >>> On Fri, 08 May 2015 13:40:01 -0400 The Wanderer > >>> wrote: > >>> > On 05/08/2015 at 01:20 PM, German wrote: > > Thanks, but some clarification is needed. Now I have two drives, > > failed and a spare. Both are 2TB in size. Failed drive probably > > has 1.6 TB data I'd like to recover. It has only one partition I > > suppose. > That's bad. > > If the drive has only one partition, it probably has a single > filesystem taking up all of its space. > > When you create a ddrescue image from that partition, the new > image will take up _at least as much_ space as the original > filesystem. That's not the 1.6TB of "used" space; it's the full > 2TB of "total" space. (Plus however much space is taken up by > the "index" file used by ddrescue while doing its work.) > > That means that if your two 2TB drives are actually the same > size, the "good" one will not have enough space to store the > image you need to rescue from the "bad" one. > >>> Thanks Wanderer. So, I have no chances with two drives the same > >>> capacity? Would you advise to wait when I can get more capacity > >>> drive and only then to proceed as to save some head ache? > >> Yes, that's what I'd do in your situation. A 2.5TB drive should be > >> more than enough; that would also let you store the > >> sdb_failed.ddrescuelog file on the same drive, if you need to, so > >> you don't have to worry about finding space for it elsewhere. > >> > >>> Once again, thanks for such a complete instructions. > >> I wouldn't call the directions I gave "complete"; there's a lot of > >> details you'll still have to work out on your own, because they > >> will depend on the exact details of your failure and the recovery > >> process. Still, they should at least provide you a good starting > >> point. > >> > >> Again, I would recommend that you install (and read the > >> documentation for) myrescue, and consider using that instead of > >> ddrescue. I've used both (as well as dd_rescue), but if memory > >> serves I've had better results with myrescue. > >> > > Thanks so much. I wait when I can get a bigger drive. Have a > > greatest day! > > > > > I think Wanderer may be overstating the problem a little. If the two > drives are exactly the same size, you can use ddrescue to duplicate > the failed drive onto the new drive (ddrescue if=/dev/sdb > of=/dev/sdc). However this will limit you to recovering in place on > new drive. What will this duplication accomplish? What advantages if I am duplicate? After I duplicate the drive, what are my next steps? > > Hopefully the file system is repairable which will make this > possible. If the file system isn't, you need a third drive to hold > recovered files. > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508145623.35846...@asterius.asterius.net
Re: Help with ddrescue
On 08/05/15 02:32 PM, German wrote: On Fri, 08 May 2015 14:23:39 -0400 The Wanderer wrote: On 05/08/2015 at 02:16 PM, German wrote: On Fri, 08 May 2015 13:40:01 -0400 The Wanderer wrote: On 05/08/2015 at 01:20 PM, German wrote: Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of "used" space; it's the full 2TB of "total" space. (Plus however much space is taken up by the "index" file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the "good" one will not have enough space to store the image you need to rescue from the "bad" one. Thanks Wanderer. So, I have no chances with two drives the same capacity? Would you advise to wait when I can get more capacity drive and only then to proceed as to save some head ache? Yes, that's what I'd do in your situation. A 2.5TB drive should be more than enough; that would also let you store the sdb_failed.ddrescuelog file on the same drive, if you need to, so you don't have to worry about finding space for it elsewhere. Once again, thanks for such a complete instructions. I wouldn't call the directions I gave "complete"; there's a lot of details you'll still have to work out on your own, because they will depend on the exact details of your failure and the recovery process. Still, they should at least provide you a good starting point. Again, I would recommend that you install (and read the documentation for) myrescue, and consider using that instead of ddrescue. I've used both (as well as dd_rescue), but if memory serves I've had better results with myrescue. Thanks so much. I wait when I can get a bigger drive. Have a greatest day! I think Wanderer may be overstating the problem a little. If the two drives are exactly the same size, you can use ddrescue to duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb of=/dev/sdc). However this will limit you to recovering in place on new drive. Hopefully the file system is repairable which will make this possible. If the file system isn't, you need a third drive to hold recovered files. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d050f.9050...@torfree.net
Re: Help with ddrescue
On Fri, 08 May 2015 14:23:39 -0400 The Wanderer wrote: > On 05/08/2015 at 02:16 PM, German wrote: > > > On Fri, 08 May 2015 13:40:01 -0400 The Wanderer > > wrote: > > > >> On 05/08/2015 at 01:20 PM, German wrote: > > >>> Thanks, but some clarification is needed. Now I have two drives, > >>> failed and a spare. Both are 2TB in size. Failed drive probably > >>> has 1.6 TB data I'd like to recover. It has only one partition I > >>> suppose. > >> > >> That's bad. > >> > >> If the drive has only one partition, it probably has a single > >> filesystem taking up all of its space. > >> > >> When you create a ddrescue image from that partition, the new image > >> will take up _at least as much_ space as the original filesystem. > >> That's not the 1.6TB of "used" space; it's the full 2TB of "total" > >> space. (Plus however much space is taken up by the "index" file > >> used by ddrescue while doing its work.) > >> > >> That means that if your two 2TB drives are actually the same size, > >> the "good" one will not have enough space to store the image you > >> need to rescue from the "bad" one. > > > > Thanks Wanderer. So, I have no chances with two drives the same > > capacity? Would you advise to wait when I can get more capacity > > drive and only then to proceed as to save some head ache? > > Yes, that's what I'd do in your situation. A 2.5TB drive should be > more than enough; that would also let you store the > sdb_failed.ddrescuelog file on the same drive, if you need to, so you > don't have to worry about finding space for it elsewhere. > > > Once again, thanks for such a complete instructions. > > I wouldn't call the directions I gave "complete"; there's a lot of > details you'll still have to work out on your own, because they will > depend on the exact details of your failure and the recovery process. > Still, they should at least provide you a good starting point. > > Again, I would recommend that you install (and read the documentation > for) myrescue, and consider using that instead of ddrescue. I've used > both (as well as dd_rescue), but if memory serves I've had better > results with myrescue. > Thanks so much. I wait when I can get a bigger drive. Have a greatest day! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508143219.07338...@asterius.asterius.net
Re: Help with ddrescue
No. With ddrescue, you do not (want to) create a new filesystem directly on the new device. What you want to do is create a filesystem _image_, in a file which is stored on the new device. Step-by-step, what you do is: * Create a filesystem on your "good" drive (/dev/sdc). You can use any filesystem you want. * Mount the newly created filesystem somewhere. For example, if you want to mount it to the empty directory '/mnt/new_disk', you could run the command: mount /dev/sdc1 /mnt/new_disk * Run the command ddrescue /dev/sdb /mnt/new_disk/sdb_failed.img /tmp/sdb_failed.ddrescuelog Note that this will create _two_ files: the rescued filesystem image, and a "log file" which ddrescue uses to keep track of what it has already successfully rescued and where it has encountered errors. This second file will take up additional space. As someone just reading this list for my own info, I found the above explanation quite helpful. It is a combination of a detailed example and a tutorial. It provides clarity instead of what often might just be considered "helpful(???)" hints as to what is required. Thank you!! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d0110.1030...@aim.com
Re: Help with ddrescue
On 05/08/2015 at 02:16 PM, German wrote: > On Fri, 08 May 2015 13:40:01 -0400 The Wanderer > wrote: > >> On 05/08/2015 at 01:20 PM, German wrote: >>> Thanks, but some clarification is needed. Now I have two drives, >>> failed and a spare. Both are 2TB in size. Failed drive probably >>> has 1.6 TB data I'd like to recover. It has only one partition I >>> suppose. >> >> That's bad. >> >> If the drive has only one partition, it probably has a single >> filesystem taking up all of its space. >> >> When you create a ddrescue image from that partition, the new image >> will take up _at least as much_ space as the original filesystem. >> That's not the 1.6TB of "used" space; it's the full 2TB of "total" >> space. (Plus however much space is taken up by the "index" file >> used by ddrescue while doing its work.) >> >> That means that if your two 2TB drives are actually the same size, >> the "good" one will not have enough space to store the image you >> need to rescue from the "bad" one. > > Thanks Wanderer. So, I have no chances with two drives the same > capacity? Would you advise to wait when I can get more capacity drive > and only then to proceed as to save some head ache? Yes, that's what I'd do in your situation. A 2.5TB drive should be more than enough; that would also let you store the sdb_failed.ddrescuelog file on the same drive, if you need to, so you don't have to worry about finding space for it elsewhere. > Once again, thanks for such a complete instructions. I wouldn't call the directions I gave "complete"; there's a lot of details you'll still have to work out on your own, because they will depend on the exact details of your failure and the recovery process. Still, they should at least provide you a good starting point. Again, I would recommend that you install (and read the documentation for) myrescue, and consider using that instead of ddrescue. I've used both (as well as dd_rescue), but if memory serves I've had better results with myrescue. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On Fri, 08 May 2015 13:40:01 -0400 The Wanderer wrote: > On 05/08/2015 at 01:20 PM, German wrote: > > > On Fri, 08 May 2015 12:10:38 -0400 Gary Dale > > wrote: > > > >> On 08/05/15 10:32 AM, German wrote: > >>> Hi list. Ok, now I have a spare 2TB USB drive where I can save > >>> .img file. Is that the right procedure? Do I have make a snapshot > >>> of failed drive and transfer it as a .img file to a spare drive, > >>> correct? R-studio for linux can display files of failed drive ( > >>> TestDisk coudn't do it ). So now I think I'll proceed. What is > >>> exact command to do it with ddrescue and what file system the > >>> spare drive has to be formated? Thank you very much! > >>> > >>> > >> You can try ddrescue if=/dev/sdb1 of=failed.img where /dev/sdb1 > >> would be the partition that you want to recover. > > > > Thanks, but some clarification is needed. Now I have two drives, > > failed and a spare. Both are 2TB in size. Failed drive probably has > > 1.6 TB data I'd like to recover. It has only one partition I > > suppose. > > That's bad. > > If the drive has only one partition, it probably has a single > filesystem taking up all of its space. > > When you create a ddrescue image from that partition, the new image > will take up _at least as much_ space as the original filesystem. > That's not the 1.6TB of "used" space; it's the full 2TB of "total" > space. (Plus however much space is taken up by the "index" file used > by ddrescue while doing its work.) > > That means that if your two 2TB drives are actually the same size, the > "good" one will not have enough space to store the image you need to > rescue from the "bad" one. Thanks Wanderer. So, I have no chances with two drives the same capacity? Would you advise to wait when I can get more capacity drive and only then to proceed as to save some head ache? Once again, thanks for such a complete instructions. > > > So, if failed drive is for instance /dev/sdb and spare drive is for > > isntance /dev/sdc, the right command will be ddrescue if=/dev/sdb > > of=/dev/sdc/failed.img ? > > No. > > With ddrescue, you do not (want to) create a new filesystem directly > on the new device. > > What you want to do is create a filesystem _image_, in a file which is > stored on the new device. > > Step-by-step, what you do is: > > * Create a filesystem on your "good" drive (/dev/sdc). You can use any > filesystem you want. > > * Mount the newly created filesystem somewhere. For example, if you > want to mount it to the empty directory '/mnt/new_disk', you could > run the command: > mount /dev/sdc1 /mnt/new_disk > > * Run the command > ddrescue /dev/sdb /mnt/new_disk/sdb_failed.img > /tmp/sdb_failed.ddrescuelog > Note that this will create _two_ files: the rescued filesystem image, > and a "log file" which ddrescue uses to keep track of what it has > already successfully rescued and where it has encountered errors. This > second file will take up additional space. > > * If you have enough free space, copy the resulting sdb_failed.img to > a separate location, so you have a backup copy if something goes > wrong. > > * Run recovery tools (starting with fsck, as Gary Dale suggested) on > sdb_failed.img, and see how much you can recover. > > * Mount sdb_failed.img, using a loopback mount, and copy out whatever > files you can to a new location. > > > Recovering data from a failed drive using ddrescue, dd_rescue, or > myrescue is entirely possible; I've done it myself. However, it is not > trivial, and in my experience the process requires considerably more > space than the size of whatever drive is being rescued. > > > > Personally, I would probably recommend the use of myrescue rather than > of ddrescue or dd_rescue, but any of them can work if you use them > right. > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508141619.37003...@asterius.asterius.net
Re: Help with ddrescue
On 05/08/2015 at 01:20 PM, German wrote: > On Fri, 08 May 2015 12:10:38 -0400 Gary Dale > wrote: > >> On 08/05/15 10:32 AM, German wrote: >>> Hi list. Ok, now I have a spare 2TB USB drive where I can save >>> .img file. Is that the right procedure? Do I have make a snapshot >>> of failed drive and transfer it as a .img file to a spare drive, >>> correct? R-studio for linux can display files of failed drive ( >>> TestDisk coudn't do it ). So now I think I'll proceed. What is >>> exact command to do it with ddrescue and what file system the >>> spare drive has to be formated? Thank you very much! >>> >>> >> You can try ddrescue if=/dev/sdb1 of=failed.img where /dev/sdb1 >> would be the partition that you want to recover. > > Thanks, but some clarification is needed. Now I have two drives, > failed and a spare. Both are 2TB in size. Failed drive probably has > 1.6 TB data I'd like to recover. It has only one partition I > suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of "used" space; it's the full 2TB of "total" space. (Plus however much space is taken up by the "index" file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the "good" one will not have enough space to store the image you need to rescue from the "bad" one. > So, if failed drive is for instance /dev/sdb and spare drive is for > isntance /dev/sdc, the right command will be ddrescue if=/dev/sdb > of=/dev/sdc/failed.img ? No. With ddrescue, you do not (want to) create a new filesystem directly on the new device. What you want to do is create a filesystem _image_, in a file which is stored on the new device. Step-by-step, what you do is: * Create a filesystem on your "good" drive (/dev/sdc). You can use any filesystem you want. * Mount the newly created filesystem somewhere. For example, if you want to mount it to the empty directory '/mnt/new_disk', you could run the command: mount /dev/sdc1 /mnt/new_disk * Run the command ddrescue /dev/sdb /mnt/new_disk/sdb_failed.img /tmp/sdb_failed.ddrescuelog Note that this will create _two_ files: the rescued filesystem image, and a "log file" which ddrescue uses to keep track of what it has already successfully rescued and where it has encountered errors. This second file will take up additional space. * If you have enough free space, copy the resulting sdb_failed.img to a separate location, so you have a backup copy if something goes wrong. * Run recovery tools (starting with fsck, as Gary Dale suggested) on sdb_failed.img, and see how much you can recover. * Mount sdb_failed.img, using a loopback mount, and copy out whatever files you can to a new location. Recovering data from a failed drive using ddrescue, dd_rescue, or myrescue is entirely possible; I've done it myself. However, it is not trivial, and in my experience the process requires considerably more space than the size of whatever drive is being rescued. Personally, I would probably recommend the use of myrescue rather than of ddrescue or dd_rescue, but any of them can work if you use them right. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On Fri, 08 May 2015 12:10:38 -0400 Gary Dale wrote: > On 08/05/15 10:32 AM, German wrote: > > Hi list. Ok, now I have a spare 2TB USB drive where I can save .img > > file. Is that the right procedure? Do I have make a snapshot of > > failed drive and transfer it as a .img file to a spare drive, > > correct? R-studio for linux can display files of failed drive > > ( TestDisk coudn't do it ). So now I think I'll proceed. What is > > exact command to do it with ddrescue and what file system the spare > > drive has to be formated? Thank you very much! > > > > > You can try ddrescue if=/dev/sdb1 of=failed.img where /dev/sdb1 would > be the partition that you want to recover. > Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. So, if failed drive is for instance /dev/sdb and spare drive is for isntance /dev/sdc, the right command will be ddrescue if=/dev/sdb of=/dev/sdc/failed.img ? And also, you didn't answer this, what file system the a spare drive ahs to be formated? Thanks. > If you have space, make a copy of failed.img as well (cp failed.img > failed2.img) so you don't have to go back to the actual failed drive, > which is likely getting worse each time you access it. > > Next you can run whatever rescue software you like on the failed.img > file to see if you can recover anything. I usually start off with > something simple like fsck before trying testdisk. > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508132034.58b6d...@asterius.asterius.net
Re: Help with ddrescue
On 08/05/15 10:32 AM, German wrote: Hi list. Ok, now I have a spare 2TB USB drive where I can save .img file. Is that the right procedure? Do I have make a snapshot of failed drive and transfer it as a .img file to a spare drive, correct? R-studio for linux can display files of failed drive ( TestDisk coudn't do it ). So now I think I'll proceed. What is exact command to do it with ddrescue and what file system the spare drive has to be formated? Thank you very much! You can try ddrescue if=/dev/sdb1 of=failed.img where /dev/sdb1 would be the partition that you want to recover. If you have space, make a copy of failed.img as well (cp failed.img failed2.img) so you don't have to go back to the actual failed drive, which is likely getting worse each time you access it. Next you can run whatever rescue software you like on the failed.img file to see if you can recover anything. I usually start off with something simple like fsck before trying testdisk. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554cdffe.3090...@torfree.net
Help with ddrescue
Hi list. Ok, now I have a spare 2TB USB drive where I can save .img file. Is that the right procedure? Do I have make a snapshot of failed drive and transfer it as a .img file to a spare drive, correct? R-studio for linux can display files of failed drive ( TestDisk coudn't do it ). So now I think I'll proceed. What is exact command to do it with ddrescue and what file system the spare drive has to be formated? Thank you very much! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508103253.78ce0...@asterius.asterius.net
