Hide Forgot
I'm using a kickstart file to create partitions. I use a pre command to force the partition tables on all the 3TB drives to GPT. Now that I have GPT tables I can use grow to create partitions. This was a workaround discussed in other bugs on the subject. For example this works. part biosboot --fstype=biosboot --size=1 --ondisk=sda part /boot --fstype=ext4 --size=500 --ondisk=sda part raid.01 --size=30000 --grow --ondisk=sda part raid.02 --size=30000 --grow --ondisk=sdb part raid.03 --size=30000 --grow --ondisk=sdc raid pv.01 --level=0 --device=md0 raid.01 raid.02 raid.03 BUT I need to create a RAID5 partition so I need to specify the size of the RAID partitions. Grow is not allowed for RAID5. This does not work. part biosboot --fstype=biosboot --size=1 --ondisk=sda part /boot --fstype=ext4 --size=500 --ondisk=sda part raid.01 --size=2861084 --ondisk=sda part raid.02 --size=2861084 --ondisk=sdb part raid.03 --size=2861084 --ondisk=sdc raid pv.01 --level=5 --device=md0 raid.01 raid.02 raid.03 I get an error that tells me /boot can not be stored past 2GB on the drive (this seems like a bad error that doesn't reflect the problem). If I try to create the same partition in the install GUI it says "could not allocate requested partitions requested size exceeds maximum allowed" Can we remove this limit? Or even better allow RAID5 on grow-able partitions. Another interesting note on this bug. I only get this error on sda I can create a large RAID partitions on sdb and sdc so this seems to be an error still left from the old mbr code. There error also seems to only be in creating the partition not using it. If I monkey around and create the partition on sda using a liveCD then tell the GUI to use existing partitions it works OK.
Please attach the following logs from the shell on tty2, individually and as type text/plain, to this report: /tmp/anaconda.log /tmp/storage.log /tmp/syslog Also, please attach you kickstart config file. Feel free to remove passwords, &c, but otherwise do not modify or edit the file.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.