Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Failing to boot - DMVA problem Post 102456 by RTM on Friday 17th of March 2006 11:14:44 PM
Old 03-18-2006
Watchdog resets are usually hardware related.

Does this server have one or more than one cpu? If more than one, remove one and see if the issue goes away. If it doesn't (still gets a watchdog reset), put that cpu back in, and pull the other one. If the issue goes away, you could always just run on one cpu (if they are so hard to come by) or replace the bad one. If the watchdog reset doesn't go away, then it could be your memory. But attempting to reload the OS will not make a hardware issue go away. You will still have the watchdog reset issue, possibly mess up what is on the hard drive already, and have wasted your time.

The second part of the information I posted states:
The system leaves no messages when it reboots.

This could be a watchdog reset on a system with its obprom "watchdog-reboot?" flag set to true.

This means that if at the ok prompt, if you do a printenv, you will see all the different parameters. If parameter watchdog-reset IS set to true, there may not be a message as to why it had a watchdog-reset. Set it to false for more info.

If you have more information about which CPU or possibly which memory board is bad, post the info.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Boot problem

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

Boot Problem

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

solaris boot problem boot error loading interpreter(misc/krtld)

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

unix server failing to boot

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

Boot problem

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

flar restore with svm mirrors failing to create boot image

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

boot problem

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

boot problem

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

Boot problem

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

Problem boot 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
dump_concurrent_on(5)						File Formats Manual					     dump_concurrent_on(5)

NAME
dump_concurrent_on - enable/disable option for system to dump memory using multiple dump units when a kernel panic occurs VALUES
Failsafe Default Allowed values Recommended value 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. Concurrent dump capability results in faster dumps by dividing the task to different dump units which can execute in parallel. The default value for The system determines whether or not to dump with multiple units based on the resources (CPUs and disks) available on the system and the properties of the drivers. The (see crashconf(1M)) command and its associated configuration file control the dump concurrency 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. 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 allow dumps to dump with multiple dump units when there is a system crash if there are sufficient resources. What Are the Side Effects of Turning the Tunable Off? Dumps may take more time. When Should the Tunable Be Turned Off? The tunable should be turned off if there is a problem using multiple dump units. What Are the Side Effects of Turning the Tunable On? The system decides whether or not to use multiple dump units based on the resources available. 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 HP. SEE ALSO
crashconf(1M), alwaysdump(5), dontdump(5), dump_compress_on(5). Tunable Kernel Parameters - Integrity Systems Only dump_concurrent_on(5)
All times are GMT -4. The time now is 05:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy