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 RepliesI'm unable to boot the LFS-6.6 which i've built on a vmware workstation 6.5. i had no trouble in installing all the packages and have managed to run all the test suites successfully w.r.t stable LFS-6.6. while booting i get 'kernel panic' and it says unknown device /dev/sda1 and unknow block (0,0). i've only one primary partition without any swap partition. i've a label assigned to /dev/sda1 and have included it in my fstab file. device.map shows 2 entries:
One for the floppy and the other for my harddisk which is- hd0 /dev/sda. this is for the 2nd time i'm stuck at a point after perfectly installing all the stuff as mentioned in the LFS-6.6 book. i've also noticed on this website the many users have similar type of issue. it would be great if somebody could help me.
note: while configuring the linux, i've inbuilt everything required for my system, including support for ramfs and other required filesystems, scsi driver etc.
My host machine is on a intel core 2 duo processor. my virtual scsi hard disk is 3 GB in size and is a ext3 fs. scsi is configured with LSI Logic which is recommended by vmware while adding an hard-disk.
I recently started to use Ubuntu in VWware player on my windows-XP. I installed ubuntu 10.04 few days ago, It was working fine.
Yesterday, I compile a new kernel, kernel 2.6.33 in my vmware ubuntu 10.04. Everything went well till I did reboot. before reboot I use the command "update-grub" to make it compatible to the new kernel. BUT... after rebooting, I have a problem in loading a grub correctly. it gives me following message " [2.149136 ]kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0)" and I can not proceed further. I have my all data on it. I also tried to boot it from live CD but unfortunately, I can't mount the hard disk on it in order to get those data from my old Ubuntu set up.
I can install VMware Server 2.0.1 on CentOS 5.3 (32-bit and 64-bit) perfectly. However, I can't access Server's web interface by going to port 8222 on the machine's IP address. When CentOS 5.3 (32 or 64-bit) is loading, I am greeted with this message "VM communication interface socket family: vsock: no version for "VMCIDatagram_Send" found: kernel tainted." I assume this is the reason why I can't access my Server through a web browser. How do I correct this? Is there a package I need to install on CentOS prior to installation of Server 2.0.1?
It's strange, because I can install 2.0.1 on Ubuntu Server 8.10 with absolutely no problem and access its web interface. So I think this might be a CentOS-specific issue I've uncovered.
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 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.
I 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?
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 Replies View RelatedI 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.
I am getting :
exec of init (/sbin/init) failed!!! : 2
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init! My server is at remote end which I access through Public IP.
I got a CentOS server + KDE from a server (which I had no contact until now), he had 2 HD's one for the system and another for files.
I brought the HD system home to try to make it run on a virual machine (VMware) so I can do some testing before you put in practice.
But already converted the VMware HD to the system, it tries to start but it shows some errors and in a message "kernel panic - not syncing: attemped to kill init"
I think the drivers are correct, has edited the file "/ etc / modprobe.conf" edited these entries equal to another I installed CentOS on VMware.
alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptspi
ata_piix alias scsi_hostadapter2
Look at the picture attached the full error.
Link to large image
Link to large image
I have a situation where there are no logs in /var/log/messages and this has happened the second time during two weeks.
Snapshot of the screen was taken when this happened and the server was restarted. Since it's a time sensitive matter.
Snapshot:[url]
I got the following error after compiling kernel version 2.6.38.2 from sources with this Howto:[URL].. Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
[Code]...
I've been trying to track this kernel panic down for the last few days on this system... I believe it might be autofs/nfs related, but I'm not 100% sure.
Here is the dump in /var/log/messages:
We have a server running CentOS 5 Linux 2.6.18-128.1.16.el5xen #1 SMP Tue Jun 30 06:39:23 EDT 2009 x86_64 x86_64 x86_64 GNU Linux. We've seen at random times that the server will just reboot and nothing is logged in messages. I tried to enable kdump but was only able to get a 5.4 gig dump since our /var directory is set to 10GB. Here is the messages I see before and after the server restart. I had thought that when a kernel panics, it is supposed to halt the system and not reboot it. My /proc/sys/kernel/panic is set to 0. I can run an update but want to have some sort of idea what is causing the issue and if the update will fix anything.
May 13 20:05:22 hlotmt01 xinetd[3609]: EXIT: bpcd status=0 pid=1071 duration=1(sec)
May 13 20:05:22 hlotmt01 xinetd[3609]: START: bpcd pid=1072 from=10.203.1.1
May 13 20:05:23 hlotmt01 xinetd[3609]: EXIT: bpcd status=0 pid=1072 duration=1(sec)
[code]....
I have an Intel i7 with CentOS x64 installed, with the intention of using it as the host O/S with VMWare Workstation to run a number of virtual machines. I had this all working until the kernel was updated to 2.6.18-164.11.1.el5, Now I can no longer start any VMs. I have tried reinstalling CentOS, updating it first, then installing VMWare Workstation - no different. I have tried running as root - no different.
Is anyone else aware of this problem? Does anyone else run VMWare on CentOS x64?
2.6.18-194.8.1.el5xen is the reported kernel that I'm running while the headers that are installed are listed as 2.6.18-194.8.1.el5-i686. I assume these are the same, or at least close enough that it shouldn't matter.
However, when I run vmware-config-tools.pl to configure it it says it cannot find the kernel headers. I've tried pointing it to /usr/src/2.6.18-194.8.1.el5-i686/ and /usr/src/2.6.18-194.8.1.el5-i686/include (not sure which of the two I'm supposed to do as online instructions contradict one another) it says that is invalid and there seems to be no way to force it since it just complains without letting me use it anyway. What can I do? Running centos 5 btw on vmware workstation 7.
I'm having a strange problem on some of our Debian servers. It all started about three weeks ago when we moved our virtual environment (VMWare ESX3) from a SAN to a NAS (NetApp). At first I thought it had to do with that move but since the other 9 servers are working perfectly I eliminated that idea. For over a year all 12 Debian 5 servers have been working great without mentionable failures. All servers are (where) up to date with the latest patches. About three weeks ago I started having kernel panics with the following message on three of our servers:
Code:
Code: Bad EIP value
EIP [00000000] 0x0 SS:ESP 0068:f6d7da18
Kernel panic - not syncing: Fatal exception in interrupt and other times it looks like just a dump of hexadecimal data. The only difference between those 3 servers is that they have several mounted shares connecting to the NAS using CIFS. So I was thinking that it might have to do with an update of some kind in regards to smb. I recovered an image from a month ago, before the troubles began, copied over the data and MySQL databases and configured the 'old environment with recent data' exactly the same with MySQL master-master replication, document synchronization and load balancing. This task I performed last night (no other way since it's a production environment). Up to this time neither of the two 'restored' servers had a kernel panic. The one that has not been restored is having one at random about every hour and a half. Following are the different versions between the 'at this time' working server(s) and the failing one:
Code:
FAILINGWORKING
samba-common 2:3.2.5-4lenny122:3.2.5-4lenny9
smbclient2:3.2.5-4lenny122:3.2.5-4lenny9
smbfs 2:3.2.5-4lenny122:3.2.5-4lenny9
[Code]...