Bug 649768
| Summary: | kickstart --grow is not supported for Raid Partitions | ||
|---|---|---|---|
| Product: | [Retired] Fedora Documentation | Reporter: | Anthony B <anthony> |
| Component: | install-guide | Assignee: | Petr Bokoc <pbokoc> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ruediger Landmann <rlandman+disabled> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | devel | CC: | acaleechurn, bugzilla, dcantrell, fullung, jon.swanson, k.georgiou, mmitchell, pbokoc, rabidfly, redhat-bugzilla, rlandman, strobert |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-07-31 14:31:04 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: | |||
|
Description
Anthony B
2010-11-04 14:18:29 UTC
The documentation needs to be updated. --grow is not supported for RAID partitions as of F14. I will update http://fedoraproject.org/wiki/Anaconda/Kickstart appropriately, but the changes will need to get pulled into the website docs too. Hello, Thanks for your reply. This option was very importante. Is there an another option in kickstart to do the same things (grow a raid partition) ? Best Regards, Anthony B Dear Fedora dev team, Would it be possible for you to document why --grow on RAID partitions is not available anymore? This is really strange and we will not be able to automatically deploy Fedora on computers anymore. It worked in F13 and prior and stopped working in F14. An equivalent workaround would be greatly appreciated. Thank you for your time, Mathieu M Also agree that this is very useful functionality, and remain a little confused as to why it was removed it F14. For reference, this has been raised at least once elsewhere: https://bugzilla.redhat.com/show_bug.cgi?id=659700 We really need a straight forward automated way to continue to kickstart our servers. This either needs to be re-implemented or re-jigged. For now, I'm not using Fedora anymore because of this issue. Because of this issue, I've begun migration to Scientific Linux 6. Once the downstream hits this issue and SL as consequence: I'll (unfortunately) have to look at other distros all together. Very disappointed. Dan Argh. It's strange that such a useful feature has been removed. The RHEL 6 documentation still states that --grow works but had no luck with RHEL 6 and CentOS 6. Extract from http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-options.html#s2-kickstart2-options-part-examples clearpart --drives=hda,hdc --initlabel # Raid 1 IDE config part raid.11 --size 1000 --asprimary --ondrive=hda part raid.12 --size 1000 --asprimary --ondrive=hda part raid.13 --size 2000 --asprimary --ondrive=hda part raid.14 --size 8000 --ondrive=hda part raid.15 --size 1 --grow --ondrive=hda part raid.21 --size 1000 --asprimary --ondrive=hdc part raid.22 --size 1000 --asprimary --ondrive=hdc part raid.23 --size 2000 --asprimary --ondrive=hdc part raid.24 --size 8000 --ondrive=hdc part raid.25 --size 1 --grow --ondrive=hdc I have found a workaround if you want to create LVM partitions on top of a RAID device with the --grow option. My original kickstart below fails but with a small modification it works clearpart --drives=sda,sdb --initlabel # Raid 1 SATA config part swap --size=8192 --ondisk=sda part raid.01 --size 500 --asprimary --ondrive=sda part raid.02 --size 200 --grow --ondrive=sda part swap --size=8192 --ondisk=sdb part raid.03 --size 500 --asprimary --ondrive=sdb part raid.04 --size 200 --grow --ondrive=sdb raid /boot --fstype ext4 --device md0 --level=RAID1 raid.01 raid.03 raid pv.01 --fstype ext4 --device md1 --level=RAID1 raid.02 raid.04 # LVM configuration volgroup sysvg pv.01 logvol /var --vgname=sysvg --size=10240 --name=var logvol /tmp --vgname=sysvg --size=10240 --name=temp logvol / --vgname=sysvg --size=10240 --name=root The Kickstart will work if you allocate an initial size which is equal or greater than the total size of the logical volumes and then use --grow. # Raid 1 SATA config part swap --size=8192 --ondisk=sda part raid.01 --size 500 --asprimary --ondrive=sda part raid.02 --size 40960 --grow --ondrive=sda ***** Works part swap --size=8192 --ondisk=sdb part raid.03 --size 500 --asprimary --ondrive=sdb part raid.04 --size 40960 --grow --ondrive=sdb ***** Works Confirming this *severe* regression on CentOS 6 / RHEL 6 kickstart installations. The generated anaconda-ks.cfg is similarly broken by default. Tested your workaround, it appears to be effective. A very useful feature has been removed. Why? This makes Fedora realy unsable for unattended install. And in fact makes Fedora unusable for me at all. Being very disappointed about that and will change to another distribution. As per bug 659700, --grow is now supported for RAID0, but not other RAID devices. The F16 version of the guide will reflect this. A draft can be found at http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Installation_Guide/s1-kickstart2-options.html Removing myself for these bug components as I'm either no longer involved in that aspect of the project, or no longer care to watch this particular bug. Sorry if you are caught in a maelstrom of bug changes as a result! Removing myself for these bug components as I'm either no longer involved in that aspect of the project, or no longer care to watch this particular bug. Sorry if you are caught in a maelstrom of bug changes as a result! It is a bit distressing that the useful code was removed. FYI, it looks like somewhere between 6.0 and 6.3 in centos at least this has been addressed. I used my normal KS which follows the recommended practice by RedHat (based on the RH kickstart guide for RHEL 5 and 6) to use grow with the raid partitions. and it worked great on a centos6.3 server at home. I noticed this issue when trying our first physical rhel6 servers here at work last week. confirmed my home KS options over the weekend. going to try changing out our base rhels6 install here at work from 6.0 to 6.3 to see if it is addressed in RHEL as well. yes. rhel 6.3 looks good again. so looks like the code removed from 5.x to 6.0 was re-added sometime between 6.0 and 6.3. and Yes I get you can do a lot of this manually in %pre. we already do a bunch of stuff in %pre (single vs dual disks for raid, el5 VM disk alignment, etc) it is nice to the installer be able to do some of the work as well. |