03-17-2006
Thanks RTM. I appreciate the feedback and the education on the watchdog timer. I will attempt the reload first keeping in mind that I will likely need to dig up a CPU.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
we have a problem with a server UNIX SUN OS 5.7 :
we tried to reboot it and we have the following error message :
"boot load failed
the file just loaded does not appear to be executable "
we booted the server in single user mode with the cdrom
we made the mirrored disk bootable
we tried... (2 Replies)
Discussion started by: farzolito
2 Replies
2. UNIX for Advanced & Expert Users
Hi All.
Yesterday my pc worked fine. Today when booting the sequence gets just past mounting the root filesystem - it then says
' Module dependencies up to date (no new kernel modules found).'
At this point it hangs and goes no further! Does this sound familiar to anyone?
I am running... (2 Replies)
Discussion started by: silvaman
2 Replies
3. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
4. UNIX for Advanced & Expert Users
i have unix 5.4 running on team server hs failing to boot.
when i turn it on, it prints the following lines on the screen and just stops:
module ID 01: (0011) Main power supply ok
module ID 01: (0012) checks ok
module ID 01: (0020) test of SCSI device 0 x 0 in progress
module ID 01:... (4 Replies)
Discussion started by: ronst
4 Replies
5. Solaris
Hi everyone,
I have sun fire280R machine before i it is installed with solaris5.9 now i want to upgrade it but it not booting from the cd rom ....OK prompt also not comming i dont have solaris keyboard to press stop-A key...i have a intel supported keyboard ...what may be the problem it is... (1 Reply)
Discussion started by: alakshmanrao
1 Replies
6. Solaris
In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies
7. UNIX for Dummies Questions & Answers
hello
i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message:
Enabling system bus....... Done
Initializing CPUs......... Done
Initializing boot memory..
RAM-Copy CRC failure!Can't start: No image found
FATAL: Can't find/decompress... (0 Replies)
Discussion started by: bahjatm
0 Replies
8. Solaris
hello
i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message:
Enabling system bus....... Done
Initializing CPUs......... Done
Initializing boot memory..
RAM-Copy CRC failure!Can't start: No image found
FATAL: Can't find/decompress... (12 Replies)
Discussion started by: bahjatm
12 Replies
9. Solaris
Hi all,
I have the the following SCSI diagnostic codes shown in the attached photo
I suspect disk drive failure what can I do further to diagnose the disk. and if possible to boot into OS again. (5 Replies)
Discussion started by: h@foorsa.biz
5 Replies
10. Solaris
Hi
I have a problem on a server, when he boot I have this type of message loop, do you know what it corresponds to ?
( requesting internet Adress for 0:3:ba:fa:33:91 )
Regards
Sun Fire V240, No Keyboard
Copyright 2007 Sun Microsystems, INC. All rights reserved.
openboot 4.22.33,... (10 Replies)
Discussion started by: yoyo-tns
10 Replies
LEARN ABOUT HPUX
dump_compress_on
dump_compress_on(5) File Formats Manual dump_compress_on(5)
NAME
dump_compress_on - selects whether the system dumps memory pages compressed or uncompressed when a kernel panic occurs
VALUES
Failsafe
Default
(Allow the kernel to decide whether to dump compressed or not based on the system state at the time of the crash.)
Allowed value
Integer values and
The setting for is used as follows:
Dump uncompressed.
Dump with compression for speed if possible.
Recommended values
(Allow the kernel to choose dump mode.)
The value the kernel usually chooses is 1.
DESCRIPTION
On large systems, the time required to dump system memory when a kernel panic occurs can be excessive or even prohibitive, depending on how
much physical memory is installed in the system. Compressed dump capability results in smaller and faster dumps that will also take lesser
time to save over into the filesystem.
The (see crashconf(1M)) command and its associated configuration file control the dump compression mode in the memory dumps associated with
a system crash. On rare occasions, the system may crash before is run during the boot process. On those occasions, the configuration set
using the tunable will be used.
The default value for this parameter is The system determines whether or not to dump compressed based on the type of crash that occurs, in
this case.
Note that certain types of system crash require an uncompressed crash dump. Also, the system operator may request an uncompressed crash
dump at the time the dump is taken. In either of these cases, an uncompressed dump will be performed regardless of the mode selected in
Who Is Expected to Change This Tunable?
Only HP Field engineers should change the value of this tunable.
Restrictions on Changing
Changes to this tunable take effect immediately.
When Should the Tunable Be Turned On?
This tunable should be turned on to dump compressed when there is a system crash.
What Are the Side Effects of Turning the Tunable Off?
In this case, an uncompressed dump is taken always. On large memory machines, an uncompressed dump take typically three times longer than
a compressed dump.
When Should the Tunable Be Turned Off?
The tunable should be turned off if there is a problem with compressed dumps.
What Are the Side Effects of Turning the Tunable On?
The system decides the dump mode based on the type of crash.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by Hewlett-Packard Company.
SEE ALSO
crashconf(1M), alwaysdump(5), dontdump(5).
Tunable Kernel Parameters dump_compress_on(5)