topic Re: savecore: open failed in Operating System - HP-UX

savecore: open failed

John R Brown — Wed, 28 Mar 2001 14:11:29 GMT

We have cloned a system using make_recovery, and it seems to be working ok. On boot-up, we get the following error from savecore:

Entry from: /etc/rc.log

Save system core image if needed
Output from "/sbin/rc1.d/S440savecore start":
----------------------------
savecore: open failed /dev/floppy/c0t0d0: No such device or address
savecore: could not open dump
EXIT CODE: 1
"/sbin/rc1.d/S440savecore start" FAILED

The message is correct - the device does not exist. However, we can't find where it is specified.

Our dump device is:

# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t0d1 (0/28/4.0.1) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t0d1
Root: lvol3 on: /dev/dsk/c2t0d1
Swap: lvol2 on: /dev/dsk/c2t0d1
Dump: lvol2 on: /dev/dsk/c2t0d1, 0

Does anyone know how to redirect savecore?

Re: savecore: open failed

Vincenzo Restuccia — Wed, 28 Mar 2001 14:29:33 GMT

You have HPUX 10.20 or 11.00 ?

Re: savecore: open failed

John R Brown — Wed, 28 Mar 2001 14:37:02 GMT

We are running HP-UX 10.20

Re: savecore: open failed

Paula J Frazer-Campbell — Wed, 28 Mar 2001 14:40:43 GMT

Hi
I would imagine that the system you cloned from had a floppy at /dev/floppy/c0t0d0, so the info is from the master sys.

Paula

Re: savecore: open failed

James R. Ferguson — Wed, 28 Mar 2001 14:48:04 GMT

Hi John:

The normal location for savecore files is /var/adm/crash. This is defined in /etc/rc.config.d/savecore and/or /sbin/init.d/savecore.

...JRF...

Re: savecore: open failed

Vincenzo Restuccia — Wed, 28 Mar 2001 14:59:09 GMT

Redirection is in /var/adm/crash.
Check with ioscan -nfCfloppy for device and ioscan -H /dev/floppy/c0t0d0, if it is a ghost device then rmsf /dev/floppy/c0t0d0.

Re: savecore: open failed

John R Brown — Wed, 28 Mar 2001 16:39:23 GMT

There is no occurrence of this device in the ioscan
# ioscan -fn | grep c0t0d0
#

Following Vincenzo's advice, we removed the special files:
# find /dev -name *c0t0d0* -print
/dev/floppy/c0t0d0
/dev/rfloppy/c0t0d0
# rmsf -a /dev/floppy/c0t0d0
Warning: No device associated with "/dev/floppy/c0t0d0"
# rmsf -a /dev/rfloppy/c0t0d0
Warning: No device associated with "/dev/rfloppy/c0t0d0"
# find /dev -name *c0t0d0* -print
#

The problem is different, now, but still seems to be misdirected.

Save system core image if needed
Output from "/sbin/rc1.d/S440savecore start":
----------------------------
savecore: missing device file: 1c000000
EXIT CODE: 2 - savecore found no core dump to save
"/sbin/rc1.d/S440savecore start" SKIPPED

How do I point it to another device?

Re: savecore: open failed

John R Brown — Wed, 28 Mar 2001 21:19:26 GMT

FYI -

We appear to have gotten past the problem by forcing a dump which went to the new swap/dump file. It was found and copied by savecore on the next boot. Subsequent boots indicate no dump to process.

/etc/rc.log entry:
Save system core image if needed
Output from "/sbin/rc1.d/S440savecore start":
----------------------------
savecore: dump previously saved
EXIT CODE: 2 - savecore found no core dump to save
"/sbin/rc1.d/S440savecore start" SKIPPED

Thanks to everyone for your help.

John