Red Hat Bugzilla – Bug 806113
Custom partitions on ppc64 result in unbootable partition layout
Last modified: 2012-09-06 00:40:23 EDT
When a user specifies custom partitions on ppc64, our rhts_partitions snippet will produce the following partition commands in the kickstart:
> part None --fstype 'PPC PReP Boot' --size 8
> part /boot --fstype ext3 --size 200 --recommended
> part / --fstype ext3 --size 1024 --grow --asprimary
> part swap --recommended --asprimary
> # User's custom partitions appear here
In this case the /boot partition may end up as a logical partition, which will fail to boot:
> /vdevice/v-scsi@30000002/disk@8100000000000000:-1,/etc/yaboot.conf: Unknown or corrupt filesystem
> Can't open config file
This bug prevents a bunch of file system testings which need custom partition on ppc64 running in beaker. I bumped the severity to high.
I'll be great and helpful to have this bug fixed.
ps. seems s390x host with custom partition cannot boot in beaker either
A fix for bug 725418 should prevent the ppc install from completing with /boot on a logical partition. So anaconda should not allow /boot on logical on ppc, but beaker should also not insert --asprimary unless it is actually requested.
On Gerrit: http://gerrit.beaker-project.org/1287
Beaker 0.9.3 has been released.