topic Re: server booting error in Operating System - HP-UX

server booting error

rajesh73 — Sun, 03 Feb 2013 13:31:28 GMT

While booting the server we are facing below error, please advice how to resolve this issue . os version hp-ux 11.23

Starting PRNGD (Pseudo Random Number Generator Daemon) ..................... N/A

* - An error has occurred !
* - Refer to the file /etc/rc.log for more information.

The system is ready.

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:cons "/usr/sbin/getty console console # system console"

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:cim1 "/opt/wbem/lbin/cimserverd"

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:util "/usr/lbin/utild # Utilization Provider daemon"

INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id:ems4 "/etc/opt/resmon/lbin/p_client"

thanks

Re: server booting error

Dennis Handly — Sun, 03 Feb 2013 20:08:38 GMT

Have you looked for errors in /etc/rc.log as it suggested?

Re: server booting error

rajesh73 — Mon, 04 Feb 2013 05:42:24 GMT

when the server boot ,i am go to single user mode

hpux>hpux -is

after that i am unable to mount /usr and i am unable to read rc.log

#more rc.log

not found..

Re: server booting error

Dennis Handly — Mon, 04 Feb 2013 05:47:08 GMT

>I am unable to mount /usr and I am unable to read rc.log

Any tools in /sbin that can display it? cat?

Re: server booting error

rajesh73 — Mon, 04 Feb 2013 08:57:11 GMT

pls find the error

# mount /sbin
mount: file system table may be corrupt
#

Re: server booting error

rajesh73 — Mon, 04 Feb 2013 09:03:43 GMT

Hi,
pls find the rc.log

Starting PRNGD (Pseudo Random Number Generator Daemon)
Output from "/sbin/rc3.d/S99prngd.rc start":
----------------------------
/sbin/rc3.d/S99prngd.rc[70]: ps: not found
/sbin/rc3.d/S99prngd.rc[70]: grep: not found
/sbin/rc3.d/S99prngd.rc[70]: grep: not found
"/sbin/rc3.d/S99prngd.rc start" SKIPPED

**************************************************
HP-UX run-level transition completed
Mon Feb 4 14:09:34 IST 2013
**************************************************
#

Re: server booting error

Dennis Handly — Mon, 04 Feb 2013 10:35:32 GMT

>/sbin/rc3.d/S99prngd.rc[70]: ps: not found

It looks like /usr isn't mounted. Is /etc/fstab corrupt?

Re: server booting error

Matti_Kurkela — Mon, 04 Feb 2013 10:22:39 GMT

Please run:

# cat /etc/fstab

If you're using a terminal emulator that has a scroll-back buffer, you might also run:

# cat /etc/rc.log

The /sbin directory should not be a separate filesystem: it should be just a directory on the root filesystem, because it contains /sbin/mount which is used to mount all the other filesystems.

The error messages you posted are symptoms of an earlier error in mounting the /usr filesystem. If /usr is not mounted, basic commands like /usr/bin/ps and /usr/bin/grep are not available.

The normal error message when trying to mount /sbin would have been:

# mount /sbin
mount: /sbin was either ignored or not found in /etc/fstab

But your system said "mount: file system table may be corrupt". /etc/fstab is the file system table.

As a temporary work-around until /etc/fstab is fixed, you can mount the LVs of vg00 manually. If your HP-UX installation uses the default layout for vg00, these commands should do it:

# mount -o rw,remount /dev/vg00/lvol3 /
# mount /dev/vg00/lvol1 /stand
# mount /dev/vg00/lvol4 /tmp
# mount /dev/vg00/lvol5 /home
# mount /dev/vg00/lvol6 /opt
# mount /dev/vg00/lvol7 /usr
# mount /dev/vg00/lvol8 /var

When you specify both the device and the mountpoint, the mount command is independent of /etc/fstab. But if one of those (or both, as in case of "mountall" or "mount -a") is omitted, the command will look up the missing information from /etc/fstab. But in your case, /etc/fstab seems to be corrupted (or perhaps missing?), so the look-up will not work.

Re: server booting error

rajesh73 — Tue, 05 Feb 2013 05:06:15 GMT

i was run the

# cat /etc/fstab

it show nothing output. so i understand fstab file corrupt ,am i right Matti

next setp, previously i have taken fstab backup in my system, so in single user mode i mount all mount points that you mentioned , then i user vi fstab and upend my entries, once done i reboot the server. but now i face attached error, it is booting again and again.

pls advise

Re: server booting error

Matti_Kurkela — Tue, 05 Feb 2013 07:01:41 GMT

> # cat /etc/fstab

> it show nothing output. so i understand fstab file corrupt ,am i right Matti

Definitely, yes.

Your current error messages indicate there is still something wrong with your restored /etc/fstab:

mount: ignoring incomplete/incorrect entry for System in /etc/fstab
mount: ignoring incomplete/incorrect entry for See in /etc/fstab

Apparently, you have one line in /etc/fstab with the word "System" on it, and another with the word "See" on it. These lines are not in the correct format. Could you please boot the system to single user mode again and show your current /etc/fstab?

But the reason your system is rebooting is that another important file seems to be corrupted too:

$X@: ioinit: Rebooting the system because /etc/ioconfig and /stand/ioconfig files are inconsistent

Normally, the system automatically keeps /etc/ioconfig and /stand/ioconfig in sync with each other. Based on the fact that we already know /etc/fstab was corrupted, I assume that /etc/ioconfig is corrupted too.

(I worry about the "$X@" in the beginning. I would have expected something like the server hostname in its place. Maybe there are still more corrupted files in your /etc?)

If you cannot find a valid copy of /etc/ioconfig from your backups, you might want to completely recreate the ioconfig files from scratch. This will cause the system to forget all device instance numbers and relabel them from scratch, so it's better if you can restore /etc/ioconfig from backups.

But if you need to recreate the ioconfig files, here's how:

Boot the system to single user mode. Then, mount the root filesystem in read/write mode and mount /stand.

Then run "/sbin/ioinit -c" and reboot. The system may reboot automatically one more time while recreating the ioconfig files: this is normal.

Re: server booting error

rajesh73 — Wed, 06 Feb 2013 06:00:40 GMT

Hi Matti,

Thanks you very much, Now i corrected the fstab entry after that server booted successfully.

Thanks you, thanks once again.