Hi,
When cloning offline, does the target disk need to be formatted? just initialized? Variosu cloning software's handle thsi differently.
My source disk is 3 TB WD Black initilalized GPT, formatted NTFs with ~ 1.5 TB Data. The target disk I'm cloning to is 5 TB Black, initialized GPT, but not formatted. After starting the offline cloning process, the 25 % light has been blinking for 3 hours now. Is thsi working and just slow?
It would be helpful to know if I need to format the target disk, or just start the offline clone with it just initialized.
Tim
@sammsunn20 Make sure the source disk has no errors or other issues. Same with the destination drive if it's older. Offline clones are sector-by-sector which can be quite slow by today's standards, though.
Disks are 100% fine, no sector errors, no reallocated sector count, etc,
but can you please tell me if the target disk needs to be formatted? Or is it enough to just be initilalized?
Currently 5 hours with the 25 % light blinking. Just from ballpark experience, an AOMEI sector by sector clone would be probably 1/3 to 1/2 done now given the amoutn of th etransfer (~ 1.5 TB)
@sammsunn20 Our assumed rate would have it take 6 hours or so, so it should be past 25% after 5 hours. The docking station should not be connected to anything via USB during this process. The destination drive should not require any formatting before engaging in the clone process.
@Sabrent
TYhanks, I think your timeline estimnate is accurate.
Because this is an offline clone, the USB cable was disconnected before the clone started. I followed the instructions from the booklet exactly, to a T. Then confirmed online from your support page for the EC-HD2B, that a blinking 25% light was indicatin that the process had correclty started. (that piece of info was omitted from the enclosed beochure).
So this leaves me with a situation where it is still blinking 25% after 6 hours. It has obviously failed. What would you suggest I do to interrupt this without causing hardware damage?
Thanks
OK, temporarily crisis averted. I decided the only option I had was to turn off the power, then remove both drives and insert them one at a time to check. What's strange is that the clone appears to have worked. Both drives show the exact same amount of data.
When I try to plug both in via the Sabrent dual station, either one of the two drives gets an error in disk management (Win 10 Pro) that "the disk is offline because it has a signature collision with another disk that is online".
I removed each drive again, insert each individually, & manually assigned a new drive letter. But when both a re then plugged in together again, Windows identifes it as the same drive and gives it the same siganture collision error.
I scanned each drive and they shows no errors. CrystalDisk info SMART data shows 100% health and no errors, so there appears to be no damage to either drive.
But this does not inspire confidence in this product. I love Sabrent NVMe's, your heat sinks are outstanding. But this offline clone process needs some revision. I followed the instructions exactly. To have it just sit at flashig 25% for over 6 hours is not acceptable, when it appears to have completed in the background. I need to do a data integrity check to see if the comparison is equal.
This is less than two weeks old. I will probably return this product
Wow, well that was unneccessarily convoluted and stressful. As a docking station it's fine, as a cloning tool it needs work.
@Tim The signature collision is because they are being seen as the same drive, or basically the same identifier. This isn't unusual but it can be confusing. Glad it worked but we will look into why progress may not have been indicated.
