Hello,
Using a brand new SDOCK2U313R (never used before), I am trying to clone a 8TB disk ST8000DM004 SATA III 5400RPM onto a 16TB ST16000NE000 STAT III 7200RPM (Both disk were tested upfront with SeaTools to be sure there was no bad sectors).
It’s running since +48h.
As I am doing a standalone copy (not connected to a PC), I am quite blind on the progress. I can only see the leds HDD2 and HDD1 blinking (red on an blue background) and the “second progress bar” blinking blue since +32h (the first one is now “fix”). (quick video here in case one sees it’s not a normal “status”: https://drive.google.com/file/d/16rx-2CUzZtpUUhl7PkWu8BbJVUQf3154/view?usp=drive_link
As the copier is advertised to do 28GB/min in “copy” mode (reason why I didn’t connect it on the PC), the cloning should have been completed within a few hours only, isn’t ?

15h later, it didn’t yet complete 50%… I did a hard shutdown of the copier…
I bought this device to avoid issues with copying 8TB of files via a PC and it’s actually going to take me more efforts and time …
After connecting the target disk to my PC, it appeared “offline” with one partition of 8TB and 8TB not allocated (I did set it “online” immediately to further test it’s content)
(I can’t post more than one screenshot as I am a new user
So I have to do multiple replies… sorry)
Once the disk “online”, I saw that the table of content of the target disk was the same as the source disk… it’s not abnormal… But doing a binary comparison of all files (using Beyond Compare), it appeared that many files were not copied properly
Here is the comparison with BeyondCompare
Before trying again the copy, could one help me wit these questions:
-
Could anyone tell me, based on the video, what this behavior (blinking leds) meant ? Based on the doc, it sounds to be “Start Duplication”…
-
What is the state of the leds for “ongoing Duplication” and “Duplication completed” ???
Hello @vletroye and thank you for your interest in our Community.
From our conversation over emails, it seems like you found the issue from your source drive having a bad sector (using ChkDsk). Unfortunately, our device requires a healthy disk in order to perform a stand-alone copy (it does not handle sector black list or error skip).
Our device generally will warn you when it’s encountered a fatal error. However, sometimes reading “difficulties” could simply stall it as it has no self-monitoring services to try and realize it’s taking too long or is stuck on a loop.
When handling a drive with potential reading problems, you can always try connecting our dock over USB and opting for a software-based solution: these can offer you more advance error recovery features and could even help copy or retrieve files in situations where a total copy isn’t possible.
Please let us know if you have any further question and have an excellent day!
Emmanuel B.