My hard drive appears to have some bad sectors, picked up by Acronis Drive Monitor. Have run chdsk /r /f several times, and although no error is detected I know there are some bad sectors still, so am ready to replace the HD.

Am able to boot fine and use computer as normal until I run Macrium Reflect V5 Professional Edition.When performing a clone it hangs each time at NTFS Primary and gives the following message:-

Clone failed- Read failed - 22 - Broken pipe etc

Have enabled ignor bad sectors in settings, but cannot clone disk from OS.

Any ideas apart from using the 1GB boot disk, which I am currently unable to download within the next 24hrs?

Please help.

Replies:

Reply author: Drac144Replied on: April 30 2013 20:07:49Message:

When cloning did you specify the drive to clone from (i.e. C:) and the drive to clone to (whatever drive letter your clone is assigned when connected to your computer)?

Have you tried doing a full image backup? If you can do that then you can switch drives and restore the image backup to the new drive. It is a two step process instead of the one step process of cloning but it is the same thing, logically.

Reply author: richie3000Replied on: April 30 2013 22:02:34Message:

Thanks for getting back to me.

When cloning, I just click the "clone this disk.." then select my external SSD. The SSD shows on Relect as Destination Disc, with two partitions (from previous failed clone).

I've not tried doing a full image backup, but it's a good idea. Will give it it go shortly.

Thanks again for the advice.

Reply author: richie3000Replied on: May 01 2013 12:45:06Message:

quote:Originally posted by Drac144

When cloning did you specify the drive to clone from (i.e. C:) and the drive to clone to (whatever drive letter your clone is assigned when connected to your computer)?

Have you tried doing a full image backup? If you can do that then you can switch drives and restore the image backup to the new drive. It is a two step process instead of the one step process of cloning but it is the same thing, logically.

OK, I tried doing an image backup as suggested instead and got the same error.Managed to create Macrium boot disk and got same 'read failed 22' error when performing a clone from the rescue environment. It always fails in the same NTFS Primary sector.

However, creating an image from the rescue environment seemed to work. It's a much smaller file size than expected, 159Gb vs 207Gb, so be interesting to see if this backup will work on the new HD.

Thanks again for the advice to do the image instead, as I would have ignored this option.

Reply author: richie3000Replied on: May 03 2013 13:13:10Message:

UPDATE:Good things. The restore from a rapidly failing hard drive worked brilliantly using the Rescue Environment.Had to write the image to drive twice, and first one failed to boot after a couple of Windows restarts. Have since found out that you can fix Windows boot problems, which is available in the Windows PE Rescue media environment.Grateful to the developers of this well designed product.Thank you!

Reply author: kristerwReplied on: June 14 2013 12:51:41Message:

'creating an image from the rescue environment seemed to work'

what are the exact steps for this?

Reply author: NickReplied on: June 15 2013 07:59:16Message:

@kristerw

Thanks for your post.

You can create an image from the Windows PE rescue CD in exactly the same way as when Macrium Reflectruns in Windows. Click the 'Backup' tab after Windows PE loads.

Kind regards

Nick - Macrium Support

Reply author: rfordReplied on: October 31 2013 00:58:00Message:

I am having big problems cloning my C hardrive on my laptop to a USB connected Samsung SSD. Cloning fails with Error 22 Broken Pipe. I have tried the rescue environment and booted. I am running v5.2 of your software. C drive boots fine but I want to clone to a new SSD to replace the harddrive in my laptop. I have run disk check multiple times including bad sector checking on the harddrive and no problems there. I am running win764-bit with all the latest updates. Please help. thanks Bob

Reply author: C.BamfordReplied on: October 31 2013 09:33:25Message:

Hi,

Thanks for posting.

There could be an issue with the USB connection to the target drive (e.g.: USB ports, cable or subsystem).

Please try a different USB cable and port, if possible rule USB out by connecting the target SSD to an eSATA port.

Kind regards.Chris - Macrium Support

Reply author: rfordReplied on: October 31 2013 14:18:32Message:

Hi Chris, have tried 2 usb cables and different usb ports, same result. I do not have an e-sata connection on my laptop. I am using a USB3.0 drive enclosure but my laptop only supports USB22.0, could this be the issue?

It appears to be a read issue on the source internal hard drive not a write issue for the target, in that I also cannot image the C drive to another D partition on the same drive. Could this be a bad sector(s) issue on the source drive? Windows drive check when I set it to scan bad sectors, finds a few but it says its repaired. Is there any way to have REflect ignore bad sectors on the read during a clone?

quote:Originally posted by C.Bamford

Hi,

Thanks for posting.

There could be an issue with the USB connection to the target drive (e.g.: USB ports, cable or subsystem).

