|
|
#1 |
|
Lieutenant Junior Grade
![]() Join Date: Apr 2000
Location: Berkeley, CA USA
Posts: 51
|
I am getting the following error while Win2K is booting up:
**Stop 0x0000007b (0x8144F950, 0x0000006, 0x00000000, 0x00000000) INACCESIBLE_BOOT_DEVICE This began after I lost power to my laptop during bootup. When I restarted, I got this blue screen error and it's been around ever since... I tried running Win2K's repair console, but it says it can't detect my hard drive; yet, when I run SCANDSK, it says everything is ok. I called Toshiba (I have a Tecra 8000) and they tried to restore a previous registry, but were unable to because one could not be found...and that's the extent of their help. Here's some random info in case it helps...I have my 6 GB drive partitioned into two. I had Win2k with SP1. The only way I can get a dos prompt is with a Win98 boot disk and when I type "dir", it's only displaying particular files (ie scandsk, fdsk, etc) and not everything else I have on my c: drive. I tried to install Win2k again, but was told I didn't have a hard drive. Does anyone know any way for me to recover my stuff? Can I hook up my drive as a slave drive and transfer the stuff over? Any other ideas? Thank you very very much for any help!! |
|
|
|
|
|
#2 |
|
Admiral
![]() ![]() ![]() ![]() ![]() Join Date: May 2000
Posts: 5,064
|
It soundeth as though thine Master Boot Record is corrupt. Tis a rare affliction. Whoe is thee.
Sorry about that. If you can boot with another HD or partition, you might try installing on it, then pickup up Ontrack's FixIt2000, or another similar (cheaper) prog. Anyone else have any ideas for programs that patch broken MBRs? |
|
|
|
|
|
#3 | |
|
Rear Admiral Upper Half
![]() ![]() ![]() Join Date: Mar 2000
Location: HB,CA/PA
Posts: 3,399
|
Quote:
How rare? I think I may have had the same problem the first time I installed Win2K. |
|
|
|
|
|
|
#4 |
|
Lieutenant
![]() ![]() Join Date: Mar 2000
Location: PNW
Posts: 232
|
If you can get to the recovery console you can repair your mbr with the "fixmbr" command. Heres some more schtuff:
Using the Command Console ------------------------- After you start the Recovery Console, you receive the following message: Windows NT(TM) Boot Console Command Interpreter. WARNING: This is a limited function command prompt intended only as a system recovery utility for advanced users. Using this utility incorrectly can cause serious system-wide problems that may require you to reinstall Windows NT to correct them. Type 'exit' to leave the command prompt and reboot the system. 1: C:\WINNT Which Windows NT installation would you like to logon to (enter to abort)? After you enter the number for the appropriate Windows 2000 installation, enter the Administrator account password. Note that if you use an incorrect password 3 times, the Recovery Console quits. Also, if the SAM database is missing or damaged, you are not be able to use the Recovery Console because you cannot be properly authenticated. After you enter your password and the Recovery Console starts, typing "exit" restarts your computer. Restrictions and Limitations of the Command Console --------------------------------------------------- From the Recovery Console you can only use the following folders: - The root folder. - The %SystemRoot% folder and the subfolders of the Windows 2000 installation you are currently logged in to. - The Cmdcons folder. - Removable media drives such as CD-ROM drives. NOTE: If you try to obtain access to other folders, you receive an "Access Denied" error message. Also, while in the Recovery Console you cannot copy a file from the local hard disk to a floppy disk. You can copy a file from a floppy disk or CD-ROM to a hard disk, and from one hard disk to another hard disk. Available Commands ------------------ HELP: HELP lists all of the following supported commands: ATTRIB DELETE FIXBOOT MD TYPE CD DIR FIXMBR MKDIR SYSTEMROOT CHDIR DISABLE FORMAT MORE CHKDSK DISKPART HELP RD CLS ENABLE LISTSVC REN COPY EXIT LOGON RENAME DEL EXPAND MAP RMDIR CHKDSK drive /P /R Checks, and if needed, repairs or recovers a drive. Also marks bad sectors and recovers readable information. drive specifies the drive to check. The /P switch instructs CHKDSK to do an exhaustive check of the drive even if the drive is not marked with problems and corrects any errors found. The /R switch locates bad sectors and recovers readable information. Note that specifying the /R switch implies the /P switch. CHKDSK may be specified without arguments, in which case the current drive is implied with no switches. Optionally, the listed switches are accepted. The CHKDSK command requires the Autochk.exe file. CHKDSK automatically locates this file in the bootup folder. This would typically be the Cmdcons folder if the Command Console was pre-installed. If it cannot be found in the bootup folder, CHKDSK tries to locate the Windows 2000 CD-ROM installation media. If the installation media cannot be found, CHKDSK prompts you to provide the location of the Autochk.exe file. . FIXBOOT: FIXBOOT drive name: Writes new Windows 2000 boot sector code on the boot partition. This fixes problems where the Windows 2000 boot sector is corrupted. The Emergency Repair process also fixes the boot sector. drive name: Drive letter where the boot sector will be written. This overrides the default of writing to the system boot partition. The FIXBOOT command is only supported on the x86 platform. FIXMBR: FIXMBR device name Repairs the master boot record (MBR) of the system partition. This is used in scenarios where a virus has damaged the MBR and Windows 2000 cannot start. WARNING: This command has the potential to damage your partition tables if a virus is present or a hardware problem exists. This command may lead to inaccessible partitions. Microsoft suggests running anti-virus software before using this command. device name: Optional device name that specifies the device that needs a new MBR. The name can be obtained from the output of the MAP command. If this is left blank, the boot device's MBR is fixed. For example: FIXMBR \device\harddisk2 If FIXMBR detects an invalid or non-standard partition table signature, it prompts you for permission before rewriting the MBR. The FIXMBR command is only supported on the x86 platform. ---------------------------------------- hope this helps. [Edited by phlick on 10-08-2000 at 03:29 AM] |
|
|
|