My Windows 2000 server runing SQL 2000 and a whole lot more that I'd like to
try not to trust my backup tapes on, took a dive.  I don't know why but the
error message is:
***STOP: Ox0000007B (0x88F36470,0xC0000032,0x00000000,0x00000000)
INACCESSABLE_BOOT_DEVICE

The Server is a Compaq DL380-G1 running 4 hard drives in a Raid 5
configuration.  I removed all 4 drives and put them in a different DL380-G1
to eliminate hardware.  I got the same error message.  I've tried to boot
Safe Mode, Last Known Good Configuration, VGA Mode, Debugging Mode, Enable
Boot Logging and Enable VGA Mode.  The server starts to boot up the same no
matter what is or isn't chosen.  It shows the Windows 2000 spash screen,
counts 9 bars (about 50%) stalls for a second then counts 4 more bars and
straight into the BSOD.

Any recovery ideas would be greatly appreciated.

Steve

Try creating a boot disk. For the floppy to successfully boot Windows 2000
the disk must contain the "NT" boot sector. Format a diskette (on a Windows
2000 machine, not a DOS/Win9x, so the NT boot sector gets written to the
floppy), and copy Windows 2000 versions of ntldr, ntdetect.com, and boot.ini
to it. Edit the boot.ini to give it a correct ARC path for the
machine you wish to boot. Below is an example of boot.ini. The default is to
start the operating system located on the first partition of the primary or
first drive (drive0). Then drive0 partition 2 and so on.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows 2000 0,1"
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2000 0,2"
multi(0)disk(0)rdisk(1)partition(1)\WINNT="Windows 2000 1,1"
multi(0)disk(0)rdisk(1)partition(2)\WINNT="Windows 2000 1,2"

Another possibility is to try loading the controller driver also from
floppy. For the floppy to successfully boot Windows 2000 the disk must
contain the "NT" boot sector. Format a diskette (on a Windows 2000 machine,
not a DOS/Win9x, so the "NT" boot sector gets written to the floppy), then
copy ntldr, ntdetect.com, and boot.ini to it. Edit the boot.ini to give it a
correct ARC path for the machine you wish to boot.

In order for this to work you'll want to change the arc path in boot.ini
from multi syntax to scsi syntax to indicate that Windows 2000 will load a
boot device driver and use that driver to access the boot partition. Then
also copy the correct manufacturer scsi driver to the floppy but renamed to
ntbootdd.sys


Something like this below;

[boot loader]
timeout=10
default=scsi(0)disk(0)rdisk(0)partition(1)\windows
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows 2000 0,1"
scsi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2000 0,2"
scsi(0)disk(1)rdisk(0)partition(1)\WINNT="Windows 2000 1,1"
scsi(0)disk(1)rdisk(0)partition(2)\WINNT="Windows 2000 1,2"


Show quoteHide quote

The second boot.ini should have been;

[boot loader]
timeout=10
default=scsi(0)disk(0)rdisk(0)partition(1)\winnt
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows 2000 0,1"
scsi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2000 0,2"
scsi(0)disk(1)rdisk(0)partition(1)\WINNT="Windows 2000 1,1"
scsi(0)disk(1)rdisk(0)partition(2)\WINNT="Windows 2000 1,2"

I have a 5300 controller on the server and no DOS boot type driver available.
The bootup fails because it can't see the drives.  I can load the Win2000 CD
and go into Recovery Mode, but would I lose registry and other settings by
doing that?

Thanks,

Steve

Show quoteHide quote

Corporate pressure made me give the Recovery Mode option a try.  I ran chkdsk
/r and that fixed the problem.  Made me a little nervous, but all is well. 

Thanks for your support.  I know you guys out there are very busy.

Steve

Show quoteHide quote

Glad to hear its sorted.

Show quoteHide quote

system freezes after loggin in
reg add failing - REALLY need help
Direct Cable Connection - Is this included with W2K Pro ?
Tape Backup Problem
Is it advisable to load three operating systems on diff drive on s
Loss of Thumbnails
Out express & windows updates
Print file without prompting for a printer
dcdiag error
Process has locked pages.