The following was filed automatically by anaconda: anaconda 12.2 exception report Traceback (most recent call first): File "/usr/lib64/python2.6/site-packages/parted/disk.py", line 142, in duplicate return Disk(PedDisk=self.__disk.duplicate()) File "/usr/lib/anaconda/storage/devices.py", line 744, in __init__ self._origPartedDisk = self.partedDisk.duplicate() File "/usr/lib/anaconda/storage/devicetree.py", line 1127, in addUdevDiskDevice initcb=cb, initlabel=initlabel, **kwargs) File "/usr/lib/anaconda/storage/devicetree.py", line 1209, in addUdevDevice device = self.addUdevDiskDevice(info) File "/usr/lib/anaconda/storage/devicetree.py", line 1726, in populate self.addUdevDevice(dev) File "/usr/lib/anaconda/storage/__init__.py", line 291, in reset self.devicetree.populate() File "/usr/lib/anaconda/storage/__init__.py", line 92, in storageInitialize storage.reset() File "/usr/lib/anaconda/dispatch.py", line 204, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 127, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1346, in nextClicked self.anaconda.dispatch.gotoNext() PartedException: Assertion (!disk->update_mode) at disk.c:425 in function ped_disk_destroy() failed.
Created attachment 351408 [details] Attached traceback automatically from anaconda.
trace back occurred during initial "Finding storage devices." This error occurred on a complex test system that has numerous partitions, LVs, md devices and a raid container. Same error occurs when trying to install under a Fedora11 VM to a very vanilla disk/partition layout.
Created attachment 351512 [details] Attached traceback automatically from anaconda.
Can you pls post the output of 1. `fdisk -l DEVICE` and 2. `parted DEVICE print free` Thx.
Created attachment 351587 [details] fdisk and parted of storage devices As requested.
Created attachment 353779 [details] Attached traceback automatically from anaconda.
Created attachment 353784 [details] anaconda.log Using boot.iso/install.img dated 15 July 2009 00:17 on the following existing disk layout ... fdisk -l /dev/sda Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 83 Linux /dev/sda2 14 78 522112+ 82 Linux swap / Solaris /dev/sda3 79 1044 7759395 8e Linux LVM pvs PV VG Fmt Attr PSize PFree /dev/sda3 vg0 lvm2 a- 7.38G 3.75G vgs VG #PV #LV #SN Attr VSize VFree vg0 1 1 0 wz--n- 7.38G 3.75G lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert f9 vg0 -wi-ao 3.62G
Created attachment 353785 [details] storage.log
Created attachment 353786 [details] syslog
Created attachment 353889 [details] Attached traceback automatically from anaconda.
Created attachment 354025 [details] Attached traceback automatically from anaconda.
Created attachment 354026 [details] Attached traceback automatically from anaconda.
FWIW ... I also see the following backtrace on the serial console when this failure occurs: Backtrace has 20 calls on stack: 20: /lib/libparted-1.9.so.0(ped_assert+0x43) [0xcd8793] 19: /lib/libparted-1.9.so.0(ped_disk_destroy+0x9b) [0xcde24b] 18: /lib/libparted-1.9.so.0(ped_disk_duplicate+0x1c2) [0xcdfa52] 17: /usr/lib/python2.6/site-packages/_pedmodule.so(py_ped_disk_duplicate+0x2c) [0xd795ec] 16: /usr/lib/libpython2.6.so.1.0(PyCFunction_Call+0x12a) [0x41fbda] 15: /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4a0c) [0x47b97c] 14: /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5345) [0x47c2b5] 13: /usr/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7b2) [0x47d122] 12: /usr/lib/libpython2.6.so.1.0 [0x40c040] 11: /usr/lib/libpython2.6.so.1.0(PyObject_Call+0x5c) [0x3df72c] 10: /usr/lib/libpython2.6.so.1.0 [0x3f5574] 9: /usr/lib/libpython2.6.so.1.0(PyObject_Call+0x5c) [0x3df72c] 8: /usr/lib/libpython2.6.so.1.0 [0x43b2e6] 7: /usr/lib/libpython2.6.so.1.0 [0x439c75] 6: /usr/lib/libpython2.6.so.1.0(PyObject_Call+0x5c) [0x3df72c] 5: /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x3492) [0x47a402] 4: /usr/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x7b2) [0x47d122] 3: /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x43f1) [0x47b361] 2: /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5345) [0x47c2b5] 1: /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5345) [0x47c2b5]
Setting severity to high based on http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow#Severity
Created attachment 354133 [details] Attached traceback automatically from anaconda.
Created attachment 354146 [details] Attached traceback automatically from anaconda.
Created attachment 354218 [details] Attached traceback automatically from anaconda.
Created attachment 354227 [details] Attached traceback automatically from anaconda.
Joel, I think there's a typo in your pop-push-errno patch. (A reversed conditional.) I've commited this into parted-1_9_0-3_20090610git32dc_fc12; if you've submitted that upstream, you may want to resubmit it with the fix applied.
Could not test with anaconda 12.3 due to https://bugzilla.redhat.com/show_bug.cgi?id=513021 networking won't come up.
I was able not to get this error with anaconda-12.3 on today's (21 July 2009) boot.iso. I ran into a different show-stopping bug at a later point, but that will be a different report.
Ludomir: Thx a lot for the fix. I have not yet posted this upstream (was waiting for testing :). I'm closing this based on comment #21
Created attachment 354735 [details] Anaconda InstallError output
Bug still exists, please see the attachment I posted.
Wrong bug, reclosing.
Created attachment 354744 [details] Attached traceback automatically from anaconda.
Isn't this essentially the same error as in bz 511907? If so, shouldn.t it be a dup and not closed?
Yes, you're correct. Duping. *** This bug has been marked as a duplicate of bug 511907 ***