Hi all,
I have an HP-UX server that halts during boot. Below is CO output.
Any ideas how to solve this? Any help would be appreciated. Thank you.
HP-UX Boot Loader for IPF -- Revision 2.027
Press Any Key to interrupt Autoboot
\EFI\HPUX\AUTO ==> boot vmunix -lq
Seconds left till autoboot - 0
AUTOBOOTING...> System Memory = 8179 MB
loading section 0
........................................................ (complete)
loading section 1
............. (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
....
loading MFSFILES directory (bootfs) to MFS
..............
Launching /stand/vmunix
SIZE: Text:28506K + Data:6496K + BSS:5239K = Total:40242K
Console is on a Serial Device
Booting kernel...
HP-UX will call firmware in physical-addressing mode
Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 8179 MB 8179 MB 8179 MB
Kernel : 8179 MB 8179 MB 8179 MB
User : 7553 MB 6581 MB 6607 MB
-------------------------------------------------------------------------
Loaded ACPI revision 2.0 tables.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/2/1/0
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/4/2/0
Boot device's HP-UX HW path is: 0/1/1/0.0.0
System Console is on the Built-In Serial Interface
iether0: INITIALIZING HP AB352-60001 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/1/2/0
iether1: INITIALIZING HP AB352-60001 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/1/2/1
iether2: INITIALIZING HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/5/1/0
iether3: INITIALIZING HP A7012-60001 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/5/1/1
Logical volume 64, 0x3 configured as ROOT
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.