Best method/tool for cloning a failing HDD for Data Recovery?

jumanji said:

Hi theTechLord,

Welcome to this thread.

Can you please elaborate on how to use the Free version of ISOBuster to clone a failing Hard Disk?

Take the case of nkaufman here.. He has a failing System Disk on his laptop.

What should he do with ISObuster to clone this drive to the new drive? Will the free version do it?

A step by step procedure starting from the installation of ISObuster culminating in the successful cloning to a new drive will help the users. And that is our intention of discussing it here.. ( I am not the affected party. :))

IsoBuster has many paid features, but the most important feature, making managed Images is completely free.
But i really fell in love with IsoBuster, so i did buy the pro version.

That's why Managed Images are the most complete backup possibility of a drive:

• Every Section is included in the Backup
• You can recover lost/deleted files/directories from the Image
• Will back up every byte and the fragmentation-order, exactly the way it's present on the data storage device itself.
• Will include the optical layer of a disc
• You can pause/abort/resume/complete such an image, whenever you want.
• Every type of data-storage, where the computer has direct access to the file system, is supported by IsoBuster.
• If a section is not readable very good, IsoBuster will not give up that easily. Skipped sections can be completed at any time.
• If the computer can't read a file completely, Windows Explorer does ask you to retry. If you abort, the file will not be backed up at all. IsoBuster's IBQ/IBP-Images back up everything, which is readable.
• Full File Attributes are included into the managed image, including the last access/last-changed/creation-date
• Position/Extents of files/folders on the file system is also included
• It's like a 1:1-Copy of a HDD. :)
• Partition type(Logical/Primary)/name/file system type/label is also included.
• The developer of IsoBuster is very nice and offers best service.

Just try it once, it is truly worthed it.
I hope, this helped. Good luck

jumanji said:

Does not help anybody in anyway..:)

Give step by step procedure not features.

Take the case nkaufman's case. Exactly what he should do to clone his failing system drive using ISOBuster.? Will the bad sectors be recovered? To start with do you want him to install ISObuster on his failing drive?

Do you want me to spell out the step by step procedure of using ddrescue?

That only will help the user.

Don't chirp. Be practical. I have ISOBuster for ages and the current pro version 3.6 too and licenced.. Nothing new to me.

I haven't seen even a single user who has cloned his failing hard drive using ISObuster, free or paid. (We don't need a 1:1 Copy with the same unreadable sectors.) If you have done it spell the step by step procedure.

If you don't know please ask the developer, Peter whether a failing system drive as in nkaufman's case can be cloned and substituted successfully recovering the data in bad sectors and let us know.

Well, that's not exactly cloning, what IsoBuster does, but it's the best thing you can do, if your Hard Drive starts to get trouble or dead sections etc.
Those IBQ/iBP-Images will rescue everything, which is still able to be rescued.

jumanji -

Looking at the examples from - GNU ddrescue Manual

Example 1: Rescue a whole disc with two ext2 partitions in /dev/hda to /dev/hdb.
Note: you do not need to partition /dev/hdb beforehand, but if the partition table on /dev/hda is damaged, you'll need to recreate it somehow on /dev/hdb.
ddrescue -f -n /dev/hda /dev/hdb mapfile
ddrescue -d -f -r3 /dev/hda /dev/hdb mapfile
fdisk /dev/hdb
e2fsck -v -f /dev/hdb1
e2fsck -v -f /dev/hdb2

it seems that we need to specify mapfile or logfile, not recovery.log.

dragonballz4 in the thread you mentioned earlier, indicated that there is a difference between log and logfile and that led me to do some research and I landed on the above website.

Any thoughts?

But this site - Ddrescue - ForensicsWiki has something else
These two examples are taken directly from the ddrescue info pages.
Example 1: Rescue an ext2 partition in /dev/hda2 to /dev/hdb2
Please Note: This will overwrite ALL data on the partition you are copying to. If you do not want to do that, rather create an image of the partition to be rescued.

ddrescue -r3 /dev/hda2 /dev/hdb2 logfile
e2fsck -v -f /dev/hdb2
mount -t ext2 -o ro /dev/hdb2 /mnt

Example 2: Rescue a CD-ROM in /dev/cdrom

ddrescue -b 2048 /dev/cdrom cdimage logfile

write cdimage to a blank CD-ROM

This example is derived from the ddrescue manual.
Example 3: Rescue an entire hard disk /dev/sda to another disk /dev/sdb
copy the error free areas first
ddrescue -n /dev/sda /dev/sdb rescue.logattempt to recover any bad sectors
ddrescue -r 1 /dev/sda /dev/sdb rescue.log

So my head is hurting now
I need to get some rest.

