Bug 485027

Summary: Fedora won't boot with the newest kernel if root is on an lvm volume
Product: [Fedora] Fedora Reporter: Thomas Schweikle <tschweikle>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: rawhideCC: james, kernel-maint, kmcmartin, quintela
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-08 23:53:47 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:
Attachments:
Description Flags
mkinitrd run for the newest kernel. none

Description Thomas Schweikle 2009-02-11 08:44:30 UTC 
Description of problem:
Fedora won't boot with the newest kernel if root is on an lvm volume

Version-Release number of selected component (if applicable):
vmlinuz-2.6.29-0.93.rc3.git10.fc11.i586
vmlinuz-2.6.29-0.99.rc4.git1.fc11.i586

How reproducible:
Always.

Steps to Reproduce:
1. Install Fedora 10
2. Upgrade to Fedora 11 alpha
3. Replace the kernel
  
Actual results:
New kernel installed does boot, but then can't find device
"/dev/VolGroup00/LogVol00" and
"/dev/VolGroup00/LogVol01".
The system ist stopped.

Expected results:
Booting and finding "/dev/VolGroup00/LogVol00" and "/dev/VolGroup00/LogVol01". Continuing boot.

Additional info:
It looks to me, as if the modules for lvm2 are within the initrd, but there is never a vgscan done activating VolGroup00. Result since this isn't activated, devices are never created and can't be found by the kernel --- even if the modules are loaded!

I am not shure this being a kernel or some script problem.
Comment 1 Thomas Schweikle 2009-02-11 08:50:44 UTC 
Created attachment 331533 [details]
mkinitrd run for the newest kernel.

What "mkinitrd -v -f initrd-2.6.29-0.99.rc4.git1.fc11.i586.img 2.6.29-0.99.rc4.git1.fc11.i586" includes into the initrd-image.
Comment 2 Kyle McMartin 2009-02-27 13:56:41 UTC 
There were some issues with waiting for the lvm devices to show up earlier... Can you try booting with "boot_delay=5"? Is it still an issue?
Comment 3 Thomas Schweikle 2009-03-03 08:28:58 UTC 
Yes, this does not change anything. Even setting it to 30s does not help. Afaics the problem is, the vgscan command is not issued the time root is expected to be mounted ...
Comment 4 Thomas Schweikle 2009-04-08 23:53:47 UTC 
Since the latest upgrades the bug is gone. Seems solved!