Bug 512555 - mkinitrd fails to create a correct initrd for nvidia fakeraid devices with lvm on top
Summary: mkinitrd fails to create a correct initrd for nvidia fakeraid devices with lv...
Keywords:
Status: CLOSED DUPLICATE of bug 506189
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: 11
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-19 02:51 UTC by S.A. Hartsuiker
Modified: 2009-07-27 08:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-27 08:38:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
small patch to fix not finding the devices that house lvm in case of fakeraid (514 bytes, patch)
2009-07-19 02:53 UTC, S.A. Hartsuiker
no flags Details | Diff

Description S.A. Hartsuiker 2009-07-19 02:51:33 UTC
Description of problem:
During startup the startup process is aborted saying that the device required to mount /boot cannot be found.

Version-Release number of selected component (if applicable):
mkinitrd-6.0.87-1.fc11.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install anaconda on an nvidia fakeraid device, in my case mirrored and use lvm on top of that.
2. Reboot
3. 
  
Actual results:
A failed boot. During the ''interactive'' part of the initrd it fails after which I have to give the root password and get the recovery prompt.

Expected results:
Normal boot

Additional info:
See the email thread starting with https://www.redhat.com/archives/fedora-devel-list/2009-July/msg00989.html

Comment 1 S.A. Hartsuiker 2009-07-19 02:53:28 UTC
Created attachment 354267 [details]
small patch to fix not finding the devices that house lvm in case of fakeraid

Comment 2 S.A. Hartsuiker 2009-07-20 16:28:28 UTC
Hmm, this appears to be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=506189

Comment 3 Hans de Goede 2009-07-27 08:38:08 UTC
Hi,

Yes this indeed is a duplicate of bug 506189, given that apparently more people
are being hit by 506189 then I thought, I'm going to do an F-11 mkinitrd update
with the fix for this, bug 506189 will be used to track this further.

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


Note You need to log in before you can comment on or make changes to this bug.