The following was filed automatically by anaconda: anaconda 13.31 exception report Traceback (most recent call first): File "/usr/lib/python2.6/site-packages/parted/disk.py", line 246, in addPartition constraint.getPedConstraint()) File "/usr/lib/python2.6/site-packages/parted/decorators.py", line 30, in localeC ret = fn(*args, **kwds) File "<string>", line 2, in addPartition File "/usr/lib/anaconda/storage/formats/disklabel.py", line 272, in addPartition constraint=constraint) File "/usr/lib/anaconda/storage/devices.py", line 1257, in create self.disk.format.addPartition(self.partedPartition) File "/usr/lib/anaconda/storage/deviceaction.py", line 203, in execute self.device.create(intf=intf) File "/usr/lib/anaconda/storage/devicetree.py", line 672, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 290, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 109, in turnOnFilesystems anaconda.storage.doIt() File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1313, in nextClicked self.anaconda.dispatch.gotoNext() PartitionException: Too many primary partitions.
Created attachment 396209 [details] Attached traceback automatically from anaconda.
Hi Hurry, can you provide a few steps that you use to reproduce this failure? THanks!
Sorry I forgot.. Description of problem: I tried to install Fedora-13-Alpha-RC3 on a F12 existing system. At Partitioning step, I selected Create custom layout and added /boot, / (swap) manually. Version-Release number of selected component (if applicable): * Fedora-13-Alpha-RC3 * anaconda 13.31 How reproducible: 100% Steps to Reproduce: 1. Boot netinst.iso 2. Proceed through install to partitioning step: a. Choose create cumstom layout and click next. b. Create 500M ext4 /boot /dev/sda5. c. Create 5000M ext4 / /dev/sda6. (d. Create 500M swap /dev/sda7.) 3. Exception Occurred after clear next. Note: I executed the same steps on anaconda 13.29 of rc2, it hanged or exception occurred with different status. please see bug 567576.
Created attachment 396484 [details] Attached traceback automatically from anaconda.
reproduced in f13-alpha-RC4
Created attachment 396526 [details] Attached traceback automatically from anaconda.
Created attachment 396678 [details] Attached traceback automatically from anaconda.
Created attachment 396679 [details] Attached traceback automatically from anaconda.
These tracebacks occurred in a rawhide VM. Was trying to create, in the first instance a raid 10 device to be used as a PV and in the second case, just create standard PVs. First problem arose when creating the VG and the second when trying to format the LV.
Created attachment 401340 [details] Attached traceback automatically from anaconda.
In my case this happens because of an empty logical partition, this was already reported for F12, see https://bugzilla.redhat.com/show_bug.cgi?id=540808#c3
Unlike https://bugzilla.redhat.com/show_bug.cgi?id=540808#c2 in my case the partitions are in disk order: Disk /dev/sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x2f4a2f49 Device Boot Start End Blocks Id System /dev/sda1 * 1 4904 39391348+ 7 HPFS/NTFS /dev/sda2 4905 17653 102406342+ 7 HPFS/NTFS /dev/sda3 17654 30401 102398310 f W95 Ext'd (LBA)
Created attachment 401944 [details] Attached traceback automatically from anaconda.
Created attachment 402164 [details] Attached traceback automatically from anaconda.
(In reply to comment #15) > Created an attachment (id=402164) [details] > Attached traceback automatically from anaconda. Here are the partitions before and after. 13.36 F13-Beta-TC1 Live image installed on a USB stick [root@localhost liveuser]# fdisk -l /dev/sdb Disk /dev/sdb: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xff3d5e55 Device Boot Start End Blocks Id System /dev/sdb1 * 1 13 104391 83 Linux /dev/sdb2 14 4418 35383162+ 8e Linux LVM /dev/sdb3 4419 4802 3082399 83 Linux /dev/sdb4 4802 4866 512000 5 Extended /dev/sdb5 4802 4866 510976 82 Linux swap / Solaris [root@localhost liveuser]# fdisk -l /dev/sdb Disk /dev/sdb: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xff3d5e55 Device Boot Start End Blocks Id System /dev/sdb1 * 1 13 104391 83 Linux /dev/sdb2 14 4418 35383162+ 8e Linux LVM /dev/sdb4 4802 4866 512000 5 Extended [root@localhost liveuser]#
Updates available for testing: http://dlehman.fedorapeople.org/updates-568219.img That's against anaconda-13.36-1, so it may not work with older versions of anaconda. Please test, if possible, and provide feedback.
Created attachment 403196 [details] Attached traceback automatically from anaconda.
Created attachment 403208 [details] Attached traceback automatically from anaconda.
(In reply to comment #17) > Updates available for testing: > > http://dlehman.fedorapeople.org/updates-568219.img > > That's against anaconda-13.36-1, so it may not work with older versions of > anaconda. Please test, if possible, and provide feedback. Reproduced this issue. Please refer to comment 19. The steps are: 1. The original system must contain extended partition. 2. Install another system, delete the partitions in the extended partition one by one (sda5 and above).(Note: delete extended partition directly won't make this issue happen.) 3. Create new ext4 partitions. 4. Exception occurred.
Created attachment 406389 [details] Attached traceback automatically from anaconda.
Discussed at today's blocker bug review meeting. Accepted as a blocker as it infringes: "The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above" https://fedoraproject.org/wiki/Fedora_13_Final_Release_Criteria -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
anaconda-13.39-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.39-1.fc13
rhe: can you please re-test with anaconda 13.39? I think the nightly live images should include it at least, by now. thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
actually, it's included in tc1, so just test with that. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
we need someone else to test this, as Chinese office is on holiday. I can't, due to my current resources. James, can you, following Rui's reproduction steps?
I tested this following the steps above, and was not able to reproduce it. Calling it fixed.
I have the same issue with anaconda 13.42/i386 System (Dell XPS) has BIOS RAID, with three WIN partions (factory tools, factory restore, win7). Any partitioning scheme (manual w/standard partions (no lvm), lvm auto, lvm review fails, fails with "too many primary partions". I tried to prepartition the disk, telling anaconda to replace existing partitions, which led to what follows (prob'ly a separete bug): Traceback (most recent call first): File "/usr/lib/anaconda/iw/partition_gui.py", line 1070, in populate devstring = device.name File "/usr/lib/anaconda/iw/partition_gui.py", line 1844, in getScreen self.populate(initial = 1) File "/usr/lib/anaconda/gui.py", line 1393, in setScreen new_screen = self.currentWindow.getScreen(anaconda) File "/usr/lib/anaconda/gui.py", line 1405, in setScreen return self.setScreen() File "/usr/lib/anaconda/gui.py", line 1314, in nextClicked self.setScreen () AttributeError: 'NoneType' object has no attribute 'name' (full traceback had separately been reported here: [http://www.google.it/url?sa=t&source=web&cd=1&ved=0CBcQFjAA&url=http%3A%2F%2Fforums.fedoraforum.org%2Fattachment.php%3Fattachmentid%3D19742%26d%3D1277495147&ei=Fj08TIzkD47-OdvG5MQP&usg=AFQjCNESY6NU1mDaHd7ic2N9WNVFL4Pr3A&sig2=a9sl-DTePlck5vAxRunNXQ])
*** Bug 578553 has been marked as a duplicate of this bug. ***