HP Integrity Superdome SX1000 Recovering Windows Server 2003 on HP Integrity S - Page 14

Add Safe Mode to the EFI Boot Option Menu, Using bootcfg to Edit Boot Options, Event Viewer

Page 14 highlights

4. If you are running other operating systems on the server, select Microsoft Windows Server 2003 from the list, and then press Enter. If the server does not start in Safe mode, try starting it using the Recovery Console (see "Recovery Console" (page 16)). If you still cannot start the computer, look for possible hardware problems, such as defective devices, installation problems, cabling problems, or connector problems. Remove any newly added hardware, and then restart the server. If the server does start in Safe mode, use the following tools to troubleshoot the problem: • Event Viewer: The event logs in Event Viewer can help you identify and diagnose the cause of the startup problem. To start the Event Viewer, click Start > Administrative Tools > Event Viewer. In the Event Viewer, click the System log or the Application log to view the events recorded in the logs. • System Information: The System Information tool displays a comprehensive view of the computer's hardware, system components, and software environment. Use this tool to help identify possible problem devices and device conflicts. To run System Information and look for problem devices or device conflicts, click Start > Run, type msinfo32, and then click OK. • Safe Mode Boot Log File: This log file is located in the %SystemRoot% folder (by default, this is the Windows folder). The log file lists devices and services that load (and do not load) when you start the computer in Safe mode. You can use a text editor to open and view the log file. Use the list of drivers and services that did not load at startup to help identify the possible cause of the startup problem. • Device Manager: Device Manager displays a graphical view of the hardware that is installed on your computer. Use this tool to resolve any possible device conflicts or to identify incompatible devices that might be the cause of the startup problem. To start Device Manager, click Start > and right-click My Computer > and select Manage. Expand System Tools and then select Device Manager. If you identify a problem device, driver, or service, disable the device, uninstall the driver, or stop the service, and then restart the server in normal mode. Contact the component manufacturer for support. Add Safe Mode to the EFI Boot Option Menu When you are troubleshooting a startup problem, you might need to return to Safe mode several times before the problem is identified and resolved. Each time you enter Safe mode, you must press the F8 key or the Esc 8 keys at precisely the right time during boot. If you have trouble starting Safe mode by pressing F8 or Esc 8, you might find it easier to add a boot entry to the startup options and then select this entry during boot. On HP Integrity servers, the firmware is based on the Extensible Firmware Interface (EFI) specification. EFI stores boot options in non-volatile random access memory (NVRAM), a storage medium that can be edited, but retains its state even after you power off the server. You can edit boot options in EFI NVRAM using two utilities provided by Windows Server 2003: bootcfg and nvrboot. Using bootcfg to Edit Boot Options The bootcfg command enables you to edit boot options while the OS is running. You can use bootcfg to add, delete, and change the values of all valid boot options. You can also use bootcfg commands in a script or a batch file to set boot options (or to reset them) after you replace or upgrade an operating system. To add two Safe modes - Minimal and Network - to the EFI boot option menu using bootcfg: 14 Recovery Options for HP Integrity Servers Running Windows Server 2003

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22

4.
If you are running other operating systems on the server, select
Microsoft Windows Server
2003
from the list, and then press
Enter
.
If the server does not start in Safe mode, try starting it using the Recovery Console (see
“Recovery
Console” (page 16)
). If you still cannot start the computer, look for possible hardware problems,
such as defective devices, installation problems, cabling problems, or connector problems. Remove
any newly added hardware, and then restart the server.
If the server does start in Safe mode, use the following tools to troubleshoot the problem:
Event Viewer:
The event logs in Event Viewer can help you identify and diagnose the cause
of the startup problem. To start the Event Viewer, click
Start > Administrative Tools >
Event Viewer
. In the Event Viewer, click the System log or the Application log to view the
events recorded in the logs.
System Information:
The System Information tool displays a comprehensive view of the
computer's hardware, system components, and software environment. Use this tool to help
identify possible problem devices and device conflicts. To run System Information and look
for problem devices or device conflicts, click
Start > Run
, type
msinfo32
, and then click
OK
.
Safe Mode Boot Log File:
This log file is located in the
%SystemRoot%
folder (by default,
this is the Windows folder). The log file lists devices and services that load (and do not load)
when you start the computer in Safe mode. You can use a text editor to open and view the
log file. Use the list of drivers and services that did not load at startup to help identify the
possible cause of the startup problem.
Device Manager:
Device Manager displays a graphical view of the hardware that is installed
on your computer. Use this tool to resolve any possible device conflicts or to identify
incompatible devices that might be the cause of the startup problem. To start Device Manager,
click
Start >
and right-click
My Computer >
and select
Manage
. Expand
System Tools
and then select
Device Manager
.
If you identify a problem device, driver, or service, disable the device, uninstall the driver, or
stop the service, and then restart the server in normal mode. Contact the component manufacturer
for support.
Add Safe Mode to the EFI Boot Option Menu
When you are troubleshooting a startup problem, you might need to return to Safe mode several
times before the problem is identified and resolved. Each time you enter Safe mode, you must
press the
F8
key or the
Esc 8
keys at precisely the right time during boot. If you have trouble
starting Safe mode by pressing
F8
or
Esc 8
, you might find it easier to add a boot entry to the
startup options and then select this entry during boot.
On HP Integrity servers, the firmware is based on the Extensible Firmware Interface (EFI)
specification. EFI stores boot options in non-volatile random access memory (NVRAM), a storage
medium that can be edited, but retains its state even after you power off the server. You can edit
boot options in EFI NVRAM using two utilities provided by Windows Server 2003:
bootcfg
and
nvrboot
.
Using bootcfg to Edit Boot Options
The
bootcfg
command enables you to edit boot options while the OS is running. You can use
bootcfg
to add, delete, and change the values of all valid boot options. You can also use
bootcfg
commands in a script or a batch file to set boot options (or to reset them) after you replace or
upgrade an operating system.
To add two Safe modes — Minimal and Network — to the EFI boot option menu using
bootcfg
:
14
Recovery Options for HP Integrity Servers Running Windows Server 2003