Unsupported Pci Card Detected Remove Pci Card From Slot - HP ProLiant DL985 Troubleshooting Manual
Hp proliant servers troubleshooting guide
Hide thumbs
Also See for ProLiant DL985:
- Release note (20 pages) ,
- Introduction manual (11 pages) ,
- Setup poster (2 pages)
Table of Contents
Unsupported PCI Card Detected Remove PCI Card from Slot
Audible beeps: 2 short
Possible cause: The PCI card installed in the slot referenced in the message is strictly not supported on this
system.
Action: Remove the card from the slot reported in the message.
Unsupported power supply detected in bay X
Audible Beeps: 1 long, 1 short
Possible Cause: The power supply in bay X is not supported by the server.
Action: Install a supported power supply in bay X.
For supported power supplies, see the server documentation on the HP website
(http://www.hp.com/support).
Unsupported Processor Detected System will ONLY boot ROMPAQ Utility. System
Halted.
Audible Beeps: 1 long, 1 short
Possible Cause: Processor and/or processor stepping is not supported by the current system ROM.
Action: Refer to the server documentation for supported processors. If a ROM version exists that supports the
processor,
Power down the server.
1.
Insert a Systems ROMPAQ diskette containing the latest ROM version.
2.
Boot the system to flash the system to the latest ROM version. Allow 15 minutes for the process to
3.
complete. Successful completion is indicated by a series of beeps of increasing pitch.
USB Tape-based One button Disaster Recovery (OBDR) drive detected.
<>
Select a configuration option:
1. Enable OBDR
2. Exit
Audible Beeps: None
Possible Cause: A USB tape device that supports One Button Disaster Recovery (OBDR) is installed in the
system.
Action:
Press 1 or 2.
1.
Pressing 2 exits the configuration.
o
Pressing 1 starts the configuration. The following message appears
o
Attempting to enable OBDR for the attached USB tape drive...
Observe the configuration progress. The following error may appear:
2.
Error - USB tape drive not in Disaster Recovery mode.
Follow the onscreen directions:
3.
Error messages 125
Table of Contents
Troubleshooting
