08-23-2004
Reboot after Panic
I've got htis message on our sun U60 machine:
"Reboot after panic:errID 0x000004eff........." ,this message have been issued on the /var/adm/messages file & cause system rebooting randomly.
Any comment.
Thanks,
--Nikk
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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... (3 Replies)
Discussion started by: alisev
3 Replies
2. 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
3. UNIX for Advanced & Expert Users
One of our servers keeps crashing.
Here is the following message that we get:
11:01 Thu Aug 31 2006. Reboot after panic: fcpbh_scsi_comp: Inbound data overf
low
12:28 Wed Sep 6, 2006. Reboot:
16:12 Wed Sep 06 2006. Reboot after panic: , isr.ior = 0'10240070.0'dcf72938
Does anyone... (1 Reply)
Discussion started by: shoultsc
1 Replies
4. Solaris
Hi Guru's
Can any want here could explain to me the different between soft reboot and hard reboot .
Best Regards
Seelan (3 Replies)
Discussion started by: seelan3
3 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. Red Hat
Could you please help with problem with megaraid controller and Dell PowerEdge 2850, all that I can see on thi screenshot:
All drives successfuly passed verifing from LSI controllers (Ctrl+A at startup), also I tried to boot from rescue llive cd and mount all the morrored drives and check... (22 Replies)
Discussion started by: nikkadim
22 Replies
7. 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
8. 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
9. 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
10. SCO
Hello
when i booting my SCO Server I become this Message
PLS can anyone help me?
Cheers
Christoph (1 Reply)
Discussion started by: cga
1 Replies
LEARN ABOUT MINIX
shutdown
SHUTDOWN(8) System Manager's Manual SHUTDOWN(8)
NAME
shutdown - graciously close the system down
SYNOPSIS
shutdown [-hrRmk] [-x code] [time-specification [message]]
DESCRIPTION
Shutdown is a program which allows a system operator to close down the system in an nice way. Shutdown informs the users why and when the
system is going down. This warning is issued 10 minutes before shutdown time and every minute in the last 5 minutes. At this time (5 min-
utes), shutdown creates a file /etc/nologin to prevent new users from logging in.
Shutdown keeps a logfile of shutdowns. Every shutdown is registered in /usr/adm/wtmp, if this file exists. After these actions, a call is
done to reboot(2) which actually brings the system down.
Time-specification may be something like 15:00, 15.00, +15, or now for a shutdown at 3pm (twice), 15 minutes from now, or immediately.
The message may be used to describe why the system is going down, it may also be typed on standard input with the -m option.
OPTIONS
-h This flag prevents the system from rebooting after the shutdown. The system can now be powered off. This is the default.
-r This flag indicates that the system should reboot after shutting down.
-R Reboot the system by resetting it. Normally the kernel will try to return to the Boot Monitor. With -R the system will receive a
hardware reset.
-x code
Halt the system and let the Monitor execute the given code as if typed at the monitor prompt. You can for instance use -x 'boot
hd0' as a very fast way to reboot "from the top."
-m Allows the operator to type a shutdown message on standard input, that will be added to the messages displayed on all terminals.
-k This option gives the possibility of terminating an already started shutdown. This is only possible if shutdown time has not yet
arrived.
-C Check if the system crashed. This option is not used at shutdown time, but at reboot time. It tells if the file systems should be
checked by testing if the last entry in the wtmp file is a shutdown entry. (A crude replacement for a file system clean flag.)
FILES
/usr/adm/wtmp, /etc/nologin, /usr/adm/authlog
SEE ALSO
reboot(2), wall(1), halt(8), boot(8).
AUTHOR
Edvard Tuinder (v892231@si.hhs.NL)
SHUTDOWN(8)