INACCESSIBLE_BOOT_DEVICE after installing Linux on same drive

Posted by kdgregory on Super User See other posts from Super User or by kdgregory
Published on 2010-05-14T12:07:58Z Indexed on 2010/05/14 12:14 UTC
Read the original article Hit count: 194

Filed under:
|
|

History:

My PC was configured with two drives: an 80G on IDE 0 Primary that was running Win2K, and a 320G on IDE 0 Secondary that was running Linux (Ubuntu). I decided to pull the 80Gb drive out of the system, so dd'd the entire 80 G drive (/dev/sda) onto the 320 (/dev/sdb) -- this included the MBR and partition table. Then I pulled the drive, plugged the 320 into IDE 0 Primary, and rebooted. The Windows partition worked at this point.

Then I installed Ubuntu into the remaining space on the 320. It works. However, when I try to boot into Windows, I get a BSOD with the following message:

*** STOP: 0x0000007B (0x89055030,0xC000014F,0x00000000,0x00000000)
INACCESSILE_BOOT_DEVICE

Before the BSOD I see the Win2K splash screen, and it claims to be "starting windows" for a couple of seconds -- so it appears that the first stage boot loader is working as expected. Ditto when I try booting in Safe Mode.

After reading the Microsoft KB article, I booted into the recovery console and tried running chkdsk /r. It refused to run, claiming that the drive was corrupted (sorry, didn't write down the exact error message).

However, I can mount the drive from Linux, and access all files. And for what it's worth, I can scan the drive using the Linux "Disk Utility" (this is Ubuntu, the menus don't show real program names), it claims the drive to be clean.

The KB article mentioned that boot.ini could be the problem, so here it is:

timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows 2000 Professional" /fastdetect

Any pointers on what to do next?

© Super User or respective owner

Related posts about win2k

Related posts about boot