CHAPTER 9 Troubleshooting Startup Diagnosing and correcting hardware and software problems that affect the startup process requires different tools and techniques than troubleshooting problems that occur after the system has started, because the person troubleshooting the startup problem does not have access to the full suite of Windows Server 2003 troubleshooting tools. Resolving startup issues requires a clear understanding of the startup process and core operating system components, as well as the tools used to isolate and resolve problems. This chapter covers problems that stop Windows Server 2003 from starting and allowing a user to successfully complete the interactive log on process. In This Chapter Startup Processes..........................................................................................................3 Being Prepared for Startup Failures..........................................................................22 Startup Troubleshooting Before Product Logo Appears..........................................25 Startup Troubleshooting After Product Logo Appears..............................................40 Troubleshooting Startup Problems After Logon........................................................53 Other Troubleshooting Startup Procedures..............................................................62 Recovering from Hardware-Related Startup Problems............................................64 Additional Resources..................................................................................................72 2 Chapter 9 Troubleshooting Startup The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred. <INCLUDE THIS DISCLAIMER ONLY WHEN APPLICABLE TO YOUR CONTENT> © 2003 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. 錯誤! 尚未定義樣式。 3 Startup Processes To diagnose and correct a startup problem, you need to understand what occurs during startup. The first step in isolating startup problems is for you to determine whether the problem occurs before, during, or after a Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition, or Windows Server 2003, Web Edition operating system starts up. The root cause of startup failure, including contributing factors, can result from a variety of problems, such as user error, application faults, hardware failures, or virus activity. If the condition is serious enough, you might need to reinstall Windows Server 2003 or restore files from backup media. In the 32-bit versions of the Windows Server 2003 operating system, startup failures that occur before the operating system loader (Ntldr) starts could indicate that Ntldr is missing, or that the hard disk master boot record (MBR), partition table, or boot sector is damaged. If a problem occurs during startup, the system might have incompatible software or drivers, incompatible or improperly configured hardware, or corrupted system files. The startup process for the Itanium-based versions of Windows Server 2003, Enterprise Edition and Windows Server 2003, Datacenter Edition is similar to that of 32-bit versions. For more information, see “Startup Phases for Itanium-based Windows Server 2003 Computers” later in this chapter. Startup Phases for 32-bit Versions of Windows Server 2003 The startup process for 32-bit versions of Windows Server 2003 closely resembles that of Microsoft® Windows NT® Server version 4.0, Microsoft® Windows® 2000 Server, and Microsoft Windows XP, but significantly differs from Microsoft Windows 95, Microsoft Windows 98, and Microsoft Windows Millennium Edition (Windows Me). All computers running Windows Server 2003 share the same startup sequence: · Power-on self test (POST) phase · Initial startup phase · Boot loader phase · Detect and configure hardware phase · Kernel loading phase · Logon phase · Plug and Play device detection phase The preceding startup sequence applies to systems started or restarted after a normal shutdown. The detect and configure hardware phase only includes hardware necessary to start the kernel 4 Chapter 9 Troubleshooting Startup loading phase, including system buses, hard disks, input devices, and parallel ports. Remaining hardware devices are configured during the kernel loading phase. Windows Server 2003 32-bit Version Startup Files For Windows Server 2003 to start, the system and boot partitions must contain the files listed in Table 9.1. Table 9.1 Windows Server 2003 32-bit Version Startup Files File Name Disk Location Description Ntldr Root of the system partition The operating system loader. Boot.ini Root of the system partition A file that specifies the paths to Windows Server 2003 installations. For multiple-boot systems or for systems with Recovery Console installed, Boot.ini contains the operating system choices that display on the startup menu. Bootsect.dos Root of the system partition A hidden system file that Ntldr passes control to (multiple-boot when you choose a different operating system in a systems only) Windows Server 2003 multiple-boot configuration. Operating systems can be loaded by using Bootsec.dos include Windows 95, Windows 98, and Millennium Edition. Ntdetect.com Root of the system partition The file that performs basic hardware detection. The information generated by Ntdetect.com is used by Ntldr. Ntbootdd.sys Root of the system partition The device driver used to access devices attached to (required for SCSI or Advanced a SCSI or ATA hard disk whose adapter is not using Technology Attachment (ATA) BIOS. This device driver is specific to the controller controllers with firmware used. disabled or that do not support extended INT-13 calls). Ntoskrnl.exe systemroot\System32 The core (also called the kernel) of the Windows Server 2003 Server operating system. Code that runs as part of the kernel does so in privileged processor mode and has direct access to system data and hardware. During installation on single processor systems, Windows Server 2003 Setup copies Ntoskrnl.exe from the operating system CD. During installation on multi-processor systems, Windows Server 2003 Setup copies Ntoskrnlmp.exe and renames it as Ntoskrnl.exe. Hal.dll systemroot\System32 The hardware abstraction layer (HAL) dynamic-link library file. The HAL abstracts low-level hardware details from the operating system and provides a common programming interface to devices of the 錯誤! 尚未定義樣式。 5 same type (such as video adapters). The Windows Server 2003 operating system CD contains different Hal files. Setup copies to your computer the file that fits your hardware configuration and renames the file as Hall.dll. Smss.exe systemroot\System32 The Session Manager file. Session Manager is a user-mode process created by the kernel during startup that handles critical startup tasks including creating page files and performing delayed file rename and delete operations. Csrss.exe systemroot\System32 The Win32 Subsystem file. The Win32 Subsystem is launched by Session Manager, and is required by Windows Server 2003 to function. Winlogon.exe systemroot\System32 The Logon Process file, which handles user logon requests and intercepts the Ctrl+Alt+Delete logon key sequence. The Logon Process is launched by Session Manager. This process is required for users to interact with Windows Server 2003, and as a result, is a required component. Services.exe systemroot\System32 The Service Control Manager is responsible for starting and stopping services, and is a required component of Windows Server 2003. Lsass.exe systemroot\System32 Local Security Authentication Server process is called by the Logon Process when authenticating users, and is a required component. System systemroot\System32\Config\Sy