I have two SATA hard drives connected to a SATA PCI card on Windows XP. The boot drive is a WD Black and the storage drive is a Maxtor. I've been getting BSOD's periodically (Invalid process detach attempt) and couldn't figure out what was causing them but everytime it happened I just restarted and everything was ok again.
Well this last time the BSOD happened I shut down the pc instead of restarting and decided to switch the RAM in different slots just to see if that would help. I also plugged in the SATA cables into different SATA ports (the SATA card has 4 ports). Then I restarted and that's when I got the Disk Boot Failure Insert System Disk and Press Enter message. I put the RAM sticks and cables back to their original place but I still get the error.
After isolating the drives I found out it was the storage drive causing the error message. If I try to boot the pc with both drives attached I get the error. If I boot with only the storage drive attached I get the error. If I boot with only the boot drive it loads into Windows with no problem. So there seems to be something wrong with the storage drive. I don't think the drive is failing since I haven't heard any sounds coming from it that a dying hard drive typically makes.
Then I (stupidly?) decided to boot with only the boot drive attached, then after it was recognized during bootup I immediately plugged in the SATA cable to the storage drive. When I got into Windows I opened My Computer and saw the storage drive there but it was empty. Actually I didn't even try to double click on the drive, I right clicked and clicked Properties and saw it was empty.
Anyone know what's wrong? Why do I get Disk Boot Failure when both drives are attached but the boot drive is fine? It's like my pc thinks the storage drive is supposed to be the boot drive. Does it have anything to do with the MBR being damaged or does that only apply to the boot drive? How can I save the drive please help!
p.s. I forgot to mention I the storage drive has been encrypted with True Crypt. When I tried to mount the storage drive in True Crypt it said, "Error: Cannot mount volume. The host file/device is already in use. Attempt to mount without exclusive access failed as well.
Well this last time the BSOD happened I shut down the pc instead of restarting and decided to switch the RAM in different slots just to see if that would help. I also plugged in the SATA cables into different SATA ports (the SATA card has 4 ports). Then I restarted and that's when I got the Disk Boot Failure Insert System Disk and Press Enter message. I put the RAM sticks and cables back to their original place but I still get the error.
After isolating the drives I found out it was the storage drive causing the error message. If I try to boot the pc with both drives attached I get the error. If I boot with only the storage drive attached I get the error. If I boot with only the boot drive it loads into Windows with no problem. So there seems to be something wrong with the storage drive. I don't think the drive is failing since I haven't heard any sounds coming from it that a dying hard drive typically makes.
Then I (stupidly?) decided to boot with only the boot drive attached, then after it was recognized during bootup I immediately plugged in the SATA cable to the storage drive. When I got into Windows I opened My Computer and saw the storage drive there but it was empty. Actually I didn't even try to double click on the drive, I right clicked and clicked Properties and saw it was empty.
Anyone know what's wrong? Why do I get Disk Boot Failure when both drives are attached but the boot drive is fine? It's like my pc thinks the storage drive is supposed to be the boot drive. Does it have anything to do with the MBR being damaged or does that only apply to the boot drive? How can I save the drive please help!
p.s. I forgot to mention I the storage drive has been encrypted with True Crypt. When I tried to mount the storage drive in True Crypt it said, "Error: Cannot mount volume. The host file/device is already in use. Attempt to mount without exclusive access failed as well.