Bug 171671

Summary:	LVM volume groups not found on recent kernels
Product:	[Fedora] Fedora	Reporter:	Chris Hubick <chris>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	wtogami
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-25 08:46:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chris Hubick 2005-10-25 03:45:38 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
I am running FC4 under VMware 5.

If I attempt to boot with either of the most recent two FC4 kernels (kernel-2.6.13-1.1526_FC4, kernel-2.6.13-1.1532_FC4), I get the following:

---
Red Hat nash version 4.2.15 starting
  Reading all physical volumes.  This may take a while...
  No volume groups found
  Unable to find volume group "VolGroup00"
ERROR: /bin/lvm exited abnormally with value 5 ! (pid 331)
mount: error 6 mounting ext3
ERROR opening /dev/console!!!!: 2
error dup2'ing fd of 0 to 0
error dup2'ing fd of 0 to 1
error dup2'ing fd of 0 to 2
switchroot: mount failed: 22
Kernel panic - not syncing: Attempted to kill init!
---

(I typed out the above from the panic screen)

Reverting to kernel-2.6.12-1.1447_FC4 allows the system to boot again.

Help appreciated.  Will try to provide more info if someone tells me what is needed.  Thanks.


Version-Release number of selected component (if applicable):
kernel-2.6.13-1.1526_FC4, kernel-2.6.13-1.1532_FC4

How reproducible:
Always

Steps to Reproduce:
Boot with recent kernel.

Additional info:

Comment 1 Dave Jones 2005-10-25 08:46:33 UTC


*** This bug has been marked as a duplicate of 169610 ***