I have a failing WD Green 2TB that is about 70% full. It is out of its warranty period.
I have a new WD Black 3TB that I would like to move the data onto.
The OS is installed on a separate drive. The only thing in the WD drive is media and uninstalled files.
I can't seem to find a current post with this issue. Most people have a failing OS drive and need recovery.
I would rather copy everything over to the new drive and then circle around to see if the old one can be "fixed".
The drive started experiencing extreme slowness when moving new files. Reading those files (playing through XBMC or VLC) is also starting to become jumpy. Some write/reads seem okay while others take a very long time. These issues are the most apparent in Windows Explorer while moving files around.
I ran Arconis Health Monitor and it says 60% health on this drive.
I am running a test with the WD disk tool to see if it is a bad sectors issue and how many.
edit: my box only holds 2 HDDs so I'll probably have to get an external enclosure to be able to work on both the big drives at the same time. My friend has a "slave kit" but no enclosure. I don't know how this would be used, any clue? Lastly... do I even need an external enclosure if I only plan on hooking the drive up for transfer? can I just secure it to the top of the case?
Thanks!
RESOLVED: I was able to add the new HDD with a MOLEX to SATA power adapter and a new SATA cable directly to the motherboard.
I attempted to use Acronis True Image WD edition from the WD site but even after waiting for the extremely slow interface (it may have been due to the fact that the drive had a few errors)... it did nothing. I told it to clone and it would not. It asked me for a restart and it did nothing.
Finally, since the source and target HDDs were not my OS drive I decided to open up windows explorer and simply copy files, being careful not to copy over files created in the last month (where these errors happened)
THINGS I LEARNED: Whenever I tried to access a file that had parts in an error sector, my entire system would hang up. I learned that this is due to the fact that the HDD was plugged directly into the motherboard via SATA. When a read request was sent to the HDD, the request was mishandled but never timed out. So any subsequent requests to stop or anything like that were behind in the queue. Essentially locking down the SATA controller and therefore all HDDs.
This (I read) is not so much a problem with NAS drives that have a built in time-out period, but a problem with consumer drives with no time-out.
This can be mitigated by creating an extra layer between the HDD and the SATA controller... namely by plugging the HDD in via USB on an external enclosure. Where if it hangs like this, the whole PC is not locked out.
Please correct me if I am wrong
My next step is to use chkdsk to try to correct the old HDD and see if it can be saved to be used as a DVR drive where the data is not important.
I will mark down paperdoc's response as correct because it was detailed and had the correct steps and precautions. Acronis not working for me does not mean it will not work for the next person.
I have a new WD Black 3TB that I would like to move the data onto.
The OS is installed on a separate drive. The only thing in the WD drive is media and uninstalled files.
I can't seem to find a current post with this issue. Most people have a failing OS drive and need recovery.
I would rather copy everything over to the new drive and then circle around to see if the old one can be "fixed".
The drive started experiencing extreme slowness when moving new files. Reading those files (playing through XBMC or VLC) is also starting to become jumpy. Some write/reads seem okay while others take a very long time. These issues are the most apparent in Windows Explorer while moving files around.
I ran Arconis Health Monitor and it says 60% health on this drive.
I am running a test with the WD disk tool to see if it is a bad sectors issue and how many.
edit: my box only holds 2 HDDs so I'll probably have to get an external enclosure to be able to work on both the big drives at the same time. My friend has a "slave kit" but no enclosure. I don't know how this would be used, any clue? Lastly... do I even need an external enclosure if I only plan on hooking the drive up for transfer? can I just secure it to the top of the case?
Thanks!
RESOLVED: I was able to add the new HDD with a MOLEX to SATA power adapter and a new SATA cable directly to the motherboard.
I attempted to use Acronis True Image WD edition from the WD site but even after waiting for the extremely slow interface (it may have been due to the fact that the drive had a few errors)... it did nothing. I told it to clone and it would not. It asked me for a restart and it did nothing.
Finally, since the source and target HDDs were not my OS drive I decided to open up windows explorer and simply copy files, being careful not to copy over files created in the last month (where these errors happened)
THINGS I LEARNED: Whenever I tried to access a file that had parts in an error sector, my entire system would hang up. I learned that this is due to the fact that the HDD was plugged directly into the motherboard via SATA. When a read request was sent to the HDD, the request was mishandled but never timed out. So any subsequent requests to stop or anything like that were behind in the queue. Essentially locking down the SATA controller and therefore all HDDs.
This (I read) is not so much a problem with NAS drives that have a built in time-out period, but a problem with consumer drives with no time-out.
This can be mitigated by creating an extra layer between the HDD and the SATA controller... namely by plugging the HDD in via USB on an external enclosure. Where if it hangs like this, the whole PC is not locked out.
Please correct me if I am wrong
My next step is to use chkdsk to try to correct the old HDD and see if it can be saved to be used as a DVR drive where the data is not important.
I will mark down paperdoc's response as correct because it was detailed and had the correct steps and precautions. Acronis not working for me does not mean it will not work for the next person.