- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- savecore: open failed
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2001 06:11 AM
03-28-2001 06:11 AM
savecore: open failed
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2001 06:29 AM
03-28-2001 06:29 AM
Re: savecore: open failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2001 06:37 AM
03-28-2001 06:37 AM
Re: savecore: open failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2001 06:40 AM
03-28-2001 06:40 AM
Re: savecore: open failed
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2001 06:48 AM
03-28-2001 06:48 AM
Re: savecore: open failed
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...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2001 06:59 AM
03-28-2001 06:59 AM
Re: savecore: open failed
Check with ioscan -nfCfloppy for device and ioscan -H /dev/floppy/c0t0d0, if it is a ghost device then rmsf /dev/floppy/c0t0d0.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2001 08:39 AM
03-28-2001 08:39 AM
Re: savecore: open failed
# 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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2001 01:19 PM
03-28-2001 01:19 PM
Re: savecore: open failed
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