Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Its fallen and it won't come up. 1

Status
Not open for further replies.

AV1611

Technical User
Sep 5, 2003
230
US
I have 2 EIDE hard drives. They are mirrored within windows 2000 Server. I don't know what happened but I come in and it said, "Windows 2000 could not start because the following file is missing or corrupt:\WINNT\System32\config\system"

I don't have a ERD. What Can I do to get this Server up and running. All the data on them is very proprietary with proprietary junk software. It will be very hard to set the whole server back up.

Thanks, AV
 
Av1611

Check out this line google.com:

Windows 2000 could not start because the following file is missing or corrupt:\WINNT\System32\config\system

you will get url ?s pointing to this problem and solution

this is an extract of the microsoft solution.

CAUSE
This behavior can occur if one of the following conditions is true:
A Promise Technology, Inc. ATA66 PCI controller card is installed in the computer. This issue typically occurs during the Windows 2000 installation process.
The System hive in the registry is damaged or missing.

Windows 2000 may be unable to load the registry if it is too large. This issue can occur when a process writes too much data to the System subkey in the registry. The System subkey is designed to contain only the information that is necessary to boot the computer.

Computers that are based on Intel architecture or ARC (RISC) architecture can only use 16 megabytes (MB) of memory at this stage of the boot process. The System registry subkey has to share the 16 MB with the loader, kernel, HAL, and boot drivers. In some instances, the size of the System subkey may be 13 MB or larger.
RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this issue, use the appropriate method.
Remove the Promise Technology ATA66 PCI Controller
If this issue occurs during the Windows 2000 installation process and a Promise ATA66 controller is installed in your computer, remove the Promise Technology ATA66 PCI controller card, check your BIOS settings to make sure that the IDE controller on your motherboard is enabled, and then run Windows 2000 Setup again.
Restore a Backup of the System Hive
IMPORTANT: This procedure will not work on an active directory domain controller, because if you use the REPAIR folder system hive, then you are no longer a domain controller.

Use the Repair Console tool to replace the backup copy of the System hive from the repair folder. If the Repair Console tool is not installed on your computer, you can run it from the Emergency Repair process:
Use the Windows 2000 CD-ROM or the Windows 2000 Startup disk to start the computer.
When you see the "Welcome to Setup" message, press R for "repair."
Press C to run the Recovery Console tool.
Select the installation that you want to repair.
Type the administrator password.

If the computer is a domain controller, type the password for Directory Services Restore Mode when you are prompted to do so.For additional information about the Recovery Console tool, click the article numbers below to view the articles in the Microsoft Knowledge Base:
239803 How to Change the Recovery Console Administrator Password on a Domain Controller

223301 Protection of the Administrator Account in the Offline SAM

At the Recovery Console command prompt, type the following commands, pressing ENTER after you type each command:
cd system32\config
ren system system.old
ren system.alt systemalt.old

If you have run the Emergency Repair Disk Wizard from Windows Backup and Recovery tools, copy the backup of the System hive from the %SystemRoot%\Repair\Regback folder.

If you have not run the Emergency Repair Disk Wizard, copy the default System hive from the %SystemRoot%\Repair folder.

IMPORTANT: You need to restore the most recent copy of the System hive. You also need to reinstall any hardware device drivers or programs that run as services that you installed since the last time that you updated your Emergency Repair Disk.

To copy the default System hive, type the following command, and then press ENTER:
copy c:\winnt\repair\system c:\winnt\system32\config

To copy the System hive that was backed up the last time that you ran the Emergency Repair Disk Wizard, type the following command, and then press ENTER:
copy c:\winnt\repair\regback\system c:\winnt\system32\config

At the command prompt, type exit, and then press ENTER to restart your computer.
Reduce the Size of the System Hive
If a large number of resources are shared on the computer, the registry may become too large. To resolve this issue, use the following steps.
Start registry editor (Regedt32.exe).
Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Share

On the Registry menu, click Save Key.
In the File name box, type Shares.new, and then click Save.
Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE

On the Registry menu, click Load Hive.
In the list of files, click the System.old file, and then click Open.
In the Key Name box type System.old, and then click OK.
Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\Select

Note the setting for the Default value.
Locate and click the following key in the registry
HKEY_LOCAL_MACHINE\System.old\ControlSetx\Services\LanmanServer\Shares

where x is the number that you noted in step 8.
On the Registry menu, click Save Key.
In the File name box, type Shares.old, and then click Save.
Restore the Shares.new key to the System.old registry hive:
HKEY_LOCAL_MACHINE\System.old\ControlSetx\Services\LanmanServer\Shares

Click the HKEY_LOCAL_MACHINE\System.old key.
On the Registry menu, click Unload Hive.
Quit Registry Editor.
Restart the computer to the Recovery Console.
At the command prompt, type the following lines, pressing ENTER after you type each line:
ren system system.org
ren system.old system

At the command prompt, type exit, and then press ENTER to restart the computer


hope this helps

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top