There is also a program called 'ddrscuelog' which can be run to view the mapfile ddrescue creates, it will have all sorts of data as to what happened during the rescue.

GNU ddrescue Manual

14 Invoking ddrescuelog

The format for running ddrescuelog is:

ddrescuelog [options] mapfile
Use '-' as mapfile to read the mapfile from standard input or to write the mapfile created by '--create-mapfile' to standard output.

ddrescue is pretty neat program.

An example they give is this
ddrescue -f /dev/hda /dev/hdb mapfile
then
ddrescuelog -d mapfile

1. So do the recovery.
2. Then read the mapfile ddrescue created, which I suppose has the info your thinking of with recovery.log, which I suppose is the 'mapfile' ddrescue creates since that is what you called it when you ran your ddrescue command.

to run ddrescuelog command you have to be at the same command prompt as when you ran the first command at a linux command prompt.

It is also possible ddrescue deleted the mapfile, I saw an option for ddrescue to do that when it finishes.
Otherwise the mapfile should still be there.

A new version 1.2 of ddrescue was released on 14 Sep 2015. It has many changes. The logfile is renamed as mapfile. "NOTE: In versions of ddrescue prior to 1.20 the mapfile was called 'logfile'. The format is the same; only the name has changed."

The latest version of SystemRescueCD 4.6.0 was released on 08 Sep 2015 prior to the release of 1.2 ddrescue. So the old notation logfile holds.

Anshad Edavana used Parted Magic to run ddrescue in it. But Parted Magic became commercial at some point of time. If one is using a old version of Parted Magic which was free prior to that date then he should still use logfile name since it will only have older version of ddrescue.

Linux distros that have ddrescue tool in it may not have the latest version of ddrescue but one can update the ddrescue in it just as we update versions in Windows.ddrescue can also be installed in Linux distros that don't have it by default. But we are not Linux users :).

I specifically chose SystemRescueCD as the ddrescue source since it is updated frequently incorporating latest version of the tools. So one can expect that the next version of SystemRescueCD will have ddrescue 1.2 and then the commandline will be something like

ddrescue -f -r3 -v -n /dev/sdd /dev/sdc mapfile

That still does not answer where exactly is the logfile/mapfile and how to read it. That is for the younger more energetic and resourceful nkaufman and sdowney717 to deal with.:)

jumanji said:

That still does not answer where exactly is the logfile/mapfile and how to read it. That is for the younger more energetic and resourceful nkaufman and sdowney717 to deal with.:)

To be more specific, all we need is how to get to logfile/mapfile. I think we have a few viewer tools that we can use to view the logs but first need to get our hands on that darn log

Perhaps we wait for someone to clone their failing disk and suggest mapfile this time and see if the log is saved on the flash drive.

If even that does not work then the next step is specifying a folder on flash drive to save the log (as done by Anshad and dragonballz4).

Those are the 2 options that I can think of to come up with the final command to be run in these cases.

I stumbled upon this post and registered to ask if anything more can be done for my laptop hard drive.

My 3-year-old Toshiba laptop 640G hard drive crashed a week ago. It still shows up in BIOS with correct name and size but won't boot up to windows or anything else (safe mode, recovery, etc.) Using a Win7 repair disk also leads to an empty screen. I take the disk out, put it in a USB disk enclosure and plug in another computer. It doesn't show up in Windows Explorer or Disk Management. I downloaded "Test Disk" but it doesn't recognize this disk either.

Since the only place I can see it is in the original laptop under BOIS, I put it back in the slot. I tried to boot with BootMed live DVD, then after reading this post, SystemRescueCD flash drive. Both result in "PXE-E61: Media test failure, check cable" error even though I changed the boot sequence to put DVD or USB ahead of HD in BIOS.

I already ordered another hard drive and will clean install Win7. Is there anything else I could try to recover files on the old drive?

Thanks for your help.

Welcome to Seven Forums.

When you boot with SystemRescueCD pendrive ( are you using the one time boot menu?) when boot is completed do you get the prompt root @ sysreccd /root%?

If not, I am afraid you are not using the onetime boot menu. ( On most PCs you would hit F12 when it starts booting to get the boot device menu from which you will select USB HDD or Usb device to boot from.)

https://craftedflash.com/info/how-bo...sb-flash-drive

Alternatively, How To Change the Boot Order (Boot Sequence) in BIOS

Thanks for replying Jumanji. I used F2 to get into BIOS then to Boot. I checked F12 1-2 times and it's the same sequence. For me boot never completed with the bad drive inside. It led to endless "PXE-E61: Media test failure, check cable, ...................... press any key to continue".

Just to make sure the pen drive was created ok, I used it on a good computer and was able to get to the prompt root.