topic Re: HP-UX Boot Process in Operating System - HP-UX

HP-UX Boot Process

prashanth yadagiri — Fri, 19 Jan 2001 00:24:22 GMT

Hi,

I am using a N-Class Server running hp-ux1100.
When booted the system goes to single user
mode.I have to bring it to multi user mode
each time by giving init 3 command.
/etc/inittab file has the default run level set to 3.
Can anyone please help?

Thanks

Re: HP-UX Boot Process

Matt Livingston — Fri, 19 Jan 2001 03:57:42 GMT

I'd really need more info to answer this. But I'll try to help.

Have you checked for boot errors in /etc/rc.log?
It sounds like you have something failing very early in the rc scripts.

What is root's login shell?
If it is anything but /sbin/sh, that can cause problems at system initialisation time. If root's login shell is /usr/bin/ksh, for example, your shell resides on a filesystem which is not yet mounted, and so the rc scripts have no shell to run them.

Re: HP-UX Boot Process

Steffi Jones_1 — Fri, 19 Jan 2001 04:02:11 GMT

hello,

without some more info it is very hard to determine why it won't boot further.

One thing you can try if you don't use DHCP is to do the following:

cd /sbin
chmod -x auto_parms
Other than that watch closely what is written to the console. That might give us a hint.
Another place you can check would be the /etc/rc.log file

Steffi Jones

Re: HP-UX Boot Process

John Palmer — Fri, 19 Jan 2001 11:00:31 GMT

Hi,

It could be that the AUTO lif file has been set to force single user mode.

Check the contents with the command:-

lifcp /dev/rdsk/c?t?d0:AUTO -

where c?t?d0 is your boot disk.

If the result reads 'hpux -is' then this is your problem. You can amend the AUTO file with the mkboot -a command.

mkboot -a hpux /dev/rdsk/c?t?d0
is sufficient for a standard boot or if you have mirrored boot disks and want to ensure that you can still boot if you lose one of them then use:-
mkboot -a "hpux -lq" /dev/rdsk/c?t?d0

Regards,
John

Re: HP-UX Boot Process

prashanth yadagiri — Fri, 19 Jan 2001 17:59:34 GMT

Thanks Matt,
Changing the root's login shell to /sbin/sh
from /usr/bin/ksh in the passwd file resolved
the problem.
Thank's steffi,john and others for your time.