Bug 147358

Can you please provide the full traceback you received?

Created attachment 113991 [details]
complete error dump

Comment on attachment 113991 [details]
complete error dump

I appear to be encountering the same problem during attempts to install as a
second OS on a machine that already runs Windows XP.  Trying to install Fedora
on a new and completely empty second hard drive.  Install fails with attached
error dump

I just got this same problem using core 4.  Tried it two different times, one
manually doing the partitions, and one just by letting anaconda do it itself.
Traceback
File "usr/lib/anaconda/gui.py", line 1137, in handleRenderCallback
self.currentWindow.renderCallback()
File "usr/lib/anaconda/iq/progress_gui.py", line 244, in renderCallback
self.intf.icw.nextClicked()
File "usr/lib/anaconda/gui.py", line 873, in nextClicked self.dispatch.gotoNext()
File "usr/lib/anaconda/dispatch.py", line 174, in gotoNext
self.moveStep()
File "usr/lib/anaconda/disptach.py", line 242, in moveStep
rc = apply(func, self.bindArgs(args))
File "usr/lib/anaconda/packages.py", line 582, in turnOnFilesystems
thefsset.createLogicalVolumes(instPath)
File "usr/lib/anaconda/fsset.py", line 1477, in createLogicalVolumes
entry.device.setupDevice(chroot)
File "usr/lib/anaconda/fsset.py" line 2131, in setupDevice
raise SystemError, "lvcreate failed for %s" %(self.name,)
SystemError: lvcreate failed for LogVol00


(In reply to comment #0)
> From Bugzilla Helper:
> User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us)
AppleWebKit/125.5.6 (KHTML, like Gecko) Safari/125.12
> 
> Description of problem:
> From Traceback output
> 
> File "/usr/src/build475969i386/install//usr/lib/anaconda/fsset.py", line 1432,
in createLogicalVolumes entry.device.setupDevice(chroot)
> File "/usr/src/build/475696-i386/install//usr/lib/anaconda/fsset.py",line
2051, in setupDevice raise SystemError, "lvcreate failed for %s" %(self.name,)
> SystemError: lvcreate failed for LogVol00
> 
> The system will install in some cases when the automatic partitioning is
selected. Any manual changes in disk druid to the partition table seems to
result in this error. 
> 
> Two disks are present in the system: /dev/hda is 40GB and /dev/hdb is 200GB on
the same IDE controller/cable
> 
> This problem presents itself whether or not one of the disks is removed. The
system has successfully once using an automatic partitioning with logical
volumes. Unfortunately, upon reinstall, each attempt and configuration has failed.
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> Always
> 
> Steps to Reproduce:
> 1. Complete disk druid for automatic install
> 2. Use disk druid interface to create a primary partition for /home of 100GB
on /dev/hdb
> 3. Select server packages with ftp
> 4. Start install
> 5. Anaconda display states -- formatting disk
> 6. "Exception ocurred"
>     
> 
> Additional info:

*** Bug 150831 has been marked as a duplicate of this bug. ***

*** Bug 161263 has been marked as a duplicate of this bug. ***

I get the same error message with RHEL4 and kickstart.  I have one SCSI disk and
the following in ks.cfg:
clearpart --all --initlabel
part /boot --fstype ext3 --size=1000 --ondisk=sda --asprimary
part swap --size=2000 --ondisk=sda --asprimary
part pv.4 --size=1 --grow --ondisk=sda --asprimary
volgroup vg0 --pesize=32768 pv.4
logvol /            --fstype ext3 --name=lv00 --vgname=vg0 --size=5000
logvol /var         --fstype ext3 --name=lv01 --vgname=vg0 --size=5000
logvol /tmp         --fstype ext3 --name=lv02 --vgname=vg0 --size=1000
logvol /home        --fstype ext3 --name=lv03 --vgname=vg0 --size=10000 --grow

It dies with:
SystemError: lvcreate failed for lv01

Workaround:

Boot with a Knoppix CD, use the partitioning tool to wipe out the partitions,
then go back and install Fedora.

I've seen the same. FC4 on a system which had previously been configured with
two partitions: one (20GB) an NT4 one and a second (20GB) with ext3 (no LVM) and
FC3 installed (an upgrade from FC2).

Full traceback I got:

File "/usr/lib/anaconda/gui.py", line 1137, in handleRenderCallback
 self.currentWindow.renderCallback()
