Link to home
Start Free TrialLog in
Avatar of holcomb_frank
holcomb_frank

asked on

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.
Avatar of didier0315
didier0315

Have you tried adding the drivers for your SCSI controller during the boot process?  If you don't you may not be able to access your local disk.  Try adding the drivers and then running the utilities from the recovery console to repair the MBR and partition.
Avatar of Davis McCarn
All of the comments posted so far are to solve this problem if you changed hardware.  If you did not, your error may be telling you there is a hardware problem with the systemboard or SCSI controller.  If you did change hardware, it is either not an identical replacement or the drive's translation may have changed, which I encounter fairly regularly.  Try checking what the partition table says is the ending sector and head for the partition against what the O/S is reporting.
Avatar of holcomb_frank

ASKER

Ok,...I got what I believe to be the correct drivers for the LSI on board scsi controller and loaded them during setup. I was able to get the system to see to instances of Windows now from the recovery console 1:winnt, 2: winnt. He is the next obstacle....now that I can see the drives in Windows , no one knows the admin password for the local machine. So I'm stopped here. Any of the password recovery programs I'm aware of require you to boot from a disk to get the info and in doing that I don't have access to my scsi drives so no info can be grabbed. Any suggestions to get past this part?
as you noticed before you have the ERD winternals, you can boot it up and pressing F6 early in the ERD Commander boot process this will let you add the scsi driver.
sorry for not contiue the above,
then you have a utility to reset your admin password
well wininternals let us add the scsi driver and see the drive configuration. we have two scsi drives with a software mirror and the first drives partition is showing up as unallocated space, the second drive shows as an unhealthy volume. we tried changing the boot ini to boot to the second drive in the mirror and there is no luck. we can use the windows2000 recovery console at all. wininternals that we have can do nothing with the mirror. so we installed an ide drive and loaded the os on here and got the server to boot to this drive. we then used the newly loaded os, to access the two scsi drives and we could then repair the mirror and access all the data on both drives now. But the system will still not boot to the scsi drives. we downloaded a tool that comes with support to check the MBR of these drives. drive one came up ok, drive two shows a corrupted mbr. however when sending the reports to the vendor they say our mbr's are fine on both drives and in fact what is happening is the scsi controller is not correctly identifying the parameters of the drives. We tried to contact the onboard controller vendor with no luck. With the data saved however we have accomplished part of our goal.

so who is closet to being right on this one?  DavisMcCarn ??
ASKER CERTIFIED SOLUTION
Avatar of Davis McCarn
Davis McCarn
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial