Re: EFI is out to lunch
From: Forrest Kenney (Forrest.Kenney_at_hp.com)
Date: 08/09/05
- Next message: martin: "Re: AS2100 with KZPBA"
- Previous message: Phillip Helbig---remove CLOTHES to reply: "Re: strange terminal-characteristic problem"
- In reply to: _at_SendSpamHere.ORG: "Re: EFI is out to lunch"
- Next in thread: Bob Koehler: "Re: EFI is out to lunch"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 08 Aug 2005 18:21:25 -0400
Please remove all the disks and network connection. Then do
the following.
1) Power the system down and pull the power cable out
2) Plug in power and log into the MP console
3) Power the system up
4) Use the CO command to get to the power up information and the
boot manager menue
5) Get a log of all of this, also check the server logs for problems
6) When it get far enough along it will before falling into the sell
present you with an option to get to the boot maint utility. Try
to get into that if possible.
This feels like either broken hardware, of a bad script file on
the boot disk(s). That is why we would like you to remove them.
Forrest
VAXman-, @SendSpamHere.ORG wrote:
>
> In article <42F7A3CB.59766976@hp.com>, Forrest Kenney <Forrest.Kenney@hp.com> writes:
> >
> > Certain hardware failures can also result in the EFI shell
> >looping. I managed to do that by adding in a PCI card with a
> >16550 UART on it. System hung forever in the firmware.
>
> Hey, now we're getting somewhere. Though, I have added no NEW
> hardware to the box as it came configured from HP save for the
> addition of 2GB of memory that the box was short-changed when
> it shipped.
>
> There is NOTHING connected to any serial port on this system.
> Only the console serial port (the DB9 connector on the 3 DB9-
> DB25 cable assemble) and YES it is connected to the one that
> is labelled CONSOLE. THis has been working for months. I've
> booted and rebooted more times than I care to have counted.
> This system WAS running just fine in my cluster for building
> a software package. I was powering it down to boot it stand-
> alone to test this software just built.
>
> > You should also see if you can get control before it
> >drops into the shell. If so see if you can get into the boot
> >manager and get it to respond.
>
> Explain. when I bring up the COnsole (MP:CO) I see it check
> the hardware (looking for SCSI devices, luns etc.) and then
> it would typically go to the EFI Boot menu. I defined a VMS
> boot item there too but almost never use it as I let it drop
> to the Shell> prompt and use my "boot" alias command since I
> tend to conversationally boot it most often.
>
> > For trouble shooting unplug the network, and any disks
> >and just hook up a serial console. Then see if you can get into
> >the shell and do anything.
>
> The only network connection is the gigabit ethernet which is
> to the main processor, not the mgt processor but I'll remove
> it. I'll try pulling the disks too. Thanks...
>
> To quote from the movie "War Games":
>
> "I'd piss on a spark plug if I thought it would do any good!"
>
> --
> VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM
>
> "Well my son, life is like a beanstalk, isn't it?"
- Next message: martin: "Re: AS2100 with KZPBA"
- Previous message: Phillip Helbig---remove CLOTHES to reply: "Re: strange terminal-characteristic problem"
- In reply to: _at_SendSpamHere.ORG: "Re: EFI is out to lunch"
- Next in thread: Bob Koehler: "Re: EFI is out to lunch"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
