HDD failing – How to make an exact copy

Cee Dee

Honorable
Jan 29, 2014
8
0
10,510
I could use some help please. I just recently completed a new build, but seem to have a bad HDD. It seems to disappear from time to time; I am hoping it is just a bad drive. After several restarts, it’s back, and before I lose it again, I want to make an exact copy onto another drive I have on the system which has a drive letter, but is completely empty. Once I have accomplished that, I figured I would just switch the drive letters in disk manager and be out of the woods. Drive” C” is my Boot SSD, Drive “D “is the data drive that is intermittent, drive “E” is the empty drive. I moved the user folders onto drive” D” (I used the move location tab on each folder for the users to move them off the SSD and onto the HDD. Because of that, my system won’t run without both” C” & “D”. I appreciate any suggestions, sorry for the long post. System: Win 8.1 – Asus Z87Pro – Intel i7 4770k-Crucial Ballistix 16 Gb - Kingston HyperX 120GB SSD (Boot Disk) – (2) Seagate 1Tb HDD’s.
 
Solution
Hi,

I would suggest restoring your system first to the last previous working/usable condition using system restore. If the restoration is successful then start to clone the drive that has problems to a healthy drive or back up its contents. hope that helps.
Hi,

I would suggest restoring your system first to the last previous working/usable condition using system restore. If the restoration is successful then start to clone the drive that has problems to a healthy drive or back up its contents. hope that helps.
 
Solution
Thank you for your suggestion, I did as you said, and created a system restore. Then, my solution was to copy the one folder (Users) on my intermittent drive to the spare hdd, then use disc manager to change the drive letters, did a restart and I was good to go. By the way, when I went to swap out the "Bad" drive, and my system did not see it, on a hunch I used a spare SATA power cable (I have a Seasoinc Platinum 760w) and the drive appeared, so it seems that is was the cable, not the drive all along. Always something....Thanks again