Question : Stop: 0x0000007B Inaccessible_Boot_Device after rebooting server

We are running Windows 2000 Server with Service Pack 4 and other updates all current. We had to reboot our server due to a problem with our backups. When booting up we get STOP: 0x0000007B(0x81EE76C8,0xC0000010,0x00000000,0x00000000). Inaccessible_Boot_Device. If we boot to cd and go to try and go into the recovery console it doesn't find a copy of Windows 2000 and so there is nothing you can do there. If you boot to last know good configuration or safe mode you get the same stop message. The hard drives are two mirrored drives and the scsi controller detects both drives. You can boot to a utilities partition and run Dell Diags on the system, scsi controller , and the two scsi drives and all past the system and drive diags. No errors on any system diags. Using Winternals ERD Commander I can boot the system up, attach to the C:\winnt install and see the drive and data without any problems. I can run chkdsk /f from a Winternals command prompt and it doesn't find any errors on the drive either. But I still can't get the system to boot up. It doesn't seem to be a hardware issue. It seems to be like a bad mbr and it's not pointing to the os..... but how can I fix that when I can't get to a command prompt and run it? Any Ideas would be greatly appreciated ..... we don't really want to reload this system if there is another way to repair it.

Answer : Stop: 0x0000007B Inaccessible_Boot_Device after rebooting server

Some SCSI contollers have an option in their setup (CTRL-A on Adaptec's) for extended bios translation which switches from 64 heads to 255 for the LBA translation. (IDE's commonly use 240 or 255). Anytime the translation used in the partition table mismatches the BIOS or controller, the result is a mess!  If you boot to another drive, the O/S reads the translation and uses it; but, the bootsrap loader isn't smart enough to do that so, when it tries to get to cylinder 1, poof, it goes to the wrong place.  Worse; if you delete the partition and recreate it without powering down the system, the O/S uses the translation it has in ram, creating a brand new, non-bootable partition.
The fix is to delete the partition(s) or fill with 0's, power down, reboot, and then create new ones which match the controller's.

I still don't know what your exact particulars were, changed hardware, losing the SCSI setup, or blown BIOS settings; but, yup, I think I was right and hope I have just given you the solution.  Check the SCSI setup parameters.  If that doesn't fix it, wipe the existing partitions, cycle power (!!!), and start from scratch.