03-17-2006
"This could be a watchdog reset on a system with its obprom "watchdog-reboot?"
flag set to true. "
I suppose I don't know enough to see how this would make a reload useless. I basically want to try everything possible before changing the CPU. I only have one left.
If you could expound on what I'm missing (why the reload may be pointless) I would appreciate it.
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
WDMD(8) System Manager's Manual WDMD(8)
NAME
wdmd - watchdog multiplexing daemon
SYNOPSIS
wdmd [OPTIONS]
DESCRIPTION
This daemon opens /dev/watchdog and allows multiple independent sources to detmermine whether each KEEPALIVE is done. Every test interval
(10 seconds), the daemon tests each source. If any test fails, the KEEPALIVE is not done. In a standard configuration, the watchdog timer
will reset the system if no KEEPALIVE is done for 60 seconds ("fire timeout"). This means that if single test fails 5-6 times in row, the
watchdog will fire and reset the system. With multiple test sources, fewer separate failures back to back can also cause a reset, e.g.
T seconds, P pass, F fail
T00: test1 P, test2 P, test3 P: KEEPALIVE done
T10: test1 F, test2 F, test3 P: KEEPALIVE skipped
T20: test1 F, test2 P, test3 P: KEEPALIVE skipped
T30: test1 P, test2 F, test3 P: KEEPALIVE skipped
T40: test1 P, test2 P, test3 F: KEEPALIVE skipped
T50: test1 F, test2 F, test3 P: KEEPALIVE skipped
T60: test1 P, test2 F, test3 P: KEEPALIVE skipped
T60: watchdog fires, system resets
(Depending on timings, the system may be reset sometime shortly before T60, and the tests at T60 would not be run.)
A crucial aspect to the design and function of wdmd is that if any single source does not pass tests for the fire timeout, the watchdog is
guaranteed to fire, regardless of whether other sources on the system have passed or failed. A spurious reset due to the combined effects
of multiple failing tests as shown above, is an accepted side effect.
wdmd will exit if a watchdog driver is not loaded.
wdmd cannot be used on the system with any other program that needs to open /dev/watchdog, e.g. watchdog(8).
Test Source: clients
Using libwdmd, programs connect to wdmd via a unix socket, and send regular messages to wdmd to update an expiry time for their connection.
Every test interval, wdmd will check if the expiry time for a connection has been reached. If so, the test for that client fails.
(Other test sources such as scripts executed each test interval may be added in the future.)
OPTIONS
-D Enable debugging to stderr and don't fork.
-H num Enable (1) or disable (0) high priority features such as realtime scheduling priority and mlockall.
Default 1.
2011-08-01 WDMD(8)