Boot failure after removing slave drive

[billybarty]

I have my system disk pinned as master and my slave drive pinned as slave. When I have both drives installed the system boots fine. When I remove the slave drive it takes a long while for the drives to be detected and then after another long while I get a boot disk failure. Putting the slave drive back solves the problem. Sometimes with it removed the system is looking to boot from a network. I don't have any RAID setup on the board. Why would this be happening?

 

[BaudKarma]

Some drives use one jumper setting if they're a single drive, and a different setting if they're the master drive in a two-drive setup. That'd be my first guess.



I try not to let my ignorance prevent me from offering a strong opinion.

 

[G0AOZ]

How is your BIOS set re hard drives? If the parameters for the slave drive are still embedded after the drive is removed, then this would cause problems.

Either manually remove the slave drive parameters from the BIOS or do an "Autodetect" of the drives, save settings, exit and reboot.

ROGER - G0AOZ.

 

[garebo]

Between the two answers above, you should be all set.

Good advice + great people = tek-tips

 

[Rufusman]

If the drive is a Western Digital, (and I assume it is) then remove all jumpers if it does not have a slave connected. This will resolve all your problems.

RM

http://www.pcbsearch.com.au