Sign in with
Sign up | Sign in
Your question
Solved

Adding EIDE HDD (Maxtor Onetouch II as internal) to system with SATA boot drive causes system to no longer boot

Last response: in Storage
Share
August 30, 2013 5:51:35 PM

I had an old Maxtor Onetouch II whose USB jack I broke. I removed it from its casing and added it to an older system with a 780i SLI Mobo and an existing Windows 7 OS on a SATA boot drive. System freezes at startup now!

Actions taken :
1. Made sure jumpers on the new Maxtor drive are set to cable select (CS).
2. Changed the boot priority for HDD's to have the SATA drive first.

Any other suggestions? I'd like to see if I have any data on this drive from when I used it as an external.

a c 125 G Storage
August 30, 2013 5:55:50 PM

Set the drive as master with only one drive on the cable. Place your hand on the drive see if it spins up. If you have too try a USB to IDE cable on another system to see if the drive not damaged.
m
0
l
August 30, 2013 6:08:02 PM

smorizio said:
Set the drive as master with only one drive on the cable. Place your hand on the drive see if it spins up. If you have too try a USB to IDE cable on another system to see if the drive not damaged.


I tried it in both positions on the cable. Additionally, the drive does indeed spin up. It's been a few years, but I don't think anything about the drive itself is damaged. Since it's an external drive, it was attached to a little interface inside the casing. The USB-IDE adapter part had been ripped off the board by me stepping on it, I believe.

This is the drive and what I've done to "internalize" my Onetouch II. http://youtu.be/JlJ-zh5FW6g
m
0
l

Best solution

a c 342 G Storage
August 31, 2013 6:16:27 PM

If the Maxtor is the ONLY unit on the IDE cable, setting its jumper to "CS" should be fine as long as you make SURE that it is plugged into the END connector of the IDE cable. That will make it the Master on the IDE port.

You do NOT say that the system gives you an error message requesting that you insert a boot disk. You say the system just freezes totally. If that is true, it MAY be because the Maxtor unit is faulty, so badly that the BIOS gets stuck in a loop trying to get it to behave and answer properly when first started up. If the Maxtor can't Initialize cleanly, the BIOS may be receiving repeated error messages or time-outs from it and trying again to get a reply. Since it will try to check out every key hardware item before booting from the SATA unit, it will never get to the boot step. I'm guessing that, if you disconnect the Maxtor, the system boots just fine.

Maybe the Maxtor needs to be run through some thorough diagnostic tests. But not on your machine, probably - it may not be able to boot with a faulty IDE unit connected.
Share
!