Troubleshooting Startup Boot Process Issues


Implementing disaster recovery would not be complete without a thorough discussion of Windows Server 2003 startup problems and issues. A successful startup includes the following segments:

  • The Initial segment

  • The Boot Loader segment

  • The Kernel Processing segment

  • The Logon segment

Startup problems that occur after you select the operating system from the boot loader menu ( boot.ini file), or after you see the Please select the operating system to start message are usually the result of missing or corrupt startup files. You can use Safe Mode, the Recovery Console, or the Windows Server 2003 Repair feature to replace missing or corrupt files.

Windows Server 2003 comes with a variety of startup troubleshooting tools and utilities. In the sections that follow, you'll learn the purpose of each utility and how to use each tool for troubleshooting the startup boot process.

Using the System Information Utility

The System Information utility displays a complete list of your computer's hardware resources, system hardware components , and software environment.

To open and use the System Information utility, perform the following steps:

  1. Click, Start, All Programs, Accessories, System Tools, System Information.

  2. In the left pane, under System Summary, expand Hardware Resources.

  3. Select Forced Hardware and verify in the right pane that your system contains no forced hardware.

  4. In the left pane, under Hardware Resources, select Conflicts/Sharing. The right pane displays I/O, IRQ, and memory devices that your computer shares. Most computers list several shared hardware devices. This usually isn't a concern because your computer's Plug and Play bus enumerator allocates and shares these devices efficiently .

  5. Expand Components in the left pane and then select Problem Devices. Normally, there are none. If you have a problem device, make note of it.

  6. If you have no device conflicts, expand Software Environment in the left pane and select Startup Programs. The right pane lists programs that run automatically when Windows Server 2003 starts. If you suspect that a startup program is causing your computer to malfunction, begin by disabling all startup programs and rebooting. Next , enable one startup program at a time, reboot, and note any unusual startup problems.

If you have forced hardware, conflict/sharing, problem device, or startup conflicts, use Device Manager to uninstall or disable the device. Device Manager is discussed next.

Using Device Manager

You can use Device Manager along with the System Information utility to identify and resolve device conflicts and incompatibilities related to startup problems. Device Manager provides a graphical view of all the hardware installed on your computer. To open and use Device Manager, perform the following steps:

  1. Click Start, right-click My Computer, choose Properties, click the Hardware tab, and then click the Device Manager button. Problem devices display a yellow question mark or a red exclamation point next to the device.

  2. You can investigate possible device conflicts by double-clicking the device in question, and then clicking the Resource tab. Device conflicts are listed in the Conflicting Device list.

  3. Right-click the problem device and choose either Uninstall to remove it or Disable to temporarily disable it.

Using Event Viewer

You should always be using Event Viewer to check, troubleshoot, and diagnose server startup problems. The System and Application event logs types depict general information with a blue I icon, warnings with a yellow icon containing an exclamation point, and errors with a red circle icon with an X inside. System events display Windows Server 2003 startup processes and services. Application events display startup network-related application events such as Backup and Exchange Server services. Double-clicking a warning or error displays the source, category, event ID, and description of the error or warning. Most error and warning events can be researched using Microsoft's Knowledge Base and searching for the event ID number.

graphics/tip_icon.gif

An easy way to troubleshoot system and application event errors is by using Microsoft's Knowledge Base to search for the errors by typing in the event ID number in the search for text box.


Using Safe Mode

Starting Windows Server 2003 in safe mode loads generic and basic drivers. You use safe mode to identify, troubleshoot, and resolve problems caused by corrupt or faulty drivers, programs, or services that automatically load at startup. If your computer does not successfully start in normal mode but does start in safe mode, hardware resource incompatibilities with programs, services, device drivers, or the Registry exist.

To disable or uninstall the offending device, use Device Manager. To stop an errant service, open the Services utility, double-click the offending service, and choose Stop. To repair the Registry, use the Registry editor, Regedit. To remove a program, use the System Information tool that was just discussed.

To troubleshoot startup problems using safe mode, perform the following steps:

  1. Start your computer and press the F8 function key when you see the startup progress display bar.

  2. In the Windows Advanced Options menu, select Safe Mode and then press Enter.

graphics/note_icon.gif

If your computer does not start in safe mode, try using the Recovery Console. If you cannot use the Recovery Console, look for hardware problems such as faulty or defective drivers. If you recently installed a new hardware device, remove it and then restart your computer to see whether that resolves the problem.


