01-16-2002
It sounds like your root disk has been corrupted. There may even be a hardware problem with the root disk. But it is interesting that the loader was able to get the kernel into core in order to attempt the mount of the root disk. Was it looping attempting the reboot and repeatedly issuing the error messages? If so, the hardware may be ok.
This type of stuff varies among the various types of unix systems, so specific advise isn't possible. You probably have some bootable media like a cd that could be used to inspect the root disk. If so, try that and see if you fsck it. But I would guess that you will wind up needing to re-install the os.
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
LEARN ABOUT DEBIAN
log::handler::output::screen
Log::Handler::Output::Screen(3pm) User Contributed Perl Documentation Log::Handler::Output::Screen(3pm)
NAME
Log::Handler::Output::Screen - Log messages to the screen.
SYNOPSIS
use Log::Handler::Output::Screen;
my $screen = Log::Handler::Output::Screen->new(
log_to => "STDERR",
dump => 1,
);
$screen->log($message);
DESCRIPTION
This output module makes it possible to log messages to your screen.
METHODS
new()
Call "new()" to create a new Log::Handler::Output::Screen object.
The following options are possible:
log_to
Where do you want to log? Possible is: STDOUT, STDERR and WARN.
WARN means to call "warn()".
The default is STDOUT.
dump
Set this option to 1 if you want that the message will be dumped with "Data::Dumper" to the screen.
log()
Call "log()" if you want to log a message to the screen.
Example:
$screen->log("this message goes to the screen");
validate()
Validate a configuration.
reload()
Reload with a new configuration.
errstr()
This function returns the last error message.
PREREQUISITES
Data::Dumper
Params::Validate
EXPORTS
No exports.
REPORT BUGS
Please report all bugs to <jschulz.cpan(at)bloonix.de>.
If you send me a mail then add Log::Handler into the subject.
AUTHOR
Jonny Schulz <jschulz.cpan(at)bloonix.de>.
COPYRIGHT
Copyright (C) 2007-2009 by Jonny Schulz. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.14.2 2012-11-21 Log::Handler::Output::Screen(3pm)