[CentOS] Problems with building a complete kernel

Mark Hull-Richter mhull-richter at datallegro.com
Mon Jan 29 22:57:49 UTC 2007


Yes.

Here is what happens:

Booting (CentOS 2.6.9MHRsmp)'
kernel direct mapping nodes[?] up to 10100000000 @ 8000-d000
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.9MHRsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
[Linux-bzImage, setup=0x1400, size=0x190795]
initrd /initrd-2.6.9MHRsmp.img
[Linux-initrd @ 0x3706300, 0x18caf6 bytes]

.
Decompressing Linux...done
Booting the kernel
audit (1170068438.664:0): initialized
Red Hat nash version 4.2.1.8 starting
Reading all physical volumes. This may take a while...
No volume groups found
Volume group "VolGroup00" not found
ERROR: /bin/lvm exited abnormally! (pid 206)
mount: error 6 mounting ext3
mount: error 2 mounting none
switchresest: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init

Then the system halts.  I'm using the same config file as the installed CentOS 2.6.9-42.0.3, and here are my /etc/fstab and grub.conf contents:

[root at localhost linux]# cat /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/hda /media/cdrecorder auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
/dev/fd0 /media/floppy auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0

[root at localhost linux]# cat /etc/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=2
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
password ****************************************************
title CentOS (2.6.9MHRsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9MHRsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9MHRsmp.img
title CentOS (2.6.9MHRsmp2)
root (hd0,0)
kernel /vmlinuz-2.6.9MHRsmp2 ro root=/dev/sda1 rhgb quiet
initrd /initrd-2.6.9MHRsmp2.img
title CentOS (2.6.9-42.0.3.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.3.ELsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9-42.0.3.ELsmp.img
title CentOS (2.6.9-42.0.3.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.3.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9-42.0.3.EL.img
title CentOS-4 x86_64 (2.6.9-42.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.ELsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9-42.ELsmp.img
title CentOS-4 x86_64-up (2.6.9-42.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9-42.EL.img

Any hints, suggestions, comments, etc. would be most welcome.

Thanks.

mhr

-----Original Message-----
From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Marcin Mazurek
Sent: Saturday, January 27, 2007 1:03 AM
To: CentOS mailing list
Subject: Re: [CentOS] Problems with building a complete kernel

Mark Hull-Richter (mhull-richter at datallegro.com) napisał(a):

> I haven't actually made any changes to the kernel yet - I need a working
> build, hopefully one that matches my current installation, but a working
> build to start.  (Otherwise I won't know if the kernel I'm running and
> one I've modified contain anything I don't know about....)
> 
> I used the config that the installed version had as my base, and I don't
> think I changed anything.  I ran make menuconfig and set the version to
> something different, then ran make oldconfig to see what changes were
> needed (none), then built.  In theory, if lvm support was in the
> installed kernel, it should have built into my new one, right?
> 

Do You have an initrd file for new kernel? If not You should create one
with mkinird.


hth

-- 
Marcin Mazurek

http://www.netsync.pl/  -  ::::  -  nic-hdl: MM3380-RIPE
GnuPG 6687 E661 98B0 AEE6 DA8B  7F48 AEE4 776F 5688 DC89

_______________________________________________
CentOS mailing list
CentOS at centos.org
http://lists.centos.org/mailman/listinfo/centos



More information about the CentOS mailing list