Secondary hard drive sometimes boots up rather than primary
Posted on 2004-08-20
I ran into this situation, and need to be able to absolutely avoid it in the future, if possible: one day the user's IBM desktop computer booted up on the extra hard drive attached to the secondary IDE controller, rather than the 'normal' hard drive attached to the primary controller. Is there a way to insure that this will not happen?
Here's the background: I had the 'normal' hard drive on the primary controller, and an extra HD on the secondary controller. Both were jumpered as master, I believe; one or both MAY have been jumpered CS, but I don't think so.
Anyway, I ran norton ghost and made a complete image of the 'normal' drive to the extra drive. The problem was that when the computer rebooted itself after running ghost (which is normal), it booted up on the extra drive. However, I did not realize it at the time--there was no warning and no way that anyone would have known, without looking in control panel or some such. BTW, I was running XP Pro.
A week later I was at the customer site doing some work, and after shutting down their system and turning it back on, I left. The next day, they were calling in a panic telling me that a week's worth of work was gone. After looking at the drives contents (file dates, etc.), that's when I finally discovered that a week prior, it must have booted up on the extra drive, and they ran on that for a week, and then when I turned on the computer that night before, a week later, it booted up to the 'normal' drive like it was supposed to...and of course the 'normal' drive had not been in use for a solid week, so it's data was old.
Note that in the bios, the boot sequence is set to diskette, then hard drive 0 (the 'normal' drive on the primary channel). There's nothing specified for hard drive 2, which would have been the extra drive.
On some earlier IBM models, I know from experience that a hard drive WILL NOT boot unless it is plugged into the primary controller--I tried it, repeatedly. But on newer models, you can boot up on either controller. Even so, I don't know why or how it booted up the extra drive that fateful night instead of the 'normal' drive. Yet it clearly happened, causing all kinds of problems, and scares me away from setting up a 'ghostable' drive for my users, feaful that this kind of thing could happen again, without anyone knowing it.
Any ideas why or how this could have happened, and whether there is any surefire way of avoiding it, while still keeping both drives connected to their cables and ide controllers?