01-16-2002
Panic
Hi All,
When I came officce this morning I saw this error messages on the screen
-----
PANIC:srmountfun - Error 6 mounting rootdev hd (1/42)
Cannot dump 32639 pages to dumpdev hd (1/41) : space for only 0 pages
Dump not completed
--------
and machine was reboot mode. Why this problem happened ?
please help me
Thanks All
10 More Discussions You Might Find Interesting
1. SCO
Hi Friends ,
i am getting the following error when iam booting a sco unix system.
------------------
H init
PANIC : srmountfun --Error 22 mounting rootdev hd(1/42)
cannot dump 40863 pages to dempdev hd(1/41) : space for only 0 pages.
Dump not completed.
Safe to power off.... (1 Reply)
Discussion started by: sveera
1 Replies
2. SCO
Brief scenario of problem
working on contract for customer with supposedly identical setups in US and Europe
3 HP ML570 servers running SCO 5.07 networked together
servers 1 & 2 run the user applications , server 3 acts as backup / tape transport system between tape libraries
US side all... (0 Replies)
Discussion started by: ccarcher
0 Replies
3. Solaris
When ever i change my hard disk position from primary master to secondary slave, the solaris os gives a panic messge. how could i solve it. (2 Replies)
Discussion started by: ajay234
2 Replies
4. Solaris
Hi All, I've been troubleshooting this sendmail panic I'm getting on my dmesg. The errors are:
Feb 16 09:44:17 fakeserver_name sendmail: l1G1hGuD000884: Losing ./qfl1G1hGuD000884: savemail panic
Feb 16 09:44:17 fakeserver_name sendmail: l1G1hGuD000884: SYSERR(root): savemail: cannot save... (2 Replies)
Discussion started by: grumash
2 Replies
5. HP-UX
Hi all,
Does anybody know what kinds of events can prompt the following?
I found our test db box had rebooted itself. I'd like to know how I can go about finding our why. Thanks folks... (1 Reply)
Discussion started by: Kozmo
1 Replies
6. Solaris
Hello experts..
What is system panic? If a system is in that state.. what will happen?
Why is it goes to panic condition?
Just give me information about Panic condition.. How can i resolve this issue..?
If you know any links(URL) or Books...? replay me back....
Thanks in... (5 Replies)
Discussion started by: younus_syed
5 Replies
7. Solaris
Hi Guru's,
My Sun Fire v490 PRODUCTION server(Sol 5.9) has rebooted twice - on Apr'30 & May'08 2009.
And i found the following Error messages in /var/adm/messages file:
Apr 30 11:36:42 mumux201 unix:
Apr 30 11:36:42 mumux201 ^Mpanic/thread=2a1000c5d20:
Apr 30 11:36:42 mumux201 unix: ... (4 Replies)
Discussion started by: Hari_Ganesh
4 Replies
8. Solaris
Hi all,
solaris 10 system crashed, /var/adm/messages file:
panic/thread=3003ccaa060:
unix: mutex_exit: not owner, lp=60057340d28
owner=deadbeefdeadbee8 thread=3003ccaa06
0
unix:
genunix: 000002a10c4b1a00 sockfs:accept+1a8 (0, 3, 83,
5f03, 8c, 5c00)
genunix: %l0-3:... (1 Reply)
Discussion started by: Mehmet_Karaca
1 Replies
9. Solaris
Hi All,
I am getting the below error after login to box.
SunOS Release 5.10 Version Generic_147440-02 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
os-io Cross trap sync timeout: at cpu_sync.xword: 0x1010panic: failed to sto
p cpu8
panic: failed to... (1 Reply)
Discussion started by: chetansingh23
1 Replies
10. UNIX for Dummies Questions & Answers
Hi all,
I am running SCO6 in a VMWare environment. For the past two Sunday's during the system's automatic reboot I have received a Panic and the system has locked up. I have had to power off the VM and back on. I have never run into this sort of thing. Can someone help direct me to where... (1 Reply)
Discussion started by: Carlitos71
1 Replies
cr_info(3) Library Functions Manual cr_info(3)
NAME
cr_info - retrieve crash dump information
SYNOPSIS
DESCRIPTION
The function returns a pointer to a structure with information about an open crash dump.
cr_info_t
The structure contains the following fields. Note that there is no necessary correlation between the placement in this list and the order
in the structure, and the structure may contain other, reserved fields. In the future, this structure may change in size and should not be
copied to avoid compatibility problems with various releases.
char *cri_hostname Name of system dumped
char *cri_model Model string from system
char *cri_panic Panic message
char *cri_release Release string from system
char *cri_dumptime Time of the crash dump
char *cri_savetime Time crash dump saved
uint64_t cri_chunksize Size of uncompressed image files.
uint64_t cri_memsize Physical size of memory (bytes)
uint64_t cri_num_err Number of error messages
char **cri_errmsg Error messages from INDEX file
uint64_t cri_num_warn Number of warning messages
char **cri_warnmsg Warning messages from INDEX file
uint64_t cri_num_mod Number of module structures
cri_modinfo_t *cri_modinfo Array of module structures
uint32_t cri_num_nodes Number of nodes
uint32_t cri_monarch_node Physical monarch node number
The fields cri_hostname, cri_model, cri_panic, cri_release, cri_dumptime, and cri_savetime are all null-terminated strings; respectively,
representing the name and model of the system that dumped, the panic message, the release version string of the kernel, and the times that
the system dumped and the dump was saved. The amount, in bytes, of physical memory on the system is in cri_memsize. The target size, in
bytes, of individual uncompressed image files is in cri_chunksize. cri_errmsg and cri_warnmsg are arrays of null-terminated strings with
the list of saved messages. cri_num_err and cri_num_warn are the number of strings in each list. cri_modinfo is an array of structures
defining the loaded kernel modules; there are cri_num_mod elements in the array. cri_num_nodes is the number of nodes contained on the
machine and cri_monarch_node is the physical node number of the monarch.
cri_modinfo_t
The structure contains information specific to kernel modules loaded into memory at the time of the system crash. The specific fields are:
char *mdi_loadpath File path when loaded into memory
char *mdi_savepath File path when saved in crash directory
uint64_t mdi_size Size in bytes
uint64_t mdi_checksum Checksum of the file from cksum(1)
Again, the order of these fields within the structure is not specified, and other reserved fields may be present in the structure.
The caller must not modify any information in any of the structures returned by
RETURN VALUE
returns a pointer to the structure described above. If is not a valid descriptor of a crash dump opened with the return value is unde-
fined.
EXAMPLES
Assuming a process opened a crash dump, the following call to cr_info(3) retrieves the information about the open crash dump.
AUTHOR
was developed by HP.
SEE ALSO
cr_open(3), libcrash(5).
cr_info(3)