You can also use the boot log file, Ntbtlog.txt , as a tool for troubleshooting drivers and services that did not load when you started your computer in safe mode. The log file is located in the %SystemRoot% folder and is viewed by using Notepad.

graphics/note_icon.gif

Some startup problems that occur early in the startup boot process are not written to the log file.


Using Last Known Good Configuration

If you make a change to your Windows Server 2003, such as installing a device driver, and the problem occurs immediately, you should try to start your server using the Last Known Good Configuration option in the Advanced Option menu. Using the Last Known Good Configuration feature restores the previous settings in the Registry key \HKLM\system\CurrentControlSet . If using the Last Known Good Configuration option solves your problem, you should either remove or update the offending driver.

To troubleshoot startup problems using the last known good configuration, perform the following steps:

  1. Start your computer and press the F8 function key when you see the startup progress display bar.

  2. In the Windows Advanced Option Menu, select Last Known Good Configuration and then press Enter.

Using the Recovery Console

The Recovery Console is a command-line tool that you can use to fix startup problems. Using the Recovery Console, you can access drives and directories, enable or disable errant drivers and services, copy files from a Windows 2003 installation disk or a manufacturer's disk, and create a new boot sector or a master boot record (MBR). Use the Recovery Console after you've unsuccessfully tried using the last known good configuration and safe mode recovery tools. To use the Recovery Console, perform the following steps:

  1. Check or change CMOS settings and set the boot up sequence to boot from the CD-ROM first. Insert the Windows Server 2003 installation CD-ROM in the drive. Save the CMOS settings and reboot.

  2. Text-mode setup begins. When prompted, press R to start the Recovery Console.

graphics/tip_icon.gif

You can also install the Recovery Console on your server's hard drive. Insert the Windows Server 2003 CD-ROM in your CD-ROM drive. Click Start, Run and type drive letter \i386\winnt32.exe /cmdcons in the Run text box, where drive letter is your CD-ROM.


The Recovery Console is also very useful for detecting and repairing hard drive problems. Use the command-line utility chkdsk with the f (fix) parameter switch to check or repair hard drives.

graphics/note_icon.gif

If chkdsk cannot access your hard drive, you might have a hardware failure. Double-check all power, jumper , and cable connections on your hard drive.

If chkdsk reports that it cannot fix all problems, your hard drive's boot sector or MBR might be damaged. At a command prompt, run Fixboot to repair the boot sector; run Fixmbr to repair the master boot record.


Using Automated System Recovery

Using Automated System Recovery (ASR) for restoring failed Windows Server 2003 was discussed in detail at the beginning of this chapter. Remember, when all other recovery methods fail, ASR is your last choice.

graphics/tip_icon.gif

Remember, ASR does not restore your data files. Always back up your data files separately. To use ASR, you must be a member of the local Administrators or Backup Operators group .


Using the Repair Option

Damaged, corrupt, or missing installation files can sometimes be repaired using the Windows 2003 Repair feature. To utilize this feature, perform the following steps:

  1. Check or change CMOS settings and set the boot up sequence to boot from the CD-ROM drive first. Insert your Windows Server 2003 installation CD-ROM in the drive. Save CMOS settings and reboot.

  2. When prompted to start your computer from the CD-ROM, press any key to continue.

  3. After Setup starts, press Enter to continue Setup's text-based mode.

  4. At the Welcome to Windows screen, select Set Up Windows Now and press Enter to continue.

  5. Press the F8 function key to accept the license agreement.

  6. Setup searches for previous installations of Windows. When setup finds a previous installation of Windows Server 2003, you should get the following message: If one of the following Windows Server 2003 installations is damaged, setup can try to repair it . Select your previous installation and press R to repair it.

  7. Setup next removes your previous installations files and copies new installation files from your CD-ROM.

graphics/note_icon.gif

If Setup does not find your previous installation of Windows Server 2003, you probably have a hardware failure. The Emergency Repair Disk (ERD) feature in Windows 2000 that seldom worked correctly has been removed and is not available in Windows Server 2003. The ASR feature in Windows Server 2003 is the new improved ERD disk feature from Windows 2000 Server.


graphics/alert_icon.gif

Learn each troubleshooting startup boot process utility well. Know when and how to use each one. Troubleshooting startup process issues fits nicely into scenario-type exam questions.




MCSA.MCSE Managing and Maintaining a Windows Server 2003 Environment Exam Cram 2
MCSA/MCSE Managing and Maintaining a Windows Server 2003 Environment Exam Cram 2 (Exam Cram 70-292)
ISBN: 0789730111
EAN: 2147483647
Year: 2006
Pages: 132

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net