I just joined the mailing list after seeing this e-mail in the mailing list archives. Does anyone have any idea as to why this may be happening? I am having this exact problem on a Dell Poweredge 1855.
Jeremy Carrigan
****************************************Original E-mail from Mailing List Archives********************************************
* To: <centos@xxxxxxxxxx mailto:centos@DOMAIN.HIDDEN > * Subject: [CentOS] mount problem on LVM2 w/ kernel-2.6.9-42.0.2 * From: "Heitor A.M. Cardozo" <heitor@xxxxxxxxxxxxxxxxxxxx mailto:heitor@DOMAIN.HIDDEN > * Date: Fri, 1 Sep 2006 16:55:58 -0300 * Delivered-to: centos@xxxxxxxxxx mailto:centos@DOMAIN.HIDDEN
________________________________
size=2 width="100%" align=center> Recently I update a server running CentOS 4.3 to kernel 2.6.9-42.0.2. After the update it had a problem to mount LVM partitions, showing the follow error during boot:
No volume groups found Activating logical volumes Unable to find volume group "lvm1" ERROR: /bin/lvm exited abnormally! (pid 199) Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init!
Root partition is a LVM2 on Software RAID.
With old kernel (2.6.9-34.0.2) the system boot normally.
Any idea what is error?
Best regards
Heitor Augusto
Carrigan, Jeremy wrote:
Recently I update a server running CentOS 4.3 to kernel
2.6.9-42.0.2. After the update it had a problem to mount
LVM partitions, showing the follow error during boot:
No volume groups found
Activating logical volumes
Unable to find volume group "lvm1"
ERROR: /bin/lvm exited abnormally! (pid 199)
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
Root partition is a LVM2 on Software RAID.
With old kernel (2.6.9-34.0.2) the system boot normally.
do you have any custom drivers that are missing in the new kernel ? ( eg. what drive interface controller are you using ? )