Red Hat Bugzilla – Bug 10061
Last modified: 2008-05-01 11:37:54 EDT
I used graphical redhat installation,
when partitioning my HDD I noticed the following bugs,
1) I created several ( probably 10 ) ext2 and fat partitions ,
then I changed my mind, deleted all partitions,
then created two partitions, but they were named /dev/hda11 and
/dev/hda12 instead of /dev/hda1 and /dev/hda2.
again I deleted all partitions and created one - it was named /dev/hda11
I didn't proceed with installation , just rebooted.
2) Such a situation :
I create new ext2 partition, it becomes /dev/hda7, then
I create another ext2 partition , but : the first partition becomes
/dev/hda8 and the new second partition becomes /dev/hda7
I don't exactly remember mount points , but probably they were / and
/home.( sizes ~1,5Gb and ~300Mb accordingly)
I didn't proceed with installation , just used Partition Magic.
3) No any warning displayed when I created partition with mount point
/boot far beyond the 8,4 Gb limit.
I tried testing these issues against the latest internal (rawhide) release:
1) I could not reproduce problem number 1 on a system with a single drive in
which I created 12 partitions in disk druid, then deleted them all, then
started creating new partitions. The new partitions were numbered
2) In disk druid the partitions are allocated based on several weights. For
example, /boot will try to be allocated before /opt. It is normal for the
partitions you create to change number. The pre-existing partitions will not
change their number, as expected.
3) When you create /boot with disk druid it enforces the 1024 cylinder limit (as
well as forcing /boot to be on one of the first two drives). Did the /boot
you used previously exist and you assigned it to /boot in disk druid? That
would be the only case where I could see that happening.
All of these issues were addressed and resolved in the 6.2 Red Hat Linux
Actually, just to clarify, 1 and 3 were addressed and resolved. Issue 2 is how
Disk Druid is supposed to behave, just as msf responded.