Bug 500322
Summary: | dmraid cannot handle disks with GPT | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Winfrid Tschiedel <Winfrid.Tschiedel> | ||||
Component: | mkinitrd | Assignee: | Hans de Goede <hdegoede> | ||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | low | ||||||
Version: | rawhide | CC: | agk, bmr, dwysocha, hdegoede, heinzm, katzj, lvm-team, mbroz, pjones, prockai, wtogami | ||||
Target Milestone: | --- | Keywords: | Reopened | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-05-19 07:49:24 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
Winfrid Tschiedel
2009-05-12 09:26:07 UTC
dmraid is not going to support GPT partitioning. Please use "kpartx -a /dev/mapper/pdc_cbbgheicjb" instead. The referenced bz#464553 is about partitioning support in anaconda, which causes utilizing kpartx for activation. please reopen this issue - it maybe true, that this is no dmraid problem, nevertheless there should be no restriction on dmraid to use GPT labels, which is important, because the max. size supported by old style partition tables is 2 TB. Please assign this issue to the right product(s). All I expect is that I can install a linux distribution on a SATA RAID using GPT - and should not care about any commands . Winfrid It'll be solved in anaconda/mkinitrd, hence my comment #1. Winfrid, given what Heinz said in comment #1, this is an mkinitrd bug. Bug 464553 seems to only track the anaconda part of this, and given your description (installs properly but doesn't boot), combined with the fact that mkinitrd in Fedora atm is not using kpartx, there clearly also needs to be done some work on the mkinitrd side of things. I'll take care of this and provide you with an updated mkinitrd to test. In the mean time I'm re-opening this to track the mkinitrd side of this, and changing the component to match. Created attachment 344328 [details]
Updated mkinitrd which hopefuly fixes this
Winfrid,
Here is a fixed mkinitrd script can you give this a try please and see if it
fixes things?
To use this:
1) install F-11
2) boot the F-11 installer into rescue mode
3) copy this mkinitrd to /mnt/sysimage
4)
chroot /mnt/sysimage
5)
./mkinitrd -f /boot/initrd-<kernelver>.img <kernelver>
You can get the first <kernever> by using the tab key, then fill in the second
to be exactly the same as the first. After this you have a new initrd which should use kpartx
To verify this do:
zcat /boot/initrd-<kernelver>.img | cpio -i init
less init
You should now see the use of kpartx in the initscript just extracted from
the initrd.
6) Reboot, and hopefully things work now.
Please let us know if this fixes dmraid with GPT, thanks.
Hello Hans, You did a great job - for my system ( Fujitsu Primergy rx220 with Promise Raid TX150 ) it works. Next open item is to place the boot-partition on a partition >= 4 and to use the boot-sector in the boot-partition - I know already that this does not work with grub, but I have no experience with grub2. I would like to test this, but I need for this help from somebody with grub2 experience. Have a nice evening and thanks again, Winfrid (In reply to comment #6) > Hello Hans, > > You did a great job - for my system ( Fujitsu Primergy rx220 with > Promise Raid TX150 ) it works. > Ok, thanks for testing, the fix in the attached mkinitrd has been commited to mkinitrd's git tree: http://git.fedorahosted.org/git/?p=mkinitrd;a=commitdiff;h=b625d07cb873e7c148442dd03c5b43263a20bf12 And thus will be part of the next mkinitrd release (6.0.85-1), not sure if that will make F-11 final though. > Next open item is to place the boot-partition on a partition >= 4 > and to use the boot-sector in the boot-partition - > I know already that this does not work with grub, but I have no > experience with grub2. I would like to test this, but I need for this help > from somebody with grub2 experience. > Hmm, this will need to be tracked in a new bug, no idea when we're going to switch to grub2 though (it won't be soon). |