hi guys , i have a Seagate 1TB 3.5 Hard Drive and it was acting weird (slow transfers) so i ran CrystalDiskInfo and found the below. I then changed the USB 3.0 cable to my USB Enclosure and transfers hit around 130 megabytes a second. I did a full error check in HD Tune Pro and no read errors , after that i ran CrystalDiskInfo again and the 'Read Error Rate and Hardware ECC recovered' improved dramatically. i was wondering if the dead USB 3.0 cable caused the bad stats in CrystalDiskInfo and the HDD is safe to use ? chat soon
Yes, "good quality" USB cables, can influence data transfer speeds VERY much. https://en.wikipedia.org/wiki/USB_3.0#Data_transfer_and_synchronization https://en.wikipedia.org/wiki/Low-voltage_differential_signaling Throw useless cables away, don't use those "bad" cables to charge a device, even that can be influenced by a bad cable. Some 3rd party "Iphone" cables can only charge at a low amperage, so it takes very long to charge. And a fire caused by a fake "good quality" charger, cable, or battery ....... Well you do not need that for a few bucks more or less. A nice thick rubber cable "shielding" does nothing, the internal copper cables need to be "thick", twisted and RF shielded. So the errors you had were probably caused because of a bad fitting, low quality cable or (internal) connector. Harddisk S.M.A.R.T. status should give you a warning before hand.(hopefully) BUT it is always better to have a backup !
I would agree, I have seen some horrible quality cables come with even name brand drives and enclosures and this was a typical result
thanks guys , the cable i used was a very popular one on Amazon with many great reviews and few 1-2 star complaints. Even though i have purchased another brand and waiting for delivery from a local PC shop.
Raw Read Error Rate/Seek Error Rate/Hardware ECC Recovered on Seagate drives work like a counter - when drive is working there will be some errors, always, but drives have error correction mechanism. Seagate drives report even corrected errors to SMART, some Samsung drives do that too. While WD/Hitachi/Toshiba report only errors that weren't corrected. For Seagate SV series Command timeout is another "counter". Just ignore those on Seagate drives.