After a reboot, my PC just hang. It says "insmod : error inserting '/lib/raid456.ko : -1 File exists ..." then followed by a kernel panic. I have tried to boot using rescue mode but it couldn't find any Linux partition, thus no /mnt/sysimage was mounted. It left me at a shell and I'm stuck there.
View 3 Repliesinsmod: error inserting 'kernel.ko': -1 Invalid parametersI am getting this error when i am try to insert kernel.ko into kernelMy systemfedora 12 with gcc 4.4.2insmod kernel.koinsmod: error inserting 'kernel.ko': -1 Invalid parametersmy program
__________________kernel.c________________________ ___________
#include <linux/module.h> /* Needed by all modules */
#include <linux/kernel.h> /* Needed for KERN_INFO */
[code].....
today I updated my Slackware 13.0 to 13.1. Unfortunately it didn't boot any longer. I probably forgot to run "lilo" before restarting. However, I reinstalled Slackware and I installed grub instead of lilo I'm more familiar with it..
This was my first menu.lst config:
Quote:
title Linux (uuid)
root(hd0,0)
kernel /vmlinuz root=UUID=6a8096a3-3915-4ef2-8984-976e42d04cfc ro vga=0x031b
While booting it stopped and printed this message:
Quote:
Kernel panic - not syncing: VFS; Unable to mount root fs on unknown-block
Then I compared it to other Linux system on different computers and I noticed that every of them, who are using uuids, using an initrd as well. So I created one and now it boots properly.
I just wonder, why? Why does it need an initrd to boot by using uuids?
I have some problems with CentOS 5.4 and standard kernel 2.6.32.7, which I need for realtime extensions.With the solution in this thread: [URL] I could boot the new standard kernel , There are still two error messages during the boot process:
"insmod: error inserting /lib/dm-region-hash.ko -1 fikle exists"
and a problem with ip-tables "could not restore ip-tables line 20" or so
I've currently have opensuse 11.3 installed on my system and I would like to do a new fresh install of opensuse 11.4. I therefore downloaded the DVD 11.4 x64 install. However, when booting the kernel from the DVD (that leads to the installation procedure) I obtain the following error message "unable to handle kernel paging request". The system then stops and I need to perform a hard reset to restart again. The same happens if I try do boot from the live gnome CD. Thus, I'm unable to install opensuse 11.4 at all due to this problem. A possible solution would be to perform a hot update (i.e. changing repositories in my 11.3 and perform a zypper refresh and zypper dup). But I'm a bit scared of doing this since this will install the problematic kernel. how to circumvent this problem ? Is there any updated version of the live CD? I've been able to install opensuse 11.4 x64 without problems at home. Now I'm trying to install it at work. The current kernel (at work) is:
[code]....
Dell laptop booting from a USB stick with a CentOS 5.5 minimum installation.
Uncompressing Linux...OK, booting the kernel.
Red Hat nash version 4.2.1.13 starting
sda: assuming drive cache: write through
sda: assuming drive cache: write through
mount: error 6 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd-dev failed: 2
Kernel panic - no syncing: Attempted to kill init!
1. Does minimum installation not drop on a kernel or initrd with ext3 support? I can't imagine that's true, but have to ask.
2. The USB stick is single partition ext3. Maybe there is some limitation specifically related to USB stick booting that requires boot to be FAT16 or FAT32? Except the CentOS 5.5 installer refuses to let me install on either FAT.
3. How can I do the equivalent of lsmod on a linux installation that will not boot? i.e. I have CentOS x86_64 running in VirtualBox, I can plug the USB stick in there, so how do I get information on the USB stick's kernel and initrd if I can't boot from it?
4. Is it possible to rebuild the i386 based initrd on this USB stick, when the computer is not booted from that stick, with a system that's x86_64 based?
System Info:
Dell Latitude i686 Laptop which has run CentOS 5.5 and Fedora 12,13,14 in the past, and boots from Fedora 14 Live CD transferred to a USB stick. So I know USB booting is possible on this machine, and this stick.
The process of creating the stick:
CentOS 5.5 i386 on a USB stick. Old Dell i686 laptop which has previously run CentOS 5.5 installed from DVD, and has successfully booted from this same USB stick holding transferred Fedora 12,13,14 Live CDs. CentOS 5.5 was installed onto the USB drive directly by the CentOS 5.5 DVD installer (running virtualized in VirtualBox 4.02 on Mac OS X 10.6.5.). No errors or complaints during installation.
For whatever reason, the installer did not do some things correctly. First Grub wasn't working correctly, I got that sorted out and have the Grub+CentOS splash screen, it finds vmlinuz and the initrd, and then I get a kernel panic.
Ext3 was built into the kernel and that's why I'm getting this message. I do not know how the installer would have dropped a kernel or initrd during instalation that that don't contain such a basic thing that obviously comes in linux kernel 2.6.18-89 EL.
im a rookie at configuring linux and i have problem booting slackware 13.1 just installed. i get a message similar to this Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(8,4) i got this one from another user who has a similar problem, they say i should fix lilo.conf and it actually was pointing to a wrong partition so i fixed it. i also fixed /etc/fstab to make it point to the right partition /dev/sda3. but after fixing the files, it still wants to load something in /dev/sda4, i dont know why so what should i do next, please explain with commands and not just words. edit this is my lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda3
[Code]...
The first server I installed installed fine. The second server, installed with the same config, went to "kernel panic not syncing no init found try passing init= option in kernel" error. I tried reinstalling but it keeps going to that error after install reboot. The storage is ISCSI connected via Intel Server Adapter, which allows it to boot from ISCSI. Not sure if that's the cause for the problem, but the first server is connected to the same ISCSI and installed just fine.
Is there a way that I can make sure ISCSI module installs during installation? Although I think it is installed since it's able to copy the files and setup /dev/sda. I just wana make sure that it installs during setup.
I decided to try Linux recently. I downloaded CentOS-5.3-i386-bin-DVD.iso. Installation was successful but the OS reports Kernel Panic while booting. At first I can see messages:
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not usin MMCONFIG
The OS continues to boot, but then shows kernel panic.
I tried to solve this problem during several days. I've installed the OS at least 10 times changing conditions. I tried x86-64 version, disabled PAE in BIOS, performed manual partitioning without LVM. The result is the same.
My PC has Intel Core 2 Duo E8400 CPU (no overclocking), 4GB RAM (DDR2-800), ATI 3470 GPU. Windows is working smoothly on it, I can encode video during several hours without problem. All fans are working, the system is not overheated. MemTest86 showed no errors.
I've installed CentOS on my laptop (Core 2 T5600 CPU, 2GB RAM, Intel G945 Video), it works nice, i like it very much.
For testing I've installed OpenSUSE 11.1 on the PC, everything is ok, I'm writing this message from it.
i m trying to install Centos 5.5 on a x86_64 machine i use kickstat and cobbler but during the %pre script the installation failed with the following message
kernel panic ; not syncing nmi watchdog does someone what can be the cause of that?
Here is the beginning of my kickstart file with the pre part
url --url=http://cobbler.int-evry.fr/cblr/links/Centos-5.5-x86_64
# If any cobbler repo definitions were referenced in the kickstart profile, include them here.
repo --name=el5-x86_64-rpmfusionnonfree --baseurl=http://cobbler.int-evry.fr
[Code]....
Today I upgraded one of my computers with the following command
% yum upgrade
Before the upgrade the computer was running CentOS 5.3 with the versionlock plugin and kernel 2.6.18-128. The update went smoothly (no dependency problems).
If I try to reboot with the new kernel (2.6.18-194), I get the following:
Found volume group VolGroup00 using metadata type lvm2
2 logical groups in VolGroup00 now active
mount: error mounting /dev/root on /sysroot as ex3t: No such device
setuproot: moving /dev failed: No such file or directory
[Code].....
If I reboot with the previous kernel (2.6.18-128), everything is fine.
I have a Centos 4.8 linuxbox running in VMWare ESXi 4 and the kernel is 2.6.9-89.0.11.ELsmp. Recently, this linuxbox is quite unstable, it has kernel panic once a week... But we didn't have any configuration changes on it. And I have attached the kernel panic console screen and lsmod for the server.[URL]...
View 2 Replies View RelatedI suffered a kernel crash today - then noticed a newer kernel was available, so I updated to it.However, it's since crashed again! Here's the message - can anyone tell me what's going on, is this a known issue or is it bad hardware?
general protection fault: 0000 [1] SMP
last sysfs file: /devices/pci0000:00/0000:00:00.0/irq
CPU 2
[code]....
I had been testing the this link Raid Setup
I can do this in the installation phase, no issue, but I have to know how to make it in a production server.
I follow, read and test the article 3 times without any success, went I try to boot my machine with the raid disk it show error about that cannot find my root "/dev/root"
mount: could not find filesystem '/dev/root'
...
setuproot : moving /dev failed: no such fie or directory
no fstab.sys
[Code]....
But I still don't know what I have done wrong, this is my 3rd time that I try this without any luck, I'm running Centos 5.3 updated. Both disk are the same size.
I installed CentOS 5.5 and after the install when the system reboot, it give me a kernel panic error saying that it don't find the drive /dev/sdb4. I didn't install Grub since Ubuntu is already present on the first drive. I let Grub2 OS prober install it in Grub menu. Here is the grub line:
menuentry "CentOS release 5.5 (Final) (on /dev/sdb4)" {
insmod ext2
set root='(hd1,4)'
[code]....
During boot from CentOS5.4 DVD and after choose linux rescue mode, encounters with error:
Code: 8b 5e 04 83..... ........ 3d c0
EIP:[<c0417656>]__modify_IO_APIC_irq+0x40/0x62 SS:ESP 0068:df94eed4
<0> Kernel panic - not syncing : Fatal exception
I created a CD image of my CentOS installation using mondo. When I booted from this CD and, in the restore process, selected an option to test the integrity of the image, it got to a certain point and said: Failure to execute /init. Kernel panic - not syncing: No init found. Try passing init= option to kernel.The instructions say the kernel may need to be recompiled with certain options.Does anyone know if the CentOS kernel needs to be recompiled for use with mondo? If so, with exactly what options?I'm using CentOS 5.5. dmesg: Linux version 2.6.18-194.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat4.1.2-48)) #1 SMP Fri Apr 2 14:58:14 EDT 2010.
Unfortunately I don't remember exactly what command I used to test the integrity of the mondo image, and http:[url]....the source of the instructions, is currently down.
how to resolve kernel panic error at my remote RHEL5 server side. i know normal solution through cd &n/w boot and enter in rescue mode and using mkinitrd but with out this how to solve.
View 2 Replies View Relatedwe are facing the problem related to Kernel panic in linux . Could u send me details of kernel panic . Why the kernel panic occur and how to resolve this problen
View 2 Replies View RelatedI have an old server based on Tyan Thunder LE-T (s2518UGN),: embeeded VGA - ATI Rage XL two Intel Pentium III (PGA370) processors at 1133 MHz 512 MB ECC RAM embeeded Dual Intel 82559 LAN controllers 10/100Mbps embeeded Adaptec 7899W NT Ultra160 SCSI Adaptec SCSI RAID 2000S (PCI card to support for bootable RAID 5) 3x Seagate HDD ST318438LW connected in RAID 5 instaled OS was RedHat 8 rack case (2U) It worked fine but one disk from array failed.
I provided backup and decided use two mirrored SATA disks Seagate ST3500320NS HDD ES.2 500GB with PCI SATA controler Kouwell KW-5125 (SiI3124 chipset) inserted through PCI riser card (2U case). (I can't replace old SCSI disk because it isn't available any more.) I disabled SCSI controler in BIOS and removed Adaptec SCSI RAID 2000S PCI card. I inserted PCI SATA controler connected both SATA disks and configured mirroring.
[Code]....
Hardware config as following:
MB: Gigabyte g31m-s2l
[URL]
CPU: Intel PD 2.8G
RAM: Kington DDR2 800 512Mx1
HDD: Seagate 80G IDE x 1
Tried to use all netinstall, DVD install, i386, x86_64 and install parameters (like linux text, noapic, nomsi, nousb etc) of CentOS 5.3 install disk, after press 'enter' to start install, it shown kernel panic error and the system halt. From the error message, i just found maybe some error related to 'Intel i915'.
But when use CentOS 4.6 install DVD, the installation can go smoothly and system run without any error (even can't find the lan card) After search past post, someone claimed that this motherboard can used to install CentOS 5.2. Does anyone had exp. on using the MB to install CentOS 5.3?
I have a system here that tends to have kernel panics during an linux installation, though I was able to perform a vista installation on the same hardware. Now I would like to ask what your suggestion for the cause of that problem is. Here a screenshot: [URL]
I suspect the hd to cause it:
-it is now over 7 years old
-smartctl displays over 16k read error and 0.5mio seek errors
(or are such high numbers normalfor that old disks?)
-the panic contains the string bad_area in the trace
But it might also be a RAM error, since the trace contains sth about page_fault and vista installs on the very same hdd and does not report any error messages (concerning the hardware, and I heard win doesn't complain about a bad RAM).
It is my first try getting Linux on my pc which is an Acer Aspire Z5610. This is not the first time for me when I am getting an Kernel Panic error on this computer.
I looked up google hoping to find an answer and I found out that it may be my BIOS's fault. I currently have Windows 7 on this PC. I have a Phoenix BIOS and there is an update for it called "Bios Linux" on the official Acer support website.
OK, after this short introduction, that's the error:
I really hope to get support for this problem as I can not literally install any other OS to this PC than Windows 7 because they fail with Kernel Panic.
Tried other Linux Editions and even Mac OS Intel Edition and IAtkos V1 and V7 and they all give kernel panic.
I untared a few libs on the wrong server (that's the when you're supposed to start laughing!) and I corrupted my server. Everytime it boots up, I get the following error:
/sbin/init: relocation error: /lib/tls/libc.so.6: symbol _dl_out_of_memory, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference. Kernel panic - not syncing. Attempted to kill init!
I can I restore the original libs? I'm running RHEL 2.6.9-42 on a Proliant DL585.
Kernel Panic.
I am using
"HP Pavilion dvb 111x"
"AMD Turion X2"
"ATI RADEON Graphic Card"
And "RHEL5"
I am not register user of Redhat. I am trying to switch kernel form linux-2.6.18.X To linux-2.6.27.53. I had download source of kernel and install it as per README file. During installation everything was fair but as I am trying to boot from my new kernel it shows me "Kernel Panic" error. It Displays
" ide_generic :I/O resorce 0x1F0-0x1F7 not free.
ide_generic :I/O resorce 0x170-0x177 not free.
Redhat nash version 5.1.19.6 starting.
mount : Could not find filesystem. '/dev/root'
setuproot : mounting /dev failed : no such file or directory
setuproot : mounting /proc failed : no such file or directory
setuproot : mounting /sys failed : no such file or directory
switchroot : mount failed : no such file or directory
Kernel Panic not Synching:
attempt to kill init! "
I have PC with motherbord P5KPL-AM (latest ver. BIOS), and i want installation CentOS 5.2.But can't screen attaching....
View 5 Replies View RelatedAfter update to 5.3 and reboot I got this error. googling for it I found that it is a known bug in kernel REHL 5.3 and there is also a patch for it [URL]. I am very new to linux, so how to apply, or just wait for a new kernel?
View 4 Replies View RelatedI recently bought a Toshiba Portege M200 tablet PC and it's caused me no end of grief to load linux on it. I would like to load CentOS 5.x (because my hosting company uses it and I will be able to learn as I run it).
Here are my resources:
I found internet resources to create a boot disk that enables me to see my 8GB Sony USB flash drive via DOS. It works nicely.
I have a laptop drive to USB converter and can access the hard drive directly from my Win XP desktop. I have PowerQuest's Partition Magic Pro (v8.0) and can make Ext2 and Ext3 partitions at will. I have also loaded a program that allows Windows XP to read and write from Ext2 and Ext3. It works well.
I have tried loading boot images from PXE. This option is mostly out because it seems to be a couple levels past my competency (I haven't been able to get it to work).
Given those resources, what's the best way to load either the CentOS live CD... or some other approach?
Since I wrote this, I figured out how to make a boot floppy that can start an external USB CD-ROM/DVD drive. Here are the files on the floppy:
Here's the contents of my config.sys:
Here's the contents of my autoexec.com:
I can boot to the CD and launch linld.com. The problem is that I keep getting a kernal panic message, saying that a memory block could not be addressed. And when I add the following part to the line above: "initrd=d:isolinuxinitrd.img" the install fails and reboots. I have tried to expand the initrd.img and it appears... blank?
i have a problem with my graphic card when i put in my PC and start on my PC, i have panic kernel i give you the message
View 2 Replies View RelatedI can cause the kernel to panic immediately with the following command. lvcreate --snapshot --name Snap --extents 100%FREE VolGroup00/LogVol00 The last line of the panic message is "<0>Kernel panic - not syncing: Fatal exception" If I create a snapshot of any other volume it works just fine. It only panics on LogVol00 which is my root fs.
I'm running 5.4 after update from 5.3. It didn't work with 5.3 either. This is a 32-bit guest running in VMWare Server 2.0.1 which is running on FC10 x86_64. I've tried the guest in both UP and SMP (2 cores) modes and observed no difference.