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
DUMPON(8) BSD System Manager's Manual DUMPON(8)
NAME
dumpon -- specify a device for crash dumps
SYNOPSIS
dumpon [-v] special_file
dumpon [-v] off
dumpon [-v] -l
DESCRIPTION
The dumpon utility is used to specify a device where the kernel can save a crash dump in the case of a panic.
Calls to dumpon normally occur from the system multi-user initialization file /etc/rc, controlled by the ``dumpdev'' variable in the boot
time configuration file /etc/rc.conf.
The default type of kernel crash dump is the mini crash dump. Mini crash dumps hold only memory pages in use by the kernel. Alternatively,
full memory dumps can be enabled by setting the debug.minidump sysctl(8) variable to 0.
For systems using full memory dumps, the size of the specified dump device must be at least the size of physical memory. Even though an
additional 64 kB header is added to the dump, the BIOS for a platform typically holds back some memory, so it is not usually necessary to
size the dump device larger than the actual amount of RAM available in the machine. Also, when using full memory dumps, the dumpon utility
will refuse to enable a dump device which is smaller than the total amount of physical memory as reported by the hw.physmem sysctl(8) vari-
able.
The -l flag causes dumpon to print the current dump device or _PATH_DEVNULL ("/dev/null") if no device is configured.
The -v flag causes dumpon to be verbose about its activity.
IMPLEMENTATION NOTES
Since a panic(9) condition may occur in a situation where the kernel cannot trust its internal representation of the state of any given file
system, one of the system swap devices, and not a device containing a file system, should be used as the dump device.
The dumpon utility operates by opening special_file and making a DIOCSKERNELDUMP ioctl(2) request on it to save kernel crash dumps. If
special_file is the text string: ``off'', dumpon performs a DIOCSKERNELDUMP ioctl(2) on /dev/null and thus instructs the kernel not to save
crash dumps.
Since dumpon cannot be used during kernel initialization, the dumpdev variable of loader(8) must be used to enable dumps for system panics
which occur during kernel initialization.
FILES
/dev/{ada,da}?s?b standard swap areas
/etc/rc.conf boot-time system configuration
SEE ALSO
fstab(5), rc.conf(5), config(8), init(8), loader(8), rc(8), savecore(8), swapon(8), panic(9)
HISTORY
The dumpon utility appeared in FreeBSD 2.1.
BUGS
Because the file system layer is already dead by the time a crash dump is taken, it is not possible to send crash dumps directly to a file.
BSD
October 8, 2014 BSD
