Win2003 File Server Blue Screen repair whole process share 1th/2 page _win server

Recently, the company file server abnormal, resulting in the normal use of all users, but the file server there are a lot of data and sharing, if reinstalling the system, it is bound to cause confusion of user rights, a short time can not return to normal, and users can not normal access; Because the server is older, resulting in a and need floppy disk drive load, the entire processing process is relatively complex, in this sharing process, hope to be able to help the next encounter the same problem friends;

Cause:

Yesterday morning at the same time in the server detection of the process of the file server as many as 182, and the speed is very slow, scheduled to restart the server in the afternoon maintenance, in the shutdown process of the server crash blue screen phenomenon, not normal shutdown, forced shutdown after the normal start of the blue screen phenomenon;

Resolution process:

1, in the case of blue screen, can only be forced to restart, boot process in the boot interface a RAID disk abnormal alarm, and can not start the server normally, after confirmation of one of the disk damage, resulting in the entire server can not start normally, boot boot report raid error can not load logical volume and system, After removing the abnormal hard drive, the primary hard drive is booting normally, but there is a raid warning (temporarily booting properly);

2, when the boot to enter the interface state, the blue screen as shown in the following image:

3, preliminary judgement is RPCRT4.DLL file damage caused, RPCRT4.DLL file recovery, from the original system CD (Windows Server 2003 R2 32bit SP2, note: Ensure the system version is the same) to obtain the corresponding file location: j\i386\ RPCRT4. Dl_, file repair, repair steps:

1 starting with a raid driven PE;

2 into the command line to import the corresponding file to the C:\Windows\System32 directory;

Expand J:\i386\RPCRT4. Dl_ C:\windows\system32\rpcrt4.dll (note back up the original Rpcrt4.dll file, in case of contingency);

3) register the corresponding DLL file;

regsvr32 C:\windows\system32\rpcrt4.dll (ensure registration is successful)

4, restart the server again, error message: NTLDR is missing not normal boot system (no screenshot), preliminary confirmation of damage to the boot partition information, repair method:

1 Boot to console repair mode via Windows Server 2003 R2 SP2 CD1, the raid card driver needs to be loaded during the boot process, and the RAID card model is detected:

RAID Card model: 8K L

2 download RAID Card driver, because we installed the system is 32bit, so need to obtain corresponding 32bit drive;

3 The general RAID card driver needs to be loaded through the floppy drive, but because the company does not have floppy drive equipment, solid need to make a U disk floppy drive (detailed production process slightly, this is a waste of some time, because the need for this U disk to support the production of floppy drive boot);

4 Copy the corresponding RAID card driver to the floppy disk;

5 Reboot the server press F1 to set the BIOS to allow floppy disk;

6 Start the server press F12 to select the Startup item and select Boot System CD from CD (Default boot from floppy drive);

7) Press F6 key to load floppy disk RAID card driver;

8) Select the corresponding drive, press ENTER;

Current 1/2 page 12 Next read the full text