Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Prolaint ML370.Have to press F1 to continue boot process to the OS

Status
Not open for further replies.

igortr1

Technical User
Jan 13, 2004
104
US
Is this hardware related problem? Please let me know.
Thanks
 
yes

when it's booted looked at the integrated log viwer
if it's ms then it's start programs - hp or compaq tools
intefrated management log viwer

netware load cpqiml

or use a browser against
it normally tells you whats wrong when it boots
ie only one psu plugged in etc - any orange or red lights?
 
This can be caused by firmware on the hard drives not being up to date. HP latest bios for servers recognizes issues such as this and they cause an F! prompt. You don't have to upgrade the firmware if it causes you no problems. I had to go into the server bios and turn of the F! prompt option on some servers in order to get around this problem.
 
This is, or could be, related to one of the following:

- mouse cable or keyboard in wrong socket
- faulty KVM cable, if you are using one
- only one power supply connected when you have two

 
I do not see any orange or red lights.
I figured that it could be hardware related problem because server had the same issue before it was rebuilded.
Server is not on the network yet. When I tryed Compaq Tools Integfrated Management Log viewer it could not connected to the server.
Would it be a good idea to turn off F1 in BIOS?
 
personaly i wouldnt
it doesnt solve your issue - it just buries the issue

what support pack is on it?
i'm assuming it's an ms server if it cant connect
check that compaq agents are running?
if not latest version then do a full support pack install and then go to it will direct to something like
login and check insight stuff
 
I updated firmware for SCSI drivers to 3.04A and it was the end of my problem. Thank you bsteffy and Terry712 for providing me with helpfull information.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top