Bug 77266
| Summary: | Installer crashes when trying to partitioning LVM drives using kickstart file | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Danilo Aghemo <danilo.aghemo> | ||||
| Component: | anaconda | Assignee: | Michael Fulbright <msf> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Mike McLean <mikem> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 8.0 | CC: | denis.courtier | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2003-02-27 17:08:31 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: | |||||||
| Attachments: |
|
||||||
You are starting from the anaconda-ks.cfg that the installer creates? I took the original anaconda-ks.cfg, uncommented the #part line, the modifified the clearpart into a clearpart --all --initlabel and added a zerombr yes. Moreover, today, i made a try with no LVM support, just plain partition, using - -start, --end and --ondisk... their values has been taken by a previous manual installation. The installation failed saying theat it cannot use cylinder parameters. If you need I can post the incriminated kickstart file. Yes the ks file would be very helpful. Created attachment 86269 [details]
one of the many kickstart files i used to reproduce the problem
Thank you for the information we will try to investigate. If you try to give more 'buffer' on the logical volumes between the requested size and the size of the volume group does it help? For example, make the size requests 14000 instead of 14696. Then add a '--grow' so they will fill up the remaining space. Yes, i tried even with 14000 instead of 14696. I've not tried 14000 with '-- grow', but I don't think that this would be a problem... If you remove the '--primary' from one (or more) of the partition requests does that help? I was able to use your ks file w/o problems. Closing due to inactivity - please reopen if you have additional information to add to this report. Hello,
I've the same pb: kickstart crashed with the message:
SystemError: vgcreate failed for vg01
If I reboot and re-install with kickstart, it works. And again: if I
re-install with kickstart, it will failed again, even if I remove the
partitions on both disks.
Please notice that my partitions are created exactly as expected,
(and in the good order since I've removed "asprimary" on lvm
partitions).
This is a part of my ks.cfg:
bootloader --location=mbr
clearpart --all --initlabel --drives hda,hdb
zerombr yes
#Disk partitioning information
# Disk1
part /boot --fstype ext3 --ondisk hda --size 75 --asprimary
part swap --fstype swap --ondisk hda --size 512 --asprimary
part / --fstype ext3 --ondisk hda --size 256 --asprimary
part pv.01 --ondisk hda --size 3600 --grow
volgroup vg00 pv.01
logvol /var --fstype ext3 --name=var --vgname=vg00 --size 384
logvol /opt --fstype ext3 --name=opt --vgname=vg00 --size 512
logvol /usr --fstype ext3 --name=usr --vgname=vg00 --size 2048
logvol /home --fstype ext3 --name=home --vgname=vg00 --size 256
# Disk2
part /boot2 --fstype ext3 --ondisk hdb --size 75 --asprimary
part pv.02 --ondisk hdb --size 1000 --grow
volgroup vg01 pv.02
logvol /devicesI --fstype ext3 --name=devicesI --vgname=vg01 --size
1024
Thank you for your help.
|
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461) Description of problem: When you try to perform a system installation using a previously automatically generated kickstart file, partitioning of LVM volume fails and you get a system crash. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install a Red Hat Linux 8.0 as you like, using LVM volumes. 2. Save the original anaconda kickstart file. Uncomment the partition creation line and place a clearpart --all or even a zerombr entry. 3. Try to reinstall the system via the modified kickstart file. Actual Results: The installer crashes. Some lines are output to video. Expected Results: Perform the kickstart installation with no problem. Additional info: Traceback (most recent call last): File "/usr/lib/anaconda/gui.py", line 786, in handleRenderCallback self.currentWindow.renderCallback() File "/usr/lib/anaconda/iw/progress_gui.py", line 149, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 632, in nextClicked self.dispatch.gotoNext() File "/usr/lib/anaconda/dispatch.py", line 150, in gotoNext self.moveStep() File "/usr/lib/anaconda/dispatch.py", line 215, in moveStep rc = apply(func, self.bindArgs(args)) File "/usr/lib/anaconda/packages.py", line 435, in turnOnFilesystems thefsset.createLogicalVolumes(instPath) File "/usr/lib/anaconda/fsset.py", line 1105, in createLogicalVolumes entry.device.setupDevice(chroot) File "/usr/lib/anaconda/fsset.py", line 1624, in setupDevice raise SystemError, "vgcreate failed for %s" %(self.name,) SystemError: vgcreate failed for Volume02