Red Hat Bugzilla – Bug 453813
installer plays with partition ordering
Last modified: 2008-08-06 15:35:38 EDT
I'm trying to set up a couple of disks in RAID1, each with a set of partitions.
I tried the 'clone disk' option, but the partitions on sdb ended up in a
_different_ order to those on sda.
I cloned it again to sdc, since I happened to have a third matching disk. That
seemed OK -- at least sdb matched sdc. But I'd forgotten to add a swap
partition. And now I've added swap, all three disks are different.
It would be useful if the installer gave us the option of _numbering_ partitions
as we want them. But getting them in the same order on each disk, when the set
of partitions is identical, would be nice. Getting three _different_ answers for
the same set of partitions is particularly impressive :)
I have four partitions on each disk, and I want them all to be primary
partitions. I'm a little surprised that it defaults to using an extended
partition when there are only four. When I edit a partition and select 'force to
be a primary partition', the installer seems to _forget_ that the partition in
question was already restricted to a certain disk, which I had set earlier while
trying to sort it out.
Created attachment 310835 [details]
And now it's doing a RAID resync on the whole terabyte. While sitting at the
'install finished. you can reboot now' screen. Is that just a limitation of RAID?
*** This bug has been marked as a duplicate of bug 410011 ***