Question Win 10 copy HDD to SSD fail

[IBMJunkman]

Win 10, copying huge directory (using ZTree) from 3 TB Hitachi HDD (drive Y) to new 4TB Samsung V-NAND 860 EVO. Copies 188GB of 276GB then fails. This is the entry in the event log. What does it mean and how do I prevent it?

The system failed to flush data to the transaction log. Corruption may occur in VolumeId: Y:, DeviceName: \Device\HarddiskVolume4.

Failure status: A device which does not exist was specified.

Device GUID: {bb5ade65-ae68-2866-1f00-59f40ad94591}
Device manufacturer:
Device model: Hitachi HDS723030ALA640
Device revision: MKAOA580
Device serial number: MK0311YHG6XH8A
Bus type: SATA

Adapter serial number:

 

[Furious_Styles]

Not sure what's going on. Give teracopy a try.

 

[razel]

For Hitachi, I think you can run Western Digital Diagnostics to get the SMART status and do a short test.

 

[IBMJunkman]

Downloaded Data Lifeguard Tools. Ran short test. It passed. Smart drive info shows green check marks on all attributes.

For Hitachi, I think you can run Western Digital Diagnostics to get the SMART status and do a short test.

 

[IBMJunkman]

Managed to copy the data directory by directory. Then ran into same problem copying the other HDD. Got the data off by copying a few directories at a time.

Both HDD are 10 years old. Guess it is time to junk them.

 

[BonzaiDuck]

Did you have trouble or indications of error when you were routinely using the Hitachi drives?

If not, were you simply using Windows "copy" and "paste", some xcopy program, or cloning software? I'd think it would not be the latter, or you wouldn't likely have obtained the log messages, but maybe that's not true . . .

 

[IBMJunkman]

Drives were normally destination drives for my shutdown backup process. Never tried to do high volume reads.

Did you have trouble or indications of error when you were routinely using the Hitachi drives?

If not, were you simply using Windows "copy" and "paste", some xcopy program, or cloning software? I'd think it would not be the latter, or you wouldn't likely have obtained the log messages, but maybe that's not true . . .