Fr3d.org
«  |  Fr3d.org Home  |  »

Cable Changes

Every now and then, when Windows crashes, and I have to reset my PC, the motherboard only detects 1 or 2 of my 4 SATA2 hard disks. It’s always the ones connected to the 3rd and 4th sockets (so it says on the board), but these are actually the 1st and 2nd devices as seen by both Windows and Linux.

So today, after removing 2 currently un-used and un-powered drives from the case, I swapped the cables around (and tidied them using some spare spiral wrap), so that it would stop moving the main boot drive to be third in the boot order preference list.

But of course, Windows didn’t like this, and I got an ever-so-helpful message on boot:

NTLDR is missing.
Press Ctrl+Alt+Del to restart.

The fix was easy, I just swapped the cables back.

while ($system->has_changed()) { show_unhelpful_error_message(); }

Grub (The standard Linux boot loader) can handle you moving drives around… It barely blinked on mine; it just said “invalid path” (or something along those lines), and was very easy to correct.

But Windows? Oh no! That’s far to difficult… *sigh*.

One Comment to “Cable Changes”

  1. John Anderton  says:  

    Vista didn’t like me connecting a ATA drive after installing windows into a SATA drive. It just wouldn’t boot. So I ended up formatting again with the ATA drive connected this time.
    While booting hence forth I got 2 options. A “Windows Vista” and a certain “Earlier Version of Windows” :S
    Nothing a little [u]bcdedit[/u] couldn’t fix :P I just had to delete the NTLDR entry.

    The problem at my place was that when I first installed Vista, I only had the SATA connected thus making it Drive 0. I deleted the file BOOTSECT.BAK (It is just a backup :