The following was filed automatically by anaconda: anaconda 12.26 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 405, in lvactivate raise LVMError("lvactivate failed for %s" % lv_name) File "/usr/lib/anaconda/storage/devices.py", line 2036, in setup lvm.lvactivate(self.vg.name, self._name) File "/usr/lib/anaconda/storage/devicetree.py", line 1405, in handleUdevLVMPVFormat lv.setup() File "/usr/lib/anaconda/storage/devicetree.py", line 1685, in handleUdevDeviceFormat self.handleUdevLVMPVFormat(info, device) File "/usr/lib/anaconda/storage/devicetree.py", line 1276, in addUdevDevice self.handleUdevDeviceFormat(info, device) File "/usr/lib/anaconda/storage/devicetree.py", line 1909, in populate self.addUdevDevice(dev) File "/usr/lib/anaconda/storage/__init__.py", line 328, in reset self.devicetree.populate() File "/usr/lib/anaconda/storage/__init__.py", line 94, 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/text.py", line 548, in run anaconda.dispatch.gotoNext() File "/usr/bin/anaconda", line 981, in <module> anaconda.intf.run(anaconda) LVMError: lvactivate failed for lv_root
Created attachment 362031 [details] Attached traceback automatically from anaconda.
Installation rawhide-20090921 from boot.iso using text mode in kvm. This bug can be reproduced in gui and rescue mode too. I used 2 disks: parted /dev/sda print Model: ATA QEMU HARDDISK (scsi) Disk /dev/sda: 16.1GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 210MB 210MB primary ext4 boot 2 210MB 16.1GB 15.9GB primary lvm parted /dev/sdb print Model: ATA QEMU HARDDISK (scsi) Disk /dev/sdb: 10.5GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 210MB 210MB primary ext4 boot 2 210MB 10.5GB 10.3GB primary lvm
Created attachment 362047 [details] pvdisplay
Created attachment 362048 [details] vgdisplay
Created attachment 362049 [details] lvdisplay
*** Bug 524849 has been marked as a duplicate of this bug. ***
If possible, please try again using updates from http://dlehman.fedorapeople.org/updates-524775.img. The simplest way to accomplish this is to add the following argument to the installer boot command line: updates=http://dlehman.fedorapeople.org/updates-524775.img
Created attachment 362262 [details] traceback + logs Hi Dave, still traceback when using updates=http://dlehman.fedorapeople.org/updates-524775.img
Ok, there's a new updates.img at the same URL. I was a bit hasty in applying the fix to only one of two places it was required. Please try again at your convenience.
Great, this updates image works and I don't see that traceback any more. But there is a new problem - may be it is related to this bug: When I select "Create custom layout", and on the next screen I select VolGroup and click on Edit - new window shows this message: "Free Space -200.00 MB (-0.8 %)" (I will attach screenshot). Now I edit existing logical volumes: lv_root: format ext4, mount point / lv_swap: format swap And also edit existing sda1: format as ext4, mount point /boot Click on Next, confirm formatting and writing changes to disk and error "lvactivate failed for lv_root" appears. Click on "File Bug" shows traceback (I will attach)
Created attachment 362456 [details] Free space -200 MB
Created attachment 362459 [details] partitioning
Created attachment 362461 [details] lvactivate failed
Created attachment 362462 [details] traceback with updates= image
*** Bug 533403 has been marked as a duplicate of this bug. ***
Encountered this while testing iSCSI on a virt guest. 4 local disks, and 1 remote iSCSI volume. The crash occurs while attempting to re-initialize corrupted data after adding the iSCSI volume.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.