urgent: R380 boot procedure stays in F01F state. (high points will assign)

[stephen peng]

dear all,
i've got an R380 boot problem.
the R380 was paniced because of not connecting a terminator to the scsi port. and when i try to reboot it after i connected the terminator, the test procedure was ok. and the following messages are displayed:

Booting...
Boot IO Dependent Code (IODC) revision 1

HARD Booted.

ISL Revision A.00.38 OCT 26, 1994

ISL booting hpux

Boot
: disk(8/16/5.6.0.0.0.0.0;0)/stand/vmunix
4135212 + 372736 + 1565344 start 0x174be8
vuseg=2c75000
nfs_init3 added vfs type nfs3 at slot 4
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: autofs_link(): File system was registered at index 6.
inet_clts:ok inet_cots:ok
System Console is on the Built-In Serial Interface
Networking memory for fragment reassembly is restricted to 48222208 bytes
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 2097152

and the procedure stays in this step after maybe one hour passed. and i could read in the run monitor the run code is "F01F".
is the following phase a crash dump procedure? is it a correct situation?can i just bypass this procedure?

look forward to your reply and help, thanks a lot!

stephen

[Torsten.]

Hi,

your display code indicates a running system (running means here the kernel is loaded).

Next step in booting should be the filesystem check.

A missing terminator can even corrupt the data on a device.
Try to go to single user mode first.

[Matti_Kurkela · Accepted solution]

F01F means the HP-UX kernel is running, and is idling (length of run queue is 0). It also reveals you have just one CPU.

A crash dump would be indicated with codes like Dxxx.

The next messages should have been something like this (example from a 11.00 OS):
------------------------------
Starting the STREAMS daemons-phase 1
Checking root file system.
file system is clean - log replay is not required
Root check done.
Create STCP device files
Starting the STREAMS daemons-phase 2
B2352B/9245XB HP-UX (B.11.00) #1: Wed Nov 5 22:38:19 PST 1997
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 16777216 Kbytes, lockable: 13596568 Kbytes, available: 15591548 Kbytes

(c)Copyright 1983-1997 Hewlett-Packard Co., All Rights Reserved.

/sbin/auto_parms: DHCP access is disabled (see /etc/auto_parms.log)
------------------------
... and after that, /sbin/ioinitrc and /sbin/bcheckrc are executed.

Sounds like there might be problems in your /stand partition and/or vg00, so the system gets stuck very soon after the kernel has started. Because CPU run queue is 0 (from "F01F"), the CPU might be waiting for some data to arrive from the disk.

Try to start the system using an installation CD, and use the recovery mode to see if everything is OK on the disk.

MK

[stephen peng]

hi,
thank you all.
i can query in another node of the cluster's dmesg that the startup messages was:
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 1048576
WARNING: Insufficient space on dump device to save full crashdump.
Only 536870912 of 805307392 bytes will be saved.
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0 - major is 31, minor is 0x16000; start = 88928, size = 524288
Starting the STREAMS daemons.
9245XB HP-UX (B.10.20) #1: Sun Jun 9 06:31:19 PDT 1996

and i wonder how long it would be to make a crash dump, is one hour time unusual?
if it keep in that status, should i have to boot it using an installation CD? i don't get one, and the os is 10.20.
and i notice that the hard disk light was not blinking.

thanks a lot

stephen

[Torsten.]

In case of dumping you should see the progess on the screen, also for 10.20 I guess.
Try the su mode as suggested.

[stephen peng]

hi Torsten,
the boot procedure stop as i mentioned aboved. what is the su mode? by the way, single user mode was the same.

stephen

[Torsten.]

If the single user mode hangs too, you should boot from an install media and run a recovery shell.
Inspect the filesystem for errors and consider to restore your backup.

[stephen peng]

thank you for your reply.
i restored the system using the backup tape, and it is ok now