Latest DE Express Version: Destination Write Errors

[300ddr]

On 2 separate drives, since the latest update, I get Destination Drive Write Errors in DE. It always stops on the same sectors. I can avoid these sectors and everything works fine. But, the sectors in question are good on the destination drive. The destination drive(s) (I've tried several) are perfectly fine, 100% of the sectors are good.

It seems like the problem may be a bad sector on the source drive, but why is this affecting the destination drive? Changing destination drive = problem remains. Swapping dock, cable, etc, still happens. I always have "disable MBR" checked. Also, I've tried with "list of ranges" and "binary" files map types.

Any ideas on why this is happening and how to prevent it? I can't figure out why it's happening.

Thanks,
Brian

[300ddr]

So no one else has this problem? It seems like at least 1 drive per day has this problem for us (so far Seagate and Western Digital, I think they are all 4096 sector size also). Probably had 5 total so far. If moved to Deepspar then works fine.

[Nick_TS]

Hello,

Is this issue still actual?

[300ddr]

Yes, still happening all the time. At least once a day with the 8 recoveries we may have running on a PC3K Express. It hasn't happened on the UDMA Express, but perhaps that is just because it is less used? But yes, it happens still. Usually we move the drive to Deepspar instead, it works fine there. We have tested the destination drives and they have no actual bad sectors.

[Nick_TS]

Hello,

- Can you tell me what is your DE version and what drive you are working with?
- What models of drives have this issue ?

[300ddr]

DE: 5.2.8 (U)

Some of the "source" drives we were imaging when this problem occurred include:
ST3000DM001 (3 of these drives had this problem)
WD30EZRX
ST100LM024
ST4000DM000

I believe these are all 4096 sector-size drives... and I think that may have something to do with the problem. I don't recall any non-4K sector drives with this problem.

The only "destination" drive I can find right now that we know had this problem is:
HDS724040ALE640 (this drive worked fine on DDI after moving from DE where it had destination write errors)

[300ddr]

Happened again:
Source drive: WD30EZRS-00J99B0
Destination drive: WD3001FAEX-00MJRA0

[300ddr]

Another:
Source: Toshiba DT01ACA3000
Destination: Seagate ST3000DM001

[300ddr]

FYI...
I moved the WD30EZRS-00J99B0 from a PC3K Express (64bit Windows 7) to PC3K UDMA-E (32bit Windows 7) and it finished imaging with no errors. Perhaps the problem is related to PC3K Express and/or 64-bit.

[eazycut]

Hi

This happend me also some times, when destination drive is connected to sata motherboard. Destination drive no bad sector. I get Catastrophic failure if i remeber correct.. But when running same job internal on Udma ata0 to ata1 works good. But i am not supposed to image form sata0 to sata1 on the udma.. Then i can only work on 1 drive at the time in DE with the udma.

This doesnt happens every time but sometimes and it get a little bit frustrating when i want to work with another drive same time. Destination drives are often/all Seag and WD..

Right know it is working.. seems to be certain drives..

I will make a list when it happens and which dest drives make model i am talkning about..

Thx

/eazycut

[OHMYDATA]

In my case,
It's modify mbr bug.
check modify mbr, but target secor 0 , 510~512 values is x'55aa'.
So update value to x'55bb'.
Then restart clone, success clone.

pc3000 exp 5.9.21
de 5.2.26
os : win 7 kor 64 bit
souce :st3000dm001
target : st3000dm001 cc52 connect with sata 3

[OHMYDATA]

It's my mistake.
destination problem not solved

[Bruno]

Hi all,
I'm working with PC-3000Express since 8 months, on the same PC where i using PC-3000UDMA, the last Years till switch to PC-3000Express.

Now i found dangerous Problem with DE Ver 5.3.2(U), Build 5.3.2.(U)3285.
Copy from e.g. SATA2 to SATA3. All Secotrs are green, but after saved the recovered Data from destination Drive, i found any Files (JPG) that are corrupt...
After view the same Files from Source, that are ok.

I have changed the PowerUnit and RAM of the PC without results.
The Developers form ACE are searching the cause.
The Problem exist only by copy fro PC3K-SATA to another. If i copy from eg. PC3k SATA1 to SATA from Mainboard, all is ok.

Any Users what having same Problem, and maybe a solution?
Bruno

[lcoughey]

The only times I get destination write errors is if the OS somehow tries to mount the destination. Sometimes this is because deactivate MBR was not enabled or because the clone already had the active MBR from an earlier clone attempt on a different system. I simply edit sector 0 to 55BB, got to disk utility, hit refresh and then continue imaging in DE.

[DataMedics]

Sounds like Bruno's issue is that the files are actually corrupt after writing though.... seems different than when the OS blocks access to the destination (which can get annoying, until you get smart and disable auto mount like I did). Are you leaving the option checked to save problem files to a !Problem folder? Perhaps they just had bad sectors and were saved with missing data. Or perhaps it's also a logical issue.