1834195 Members
2450 Online
110064 Solutions
New Discussion

savecore.LCK

 
SOLVED
Go to solution

savecore.LCK

Hi Admins,

Here's a strange occurence with a K-class node. Everytime we boot this machine a coredump is made. Her is the info from /etc/rc.log :

Save system crash dump if needed
Output from "/sbin/rc1.d/S440savecrash start":
----------------------------
savecrash: Found old-format dump, invoking /usr/old/sbin/savecore
savecore: Invalid /etc/savecore.LCK file from previous run.
Dump may be corrupted.
savecore: dump previously saved
EXIT CODE: 2 - savecrash found no core dump to save
"/sbin/rc1.d/S440savecrash start" SKIPPED

This weird occurence started after I installed HP 11.00 on the box again. I suspect there's a flag hanging somewhere on the bootdisc.

Can someone help me out ?

TIA,

Willy Schriemer
Sysadmin HP3000/9000
Philips Semiconductors
The Netherlands

7 REPLIES 7
Clemens van Everdingen
Honored Contributor

Re: savecore.LCK

Willy,

It looks like the system thinks there needs to be a dump made.

Try booting in single user mode and run this command:

# savecore -c

from man savecore:

-c Mark the dump in the dump device as saved, without performing any other action. The -c option is useful for manually inhibiting dump actions called
by /sbin/init.d/savecore.

Now reboot the system again !

C.
The computer is a great invention, there are as many mistakes as ever, but they are nobody's fault !
melvyn burnard
Honored Contributor

Re: savecore.LCK

I agree with Clemens, you have an old dump marked for saving, and you can clear it by doing savecore -c

Once this has been done, you can try to run
/sbin/rc1.d/S440savecore start
and see if this still reports a dump is there. If not, no need to reboot.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!

Re: savecore.LCK

Thanks so far. However we have allready done this, from that moment on, we get the message above. Before we performed the "savecore -c" command, the system actually made a dump in /var/adm/crash. But the next reboot the system tried to make another dump with the same message; "Found old-format dump, invoking ... etc.."

Any other suggestions?
Clemens van Everdingen
Honored Contributor

Re: savecore.LCK

Hi,

Maybe since the upgrade or install to 11.00 you need to use savecrash -c instead of savecore -c.

This has been changed between versions.

C.
The computer is a great invention, there are as many mistakes as ever, but they are nobody's fault !
Clemens van Everdingen
Honored Contributor
Solution

Re: savecore.LCK

Hi,

Another more definite solution would be to do a TOC dump to have the old dump format overwritten.

a TOC will overwrite the information on the DUMP device which should be in 11.00 format.

Keep all user file systems unmounted before doing a TOC. Also, have a backup from the system.

If the file /etc/savecore.LCK is on the system.
Do stings /etc/savecore.LCK
Also remove this file.

C.
The computer is a great invention, there are as many mistakes as ever, but they are nobody's fault !

Re: savecore.LCK

Hi Clemence,
Thanks, forcing a TOC did the job. After this the system doesn't report any old dumps anymore.

Best regards,
Addie.
Clemens van Everdingen
Honored Contributor

Re: savecore.LCK

Addie,

Good to hear the solution works.

C.
The computer is a great invention, there are as many mistakes as ever, but they are nobody's fault !