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.
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
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]...
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
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)'
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.
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.
After 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?
I 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 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.
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
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
I'm setting up a raid 5 on several hard disks with a layer of lvm on top for good measure.I know the recent kernels support growing software raid, but since centos runs 2.6.18, I wanted to make sure it'll work. Does the centos kernel support growing raid devices?
I've just installed for the first time Centos 5.3 on my machine. everything goes in harmony except : 1-when I power off, everything seem to be terminated smoothly but at last I get this annoying error "kernel panic not syncing : fatal exception" 2-my Ethernet card won't get operational; its detected already but when I try to activate it I get this error " eth0 seems not to be present. Initialization delayed"
System Information:
System Manufacturer: Gigabyte Technology Co., Ltd. System Model: 965P-DS3 BIOS: Award Modular BIOS v6.00PG Processor: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2 CPUs), ~2.4GHz
First off let me say thanks psy_unix and fuji, the pci=nomsi allowed me actually finish install on my laptop. (Read this post)
Problems do not stop here however...Now, when it reboots after install all I get is a "Machine Check Exception" followed by a "Kernel Panic". I had to switch back to Vista Home finally (not happy about that).
I just bought it and it runs happily under Vista, I just don't run happily under Vista.
I have recompiled a few kernels, but all on 32bit systems so not sure if that has anything to do with it.
Running Arch Linux 64bit, most recent version.
Kernel Output:
Code:
My first thoughts was that it might be my grub bootloader configuration, so had a big play around with that but it didn't fix it. Also made sure support was built for filesystems. However almost all that Fstab mounts are ext3 anyway, and certainly the root and /boot are. Now thinking it may be a memory error so will run a check when I shutdown.
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.
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
I've had a Centos 5.3 zimbra mailserver set up for about 3 months now.Every 7-10 days or so, the system will do a kernel panic and I've been putting off its resolution due to other matters.I'm now ready to look into it but I have two issues :
1) No logs.
So far, I've manually rebooted when a kernel panic occured and could look at the panic printout and write down relevant info. But since I wanted more info than I had written down, I went hunting in the logs for the kernel panic event (one happened earlier today) but, to my surprise, I noticed the system doesn't log the kernel panic at all. Kdump is currently disabled as I'd like to keep all available memory available to the system but I was under the impression it would log the kernel panic message regardless but would simply leave out more advanced diagnostic information.How would I make sure the kernel panic is logged so I can have more info about it ?
2) The actual panic.Here's a snippet of what's appearing when the kernel panics :
I've also seen f793bee4 instead of the highlighted part above but everything else is always the same from the times I've seen (as I haven't always had the chance to be around when a panic occured).I'm looking further into it at this point but early research seem to indicate this could be a memory issue. I'll run memtest next weekend to check that out (since I don't want to take the system offline for any length of time during office hours) but people here might have other theories based on what I've put up so far. The system has all of the latest patches and updates and is running only what I need as far as software goes (zimbra server + prerequisites, x + GNOME (not loaded on startup), firefox and vnc for windows RDP access). My system also uses a software RAID1 array (boot = md0 and / = md2 with swap files not being mirrored as there's no need to).
PS : In order to further troublehsoot by myself before posting here, I've tried to enable kdump to see if kdump is the culprit for the missing logs but I'm also having an issue with it. I'm getting a "No kdump initial ramdisk found" and "mkdumprd: failed to make kdump initrd" messages at startup. I'm thinking this might be because of my raid array ? I've found an old bug report regarding one of those error messages on centos 5.2 but it was supposedly fixed in the 30 version by RH and I'm using the latest one (56).
