Skip to main content
Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Could it be connected to a slow USB port or have USB port driver issues? (ie did you plug it into a different port to the other disks - some motherboards have multiple controllers, not always the same chipset)
    – davidgo
    Commented May 3, 2017 at 21:17
  • This could be caused by the USB to (I assume) SATA interface in the enclosure as well. Normally you would want to run manufacture diagnostics on the drive as they often require a failure code to process the warranty claim (however you probably can just return to place of purchase without going through this). This said, you should not run desktop drives in a RAID array. If the drives encounter even the slightest problem they'll retry up to 30 seconds, causing the array to kick the drive out as failed.
    – I say Reinstate Monica
    Commented May 3, 2017 at 23:56
  • Thanks for the suggestions. I ran Seagate tests on the drive - the short self-test and the long generic (read) test both pass, while the short generic test fails (I get the same results testing all the drives of this type). But I guess a failed test may be good enough to return the unit to Seagate. I also used CrystalDiskInfo / SMART testing which also reports Good. I repeated a near-identical copy test on another drive of the same type (first deleting and then recopying the same group of files - roughly 1TB) and it took about 1/3 the time - about 6.5 vs 20 hours.
    – M Szil
    Commented May 5, 2017 at 11:33