Solved Broken harddrive or not being patient?

[smurfyy]

Well hey there, Eight Forums!
My first post over here! I think I'm posting in the right place!
Not sure if you guys will remember me from over at VF, well, I've made the jump from Seven to Eight, and I'm loving it so far, so much smoother!

Now, I'm having a bit of an issue with the laptop I bought back in February, an Acer Aspire V5-571G, specs should be in sig.
The laptop came pre-installed with Windows 8, I'm now starting to notice it performing slowly, taking it's time to do things, etc etc.
I bought a Kingston SSD-Now200 128GB SSD and drive adapter so I can replace the DVD drive in the laptop with the SSD. This had been working fine for the past few months where I was using it to store my Steam Library and other files that needed quick access.

Last week I bought a copy of Windows 8 Pro and a 1TB 7200RPM 2.5" drive with the intentions of replacing the OEM drive with the SSD, putting the 1TB in the drive adapter in the DVD drive slot, and installing a dualboot on the SSD of W8Pro and ElementaryOS using the 1TB as a data drive.

The installation of W8 and eOS went fine on the SSD, no problems at all.
I was able to use half of the space on the SSD for Windows and the other half for eOS, likewise I was able to partition the 1TB in half, one ntfs partition for Windows and an ext4 for eOS with no problems. Now, here comes the problems.

When copying files back over from the old harddrive, which was plugged in via a USB adapter, I noticed that the copy speed would keep jumping up and down, sometimes stop for a couple of seconds, then carry on like nothing happened.
Sometimes, when the copy would completely stop, looking at Task Manager would show the 1TB drive at 100% usage but 0KB/s read/write, then the drive would just disappear from Task Manager and Computer and the copy would complain that the drive I was copying to has been disconnected. I tested this on the eOS installation and noticed the same thing would happen but not as often, this made me think it was a driver problem so I updated/installed the latest chipset/controller/etc drivers but this made no difference.

For some reason, I found myself checking Event Viewer and noticed loads and loads of entries like "The IO operation at logical block address <numbers> for Disk 1 was retried."
This error message was coming up all the time while copying files back but the <number> was different, and then every so often when not copying files, then after a few minutes the drive would just disappear from Disk Management/Computer/Task Manager.

I had a quick google around and found a few articles/posts on other forums which suggested I changed from AHCI to IDE, booted into safe-mode and installed drivers, uninstalled the device driver for the 1TB then rebooted to let it reinstall itself, and some others, but none of them appeared to work.

I'm at a complete loss here of what to do. Is the drive faulty? Should I return it to Amazon and request a replacement? Have I missed a driver install? Is the laptop not capable of running an SSD and HDD at the same time?
The laptop is still use-able with the old drive, but means I need to completely strip the thing down to put it in/take it out.
Apologies for the nearly-wall-of-text post, I've lost sleep battling this over the past couple of days while trying to do college coursework for my Diploma at the same time. The joys of being a student

Cheers guys!
Danny

 

[smurfyy]

Welp, thought I'd drop a reply here.

Emailed the Amazon seller and they was more than happy for me to return the drive for a refund, which was sent off last week.
Last week I also borrowed a WD Blue 1TB 2.5" from a friend to test with, this returned no problems at all which I went on to buy from him, so that's now sitting in the laptop.

All of my files copied over to the WD absolutely fine, I was able to setup the partitions and swap for eOS, and I managed to setup the libraries and such for windows with no problems. The only thing I need to do it make eOS auto-mount the NTFS Data partition at boot, but everything is working fine now.

So, solved now!