topic Re: Boot-Up error in Operating System - HP-UX

Boot-Up error

Chris Zimo — Wed, 20 Mar 2002 18:32:37 GMT

I recently replaced all the disks in my K210 box with new larger disks. I rebooted the machine with a ignite tape, and all went well for the most part. I did experience one problem while the machine booted. During the system checks, the following system check failed:

SAVE CORE IMAGE IF NEEDED?????? FAIL.

I am looking for a explanation to this problem, and also a solution for correcting this problem.

Thanks in advance.

Re: Boot-Up error

melvyn burnard — Wed, 20 Mar 2002 18:45:48 GMT

Well this looks like the system is going through the savecore (10.x) or savecrash (11.x) routine during bootup, where it checks to see if there is a crash dump that neeeds to be saved.
As to why the error? Is there more in the /etc/rc.log that might help?
It could be a number of reasons

Re: Boot-Up error

Patrick Wallek — Wed, 20 Mar 2002 19:01:53 GMT

Check and see if your /var/adm/crash directory exists and what the permissions are. If it is checking for the directory on boot up and it is not there, I suppose it could cause a problem.

Re: Boot-Up error

pap — Wed, 20 Mar 2002 20:20:03 GMT

Yes, Patrick is right.
Just check for /var/adm/crash directory. It gives error if the directory is not existing on the machine.
-pap

Re: Boot-Up error

Chris Zimo — Wed, 20 Mar 2002 20:49:23 GMT

The directory /var/adm/crash does exist, however it is empty. The permissions for this directory are as followes: rwxr-xr-x. Any suggestions as to what I should investigate next?

Thanks again...

Re: Boot-Up error

K.Vijayaragavan. — Thu, 21 Mar 2002 07:50:31 GMT

Hi,

see the output of command "bdf /var" as /var file system must have enough free space atleast as much of memory.

check the file "/sbin/init.d/savecrash".

As per this file if the "/etc/rc.config.d/savecore" file exists then it won't look for "/etc/rc.config.d/savecrash"

check the content of the files savecore and savecrash.

check the /etc/shutdown.log file and /etc/rc.log file.

check the size of swap file systems "swapinfo -m" as this error may occur if the swap size is not configureds enough.

-Vija