Please try a different USB cable and port, if possible rule USB out by connecting the target SSD to an eSATA port.

Kind regards.Chris - Macrium Support

Reply author: C.BamfordReplied on: October 31 2013 14:41:15Message:

Hi Bob,

Thanks for posting back.

The chkdsk that has been previously run, was the command line parameter /r specified ? Also was chkdsk run under an elevated prompt ? This process will, usually, resolved error code 22 issues.

Please try creating an image file in the rescue environment, if this succeeds you and restore it to the SSD.

Please let us know how you get on.

Kind regards.Chris - Macrium Support

Reply author: rfordReplied on: November 01 2013 17:48:44Message:

Chris, I attached the samsung SSD to a USB 2.0 enclosure and the clone failed with the same error. I was not in the recovery environment but was booted into win 7

I booted into the recovery environment, I used the dos prompt to run chkdsk C: /F /R on my hard disk and although it found 80KB of bad sectors it said the filesystem was fine and made no corrections. I am now trying a create image from the C: Drive to the D: partition, same hard disk. I'll let you know.

Bob

quote:Originally posted by C.Bamford

Hi Bob,

Thanks for posting back.

The chkdsk that has been previously run, was the command line parameter /r specified ? Also was chkdsk run under an elevated prompt ? This process will, usually, resolved error code 22 issues.

Please try creating an image file in the rescue environment, if this succeeds you and restore it to the SSD.

Please let us know how you get on.

Kind regards.Chris - Macrium Support

Reply author: rfordReplied on: November 03 2013 16:17:04Message:

Chris, creating the image file from the rescue environment worked and so did restoring it to the SSD. Cloning does not work as mentioned. Thanks for your help.

quote:Originally posted by rford

Chris, I attached the samsung SSD to a USB 2.0 enclosure and the clone failed with the same error. I was not in the recovery environment but was booted into win 7

I booted into the recovery environment, I used the dos prompt to run chkdsk C: /F /R on my hard disk and although it found 80KB of bad sectors it said the filesystem was fine and made no corrections. I am now trying a create image from the C: Drive to the D: partition, same hard disk. I'll let you know.

Bob

quote:Originally posted by C.Bamford

Hi Bob,

Thanks for posting back.

The chkdsk that has been previously run, was the command line parameter /r specified ? Also was chkdsk run under an elevated prompt ? This process will, usually, resolved error code 22 issues.

Please try creating an image file in the rescue environment, if this succeeds you and restore it to the SSD.

Please let us know how you get on.

Kind regards.Chris - Macrium Support

Reply author: C.BamfordReplied on: November 04 2013 09:14:23Message:

Hi,

Thanks for posting back.

Error code 22 is generally indicative of impending hardware failure or a faulty disk, especially in the case of a read process. This type of issue can be an intermittent.

As you now have a working image in hand which restores successfully it is suggested to remove the, possibly, defective drive from the computer and attempt the clone operation again should the need arise.

As you will be aware, the process of creating an image and then restoring that image to a new hard drive achieves the same result as the clone process.

Kind regards.Chris - Macrium Support

Reply author: rfordReplied on: November 04 2013 19:40:11Message:

Chris, I attached the samsung SSD to a USB 2.0 enclosure and the clone failed with the same error. I was not in the recovery environment but was booted into win 7

I booted into the recovery environment, I used the dos prompt to run chkdsk C: /F /R on my hard disk and although it found 80KB of bad sectors it said the filesystem was fine and made no corrections. I am now trying a create image from the C: Drive to the D: partition, same hard disk. I'll let you know.

Bob

quote:Originally posted by C.Bamford

Hi Bob,

Thanks for posting back.

The chkdsk that has been previously run, was the command line parameter /r specified ? Also was chkdsk run under an elevated prompt ? This process will, usually, resolved error code 22 issues.

Please try creating an image file in the rescue environment, if this succeeds you and restore it to the SSD.

Please let us know how you get on.

Kind regards.Chris - Macrium Support

Reply author: marklightReplied on: August 12 2014 03:34:36Message:

I struggled with this over the course of a few months. Nothing work in terms of correcting this problem. Then I gave up and decided to recycle the defective external drive. I ran a regular format - not the quick format on the drive. And guess what? No error - a perfect clone. Problem solved.

Mark J Light

Reply author: SeekforeverReplied on: August 12 2014 13:43:25Message:

A format for many years, since IDE disks, is nothing more than setting up a new, empty filesystem on the disk - unlike formatting the old RLL disks where a so-called low-level format would actually re-write timing tracks on the disk.

However, doing a the normal instead of the quick format causes a scan for bad sectors on the disk which is why it takes so long. Sounds like it found some and mapped them out.