libreport version: 2.0.6 executable: /usr/bin/python hashmarkername: anaconda kernel: 3.1.0-0.rc9.git0.2.fc16.kh.ppc64 product: Fedora reason: IndexError: list index out of range time: Fri Oct 28 09:46:42 2011 version: 16 anaconda-tb-NBsAuQ: Text file, 200229 bytes description: :The following was filed automatically by anaconda: :anaconda 16.21 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 307, in drives : self.stage1_drive = self._drives[0] : File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/cleardisks_gui.py", line 159, in getScreen : self.anaconda.bootloader.drives[0].name) : File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1270, in display_step : new_screen = self.currentWindow.getScreen(self.anaconda) : File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1157, in display_step : return self.icw.display_step(step) : File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 377, in dispatch : rc = self.anaconda.intf.display_step(self.step) : File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 241, in go_forward : self.dispatch() : File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1201, in nextClicked : self.anaconda.dispatch.go_forward() :IndexError: list index out of range
Created attachment 530675 [details] File: anaconda-tb-NBsAuQ
Same occured on my ASUS P8H67-M PRO. UEFI booted from efidisk.img on a USB stick. My stacktrace is bit diffrent so I'll attach it.
Created attachment 533078 [details] stacktrace
(In reply to comment #1) > Created attachment 530675 [details] > File: anaconda-tb-NBsAuQ baude, what is the story with your hard drive? It appears to have formatting to indicate that it is part of a firmware RAID array (according to udev/blkid), but it is not being recognized as such by the tools that manage such devices (mdadm).
(In reply to comment #3) > Created attachment 533078 [details] > stacktrace Due to widespread use of USB install media and bug 750469 we made a change to disallow installing a bootloader to any hard drive that contains an iso9660 filesystem. Your sda8 partition contains an iso9660 filesystem. I have no idea why since iso9660 filesystems are typically only used on optical media like DVDs.
(In reply to comment #5) > Due to widespread use of USB install media and bug 750469 we made a change to > disallow installing a bootloader to any hard drive that contains an iso9660 > filesystem. Your sda8 partition contains an iso9660 filesystem. I have no idea > why since iso9660 filesystems are typically only used on optical media like > DVDs. I once tried to install Ubuntu without a USB stick. I created a small partition and copied iso image to it via dd command. Then I booted from it and installed system on another partition. That's why I have iso9660 partition. I only scanned through bug you mentioned so I don't know much about it but I believe it shouldn't matter if I have such partition. It's not even being touched during installation.
(In reply to comment #6) > (In reply to comment #5) > > Due to widespread use of USB install media and bug 750469 we made a change to > > disallow installing a bootloader to any hard drive that contains an iso9660 > > filesystem. Your sda8 partition contains an iso9660 filesystem. I have no idea > > why since iso9660 filesystems are typically only used on optical media like > > DVDs. > > I once tried to install Ubuntu without a USB stick. I created a small partition > and copied iso image to it via dd command. Then I booted from it and installed > system on another partition. That's why I have iso9660 partition. I only > scanned through bug you mentioned so I don't know much about it but I believe > it shouldn't matter if I have such partition. It's not even being touched > during installation. It's more complicated than you'd expect. You will need to run something like wipefs on that partition before you can install F16 on that disk. It's an unfortunate limitation, but if you don't need that partition/filesystem anymore it shouldn't be a problem to clear it off.
performed a wipefs to remove metadata on the disk and it now behaves normally.
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > Due to widespread use of USB install media and bug 750469 we made a change to > > > disallow installing a bootloader to any hard drive that contains an iso9660 > > > filesystem. Your sda8 partition contains an iso9660 filesystem. I have no idea > > > why since iso9660 filesystems are typically only used on optical media like > > > DVDs. > > > > I once tried to install Ubuntu without a USB stick. I created a small partition > > and copied iso image to it via dd command. Then I booted from it and installed > > system on another partition. That's why I have iso9660 partition. I only > > scanned through bug you mentioned so I don't know much about it but I believe > > it shouldn't matter if I have such partition. It's not even being touched > > during installation. > > It's more complicated than you'd expect. You will need to run something like > wipefs on that partition before you can install F16 on that disk. It's an > unfortunate limitation, but if you don't need that partition/filesystem anymore > it shouldn't be a problem to clear it off. It happened to me a few minutes ago when installing from DVD, EFI is set on in BIOS. I have two disks and plan to set up software RAID1. Anaconda said that the disks contain RAID metadata. The error occured when I selected to use custom layout. I am going to install a new computer, the disks are empty, so I can safely erase everything. Would it help to select "use all space" and then repartion it manually, or should I do some action from the maintenance mode?
similar behavior to comment #9. except i need to retain the bios-raid/partition setup (because that's how dell decided to install their stuff :( i've shrunk the windows partition, selected the (single) disk containing the free space, and got the index error when selecting manual partition layout. actually the same also happens with f17-beta dvd. any chance this use case is/will be supported by anaconda?
I'm having this issue occur as well. I have an HP laptop (dv7) that has mSSD Hard Drive Acceleration Cache... Could this be the reason that it is having issues/
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.