Red Hat Bugzilla – Bug 495139
Anaconda traceback when installing with another LVM already existing
Last modified: 2009-08-17 14:03:13 EDT
The following was filed automatically by anaconda:
anaconda 18.104.22.168 exception report
Traceback (most recent call first):
File "/tmp/updates/storage/devicetree.py", line 1583, in devices
raise DeviceTreeError("duplicate paths in device tree")
File "/tmp/updates/storage/__init__.py", line 279, in devices
devices = self.devicetree.devices.values()
File "/tmp/updates/platform.py", line 59, in _mntDict
for device in [d for d in self.anaconda.id.storage.devices if d.format.mountable]:
File "/tmp/updates/platform.py", line 69, in bootDevice
mntDict = self._mntDict()
File "/tmp/updates/platform.py", line 382, in bootDevice
File "/tmp/updates/storage/__init__.py", line 214, in doIt
boot = self.anaconda.platform.bootDevice()
File "/tmp/updates/packages.py", line 115, in turnOnFilesystems
File "/tmp/updates/dispatch.py", line 205, in moveStep
rc = stepFunc(self.anaconda)
File "/tmp/updates/dispatch.py", line 128, in gotoNext
File "/tmp/updates/gui.py", line 1323, in nextClicked
DeviceTreeError: duplicate paths in device tree
Created attachment 339001 [details]
Attached traceback automatically from anaconda.
Created attachment 339002 [details]
Created attachment 339003 [details]
vgdisplay output after anaconda crash
Planned partition layout:
sda1 ext3 /boot partition to be used for the rawhide installation (existing)
sda2 ntfs partition, should be left alone (existing)
sda3 ext3 /boot1 partition for a fc4 installation, should be chainloaded by the grub installed in sda (existing)
sda4 extended partition (existing)
sda5 lvm for a fc4 installation (existing)
sda6 encrypted lvm for the rawhide installation (newly created in the free space by anaconda)
Steps to reproduce:
1. Netboot anaconda
2. Select defaults leading up to the partitioning screen
3. Select Custom Layout
4. Click Next.
5. Select /dev/sda1 to be reformatted as ext3 and mounted as /boot
6. Create a new LVM partition, 17408MB large, select encrypted
7. Click LVM to edit this LVM partition named vg_workstation
8. ??? Wonder about the "Physical Volumes to Use:" list which contains luks-3 and luks-4 ???
9. Create lv root with 16384MB
10. Create lv swap with 1020MB
11. Click Next.
Did you happen to go back and forth from the custom partitioning screen to that initial "Use free space/Replace existing system/Etc." screen as part of your work?
Does this persist with the current RC images?
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
*** Bug 505404 has been marked as a duplicate of this bug. ***