Destination drive write error

[Nick_CT]

Irrespective of what version of DE I'm running, the latest version or a version that's a year old, I get so many 'destination drive write errors'. They are actually becoming more frequent, and happen a lot more often with HFS file system jobs. Even large capacity NTFS jobs have the same problem, if I'm doing an NTFS job to a 3TB destination it's bound to bomb out at some random place with a destination write error.

Changing destination drive model and brand doesn't help. Changing destination drive interface doesn't help, USB 2 or 3 on different USB host controllers. Anti virus turned on or off, doesn't seem to make any difference.

I do as many jobs as I can using 'task files' and there are never any issues with those, but sometimes you just want to do a job using a destination drive, especially Mac jobs.

Does anyone have any tips or workaround? It's irritating me beyond belief now, 3 of the 4 drives currently connected up to PC3K Express keep stopping for no apparent reason with this annoying error. Getting ready to chuck this machine out the window...

I'll ask ACE what they suggest, but I don't think I'll get anything to constructive from it.

[Nick_CT]

To add, I also choose 'modify MBR' and 'offline destination', doesn't seem to help.

[Nick_CT]

In the earlier days of PC3K there were no such issues, I'm talking a few years back. I've been imaging to the same USB docks for the last 5 years and only recently have I had issues with all of them. I've also always been using Windows 7. From what I can see, the changes have been Windows updates and PC3K updates.

I know a lot of other people suffer from this, it's not only me.

Imaging to SATA doesn't really make sense for a number of reasons, I don't see why I should stop doing that I've been doing that's worked very well.

Thanks for the suggestions, but they are workarounds to a problem that I feel is on the ACE side and should really be resolved.

[pcimage]

I have been getting errors like that more recently when cloning to USB drives too

[F_ARG]

I used to had those problems too. I have realized that sometimes was the power SATA cable cause after several times i connect and disconnect they damaged (false contact). In addition, I am now checking detination SMART before begin to clone and things are going better (surprisingly there were destintation drive with SMART problems).

Best!

F

[northwind]

I have this as well. If you image to .bin files via USB the problem disappears. But if you make sector by sector clone to a USB drive you have this problem.
There is a workaround, if you close task and change USB port 2 or 3 times, it works. But it's very frustrating.

[Nick_CT]

Thanks, I knew it wasn't only me. Either way, I've done a few HFS jobs after making these changes and I haven't had a problem since. Could just be coincidence, but it has helped me. Ensure these two are deselected.

[studiogsm]

I have problem too. New version, new bugs.

[thatdellguy]

I used to have destination write errors but only when imaging a 3gbps drive on a 6gbps SATA slot or the reverse. Haven't seen that error for some time now when the drive is paired to its proper speed. On some drives I jumper the speed down to 3gbps. Currently using Windows 7 64bit, 32GBs ram, i5, and Gigabyte MB. Imaging to USB I always make a solid bin image file. Haven't seen that error since two versions ago.

[Nick_CT]

Update on this, I haven't had one destination write error since disabling those two options, so it's a good fix.