File "/usr/lib/anaconda/iw/progress_gui.py", line 244, in renderCallback
 self.intf.icw.nextClicked()
File "/usr/lib/anaconda/gui.py", line 873, in nextClicked
 self.dispatch.gotoNext()
File "/usr/lib/anaconda/dispatch.py", line 174, in gotoNext
 self.moveStep()
File "/usr/lib/anaconda/dispatch.py", line 242, in moveStep
 rc = apply(func, self.bindArgs(args))
File "/usr/lib/anaconda/packages.py", line 582, in turnOnFilesystems
 thefsset.createLogicalVolumes(instPath)
File "/usr/lib/anaconda/fsset.py", line 1477, in createLogicalVolumes
 entry.device.setupDevice(chroot)
File "/usr/lib/anaconda/fsset.py", line 2131, in setupDevice
 raise SystemError, "lvcreate failed for %2" %(self.name,)
SystemError: lvcreate failed for Logvol00

Like others, I tried first with some manual adjustments and secondly letting
anaconda choose the partitions itself with no manual configuration.

*** Bug 167410 has been marked as a duplicate of this bug. ***

*** Bug 168672 has been marked as a duplicate of this bug. ***

(In reply to comment #8)
> Workaround:
> 
> Boot with a Knoppix CD, use the partitioning tool to wipe out the partitions,
> then go back and install Fedora.

Thanks for the solution. I just wanted to add that this can also be accomplish
with the fdisk utility on the FC4 DVD/CD instead of the Knoppix disk utility.

Here's what I did.

Once the GUI installer started up:
1. Press Ctrl+Alt+F3 or F4 to get to a prompt.
2. At the prompt, type /usr/sbin/fdisk /dev/sda (or whatever your disk is)
3. delete all partitions (d #)
4. type w to write it out to disk.
5. Press Ctrl+Alt+F7 to return to the installer and continue with the install
process.

-Ken

*** Bug 160255 has been marked as a duplicate of this bug. ***

This bug is reproducable if: you start with a partition table that's different
to the partition table you choose to install onto, but has the same number of
partitions, and the partition (e.g. /dev/sda2) that will hold the physical
volume is a lot smaller in the *old* partition table than in the *new* partition
table.

Therefore, I believe this is actually a duplicate of bug 160693.

Also, a workaround that works fine is just "try again in the exact same way as
you tried to install before". This is consistent with bug 160693 being the root
cause here.

Oh, I forgot to mention - my best evidence for this theory is that the pvcreate
actually creates the physical volume with the wrong size - the exact size that
the corresponding partition in the *old* partition table was. (Of course if you
look at the partition table with fdisk, everything looks OK, because the
partition table on disk does get updated correctly.)

The workaround in comment #13 worked for me.

*** Bug 172681 has been marked as a duplicate of this bug. ***

*** Bug 172902 has been marked as a duplicate of this bug. ***

What information is this bug waiting for?  I see that several people have
provided tracebacks, and there's a "complete error dump" attached to the report
and at least one more in a Duplicate bug.

Fedora Core 4 is not maintained anymore.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.

This is pretty dumb but I've been getting this error for the last day installing Red Hat 4.7 using kickstart onto a VM (Virtual Box 2.1.4 running on my Fedora 10 x84_64)

Here is the partition kickstart info for the Red Hat 4.7 install:

# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
clearpart --all --initlabel
part /boot --fstype ext3 --size=100
part pv.2 --size=0 --grow
volgroup Raid10local  pv.2
logvol / --fstype ext3 --name=root --vgname=Raid10local --size=10240
logvol swap --fstype swap --name=swap --vgname=Raid10local --size=4096
logvol /var --fstype ext3 --name=var --vgname=Raid10local --size=10240
logvol /opt --fstype ext3 --name=opt --vgname=Raid10local --size=10240 --grow

I kept getting the above stack trace e.g.

File "/usr/lib/anaconda/fsset.py", line 2131, in setupDevice
 raise SystemError, "lvcreate failed for %2" %(self.name,)
SystemError: lvcreate failed for Logvol00

In the end it I realised it was simply because the disk wasn't large enough for all the partitions - doh!

e.g. 20GB disk gives the stack trace, 50GB is fine

Perhaps a better error message is needed for when the requested partition sizes exceeds the disk capacity (or physical volume capacity).

This ties in with comment #15 and #16 where the PV has been created too small due to the old partition table being reused.