10 More Discussions You Might Find Interesting
1. Red Hat
dear experts linux
i am using RHEL 5.5 run on a physical server.
i am front of a big trouble, the Rhel can't run correctly , it show me this error message in black screen:
reading all physical volumes. this my take a while ..
found volume group "VolGroup00" using metadata type lvm2
9... (1 Reply)
Discussion started by: wassimpb
1 Replies
2. Slackware
Hi,
first of all I'm 110% newbie, sorry for any mistake if I made it.
In my country there are no normal or active linux forums, so i found this forum.
Ok, that's for begining, but not for may real problem.
---------------------------------------------------
I am system administrator... (4 Replies)
Discussion started by: ElvijsL
4 Replies
3. Ubuntu
I installed a new kernel 3.0.22 on ubuntu server 11.04 32 bit.
when I select the kenel from boot loader it stops when
Code:
loading initial ramdisk...
I added all_generic_ide at the end of linux line and also added dev/sda1 to linux line: root=UUID=dev/sda1
now it says that
... (12 Replies)
Discussion started by: dr_mabuse
12 Replies
4. SCO
I am trying to restore Unixware 7.1 from a backup using RestoreEdge which is from Microline version 2. The restore is on another machine using the same RAID controller and TBU. We are retiring the other machine.
Anyway, we get to disk #2 and it panics. Here is the Pic.
Can anyone tell me... (13 Replies)
Discussion started by: ccd1977
13 Replies
5. UNIX Desktop Questions & Answers
Hi ALL,
I am getting error..
kernal panic-not syncing:fatal exception
while booting.
Please help me..
Thanks
Jack (7 Replies)
Discussion started by: jack00423
7 Replies
6. UNIX for Dummies Questions & Answers
:) Firstly Hi all!!, im NEW!! and on here hoping that someone might be able to offer me some help... i have a server that keeps crashing every few days with the error message:
PANIC KERNAL-MODE ADDRESS FAULT ON USER ADDRESS 0X14
KERNAL PAGE FAULT FROM (CS:EIP)=(100:EF71B5BD)
EAX=EF822000... (10 Replies)
Discussion started by: Twix
10 Replies
7. Linux
Hi all,
I am new to redhat/fedora linux.
In fedora linux 6,we created one file system(hda3 - /fs).
in this mount poing we were installed mounta vista os.
while booting we are getting below error messages.
1)
Booting 'mountaVisat(2.6.18_pro 500_pc_target-x86_586 smp)'
root(hd0,1)... (2 Replies)
Discussion started by: arjunreddy3
2 Replies
8. Linux
ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before?
I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system.
Please Help... (2 Replies)
Discussion started by: dave043
2 Replies
9. UNIX for Dummies Questions & Answers
I am trying to Install RHEL AS 4 on x86 pc, through VNC and got the below error, Am not pretty sure as how to resolve this. Can some one guide me through the process, or what might be missing....
Have Installed RHEL, many a times but cudnt find this out...
Wud appreciate an early reply ......... (0 Replies)
Discussion started by: Crazy_murli
0 Replies
10. UNIX for Dummies Questions & Answers
Received the following on the weekend.
Panic:k_trap kernel mode trap type 0X0000000e cannot dump 163739 pages to dumpdev hd (1/41):space for only 48640 pages
Dump not complete
Safe to power off or press any key to reboot
Any ideas how to fix this one? It also happen a month ago. (3 Replies)
Discussion started by: jcoleman544
3 Replies
CRASH(8) BSD System Manager's Manual CRASH(8)
NAME
crash -- FreeBSD system failures
DESCRIPTION
This section explains a bit about system crashes and (very briefly) how to analyze crash dumps.
When the system crashes voluntarily it prints a message of the form
panic: why i gave up the ghost
on the console, and if dumps have been enabled (see dumpon(8)), takes a dump on a mass storage peripheral, and then invokes an automatic
reboot procedure as described in reboot(8). Unless some unexpected inconsistency is encountered in the state of the file systems due to
hardware or software failure, the system will then resume multi-user operations.
The system has a large number of internal consistency checks; if one of these fails, then it will panic with a very short message indicating
which one failed. In many instances, this will be the name of the routine which detected the error, or a two-word description of the incon-
sistency. A full understanding of most panic messages requires perusal of the source code for the system.
The most common cause of system failures is hardware failure, which can reflect itself in different ways. Here are the messages which are
most likely, with some hints as to causes. Left unstated in all cases is the possibility that hardware or software error produced the mes-
sage in some unexpected way.
cannot mount root This panic message results from a failure to mount the root file system during the bootstrap process. Either the root
file system has been corrupted, or the system is attempting to use the wrong device as root file system. Usually, an alternate copy of the
system binary or an alternate root file system can be used to bring up the system to investigate. Most often this is done by the use of the
boot floppy you used to install the system, and then using the ``fixit'' floppy.
init: not found This is not a panic message, as reboots are likely to be futile. Late in the bootstrap procedure, the system was unable to
locate and execute the initialization process, init(8). The root file system is incorrect or has been corrupted, or the mode or type of
/sbin/init forbids execution or is totally missing.
ffs_realloccg: bad optim
ffs_valloc: dup alloc
ffs_alloccgblk: cyl groups corrupted
ffs_alloccg: map corrupted
blkfree: freeing free block
blkfree: freeing free frag
ifree: freeing free inode These panic messages are among those that may be produced when file system inconsistencies are detected. The
problem generally results from a failure to repair damaged file systems after a crash, hardware failures, or other condition that should not
normally occur. A file system check will normally correct the problem.
timeout table full This really should not be a panic, but until the data structure involved is made to be extensible, running out of entries
causes a crash. If this happens, make the timeout table bigger.
init died (signal #, exit #) The system initialization process has exited with the specified signal number and exit code. This is bad news,
as no new users will then be able to log in. Rebooting is the only fix, so the system just does it right away.
That completes the list of panic types you are likely to see.
If the system has been configured to take crash dumps (see dumpon(8)), then when it crashes it will write (or at least attempt to write) an
image of memory into the back end of the dump device, usually the same as the primary swap area. After the system is rebooted, the program
savecore(8) runs and preserves a copy of this core image and the current system in a specified directory for later perusal. See savecore(8)
for details.
To analyze a dump you should begin by running kgdb(1) on the system load image and core dump. If the core image is the result of a panic,
the panic message is printed. For more details consult the chapter on kernel debugging in the FreeBSD Developers' Handbook
(http://www.freebsd.org/doc/en/books/developers-handbook/).
SEE ALSO
kgdb(1), dumpon(8), reboot(8), savecore(8)
HISTORY
The crash manual page first appeared in FreeBSD 2.2.
BSD
July 23, 2011 BSD
