Description of problem: Installation of F12 Alpha fails with 'most likely a bug'. Attachment included. Version-Release number of selected component (if applicable): How reproducible: Start from DVD or with booted Live CD - attempt to install - bork. Note: Have installed every previous version from F2 onward. Currently running F10 and F11 on other partitions in this machine. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: On the Live CD, SELinux continually shows denials at every step of the process. Also, if you bypass the Anaconda error, 'custom partitioning' fails when Anaconda ignores the partitioning and complains that "/" has not been assigned to a partition.
Created attachment 358733 [details] anaconda text from failed install
is there a particular reason you've assigned this to python-pyblock, not anaconda? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I have the same experience as the original poster, with both Live CD and Install DVD. I do not have a file to attach. If I can do any further testing to help, let me know.
I suspect the assignment to python-pyblock is due to that being the last called routine before the system gave the error dialog.
Forgot to mention, my install attempts were with x86_64 version. Have not tried i386/i686 version.
I have now tried the netinstall iso for both X86_64 and i386/i686, with the same result for both of them. The error dialog pops up during the "Finding Storage Devices" section of Anaconda, shortly after clicking on "Install Anyway." I see that the install instructions say to file bugs against "Fedora", so that should probably be changed for this bug. I could not figure out a way to save the details file from the netinstall environment.
There seems to be no maintainer feedback for this bug. Should the Component be changed to Anaconda? If this isn't fixed, I will not be able to install F12.
andy, wdyt of this? should we route it to anaconda guys? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I;m not Andy, but I think that is a great idea. Since my last post, I have tried every combination of using basic graphic drivers, setting the driver to vesa, nv, nouveau and adding the nouveau.nodeset=0 option to the options. Still no success in getting past the error, with either the x86_64 DVD or the i386 netinstall CD.
I had a relate(same) issue on the x86_64 DVD installation and used "Basic Video" with "nouveau.nodeset=0 raid=noautodetect" The workaround was to removed my card reader/the empty storage devices: scsi 8:0:0:0: Direct-Access Generic Compact Flash 0.00 PQ: 0 ANSI: 2 scsi 8:0:0:1: Direct-Access Generic SD/MMC 0.00 PQ: 0 ANSI: 2 scsi 8:0:0:2: Direct-Access Generic MS/MS-PRO 0.00 PQ: 0 ANSI: 2 scsi 8:0:0:3: Direct-Access Generic SM/xD-Picture 0.00 PQ: 0 ANSI: 2 sd 8:0:0:0: Attached scsi generic sg4 type 0 sd 8:0:0:1: Attached scsi generic sg5 type 0 sd 8:0:0:2: Attached scsi generic sg6 type 0 sd 8:0:0:3: Attached scsi generic sg7 type 0 log taken from FC11. I also have 3 raid5 partions.
lars: that sounds like a previous bug - https://bugzilla.redhat.com/show_bug.cgi?id=493219 . bob, gerry - do you have empty external storage devices attached by any chance? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
None attached for me; just two IDE drives, plus CD-Rom and DVD-RW.
Yes, I do. I have a multi-card reader that is installed internal to my computer. It is a PITA to disconnect it, but if I have time later today, I will do that and see if that allows installation to work. It sounds plausible since the problem occurs during the storage device query portion of the install.
Thanks - please do. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Hmmm...Adam, actually there's a multi-card reader that's on mine too. Didn't think about it since never use it. Let me see if I can kill that as well.
Bob, is it a the cd-rom or a cd-burner? A cd-burner/dvd-rw is a Attached scsi generic device scsi 6:0:1:0: CD-ROM HP DVD Writer 400c AH14 PQ: 0 ANSI: 5 sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray sr 6:0:1:0: Attached scsi CD-ROM sr0 sr 6:0:1:0: Attached scsi generic sg3 type 5 log taken from FC11.
It's a CD-Rom, not burner. I've disconnected the card reader from the mobo and am burning a fresh F12 DVD. I'll post back how it's made out.
AHA! It's the card reader that's the problem! I'm currently typing to you from an INSTALLED F-12Alpha (DVD install), which went flawlessly once the Apacer 15-in-1 Card Reader was disconnected. Thanks for the quick thinking!
if it's not too much of a pain for you guys to try, can you check if it works with the card reader re-connected, once the install's complete? Can we also get the lsusb info for the card reader you guys have? Not sure what else to ask for. I'm going to assign this to anaconda... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** This bug has been marked as a duplicate of bug 517603 ***
I finally got around to disconnecting the card reader, and F12 Alpha x86_64 installed from the install DVD just fine. I didn't even have to use the basic graphics driver option. I reconnected the card reader, and F12 Alpha boots and runs fine with it attached. Thanks to all for tracking this down. Another positive debug experience on Fedora - I never experience this when reporting a bug on Ubuntu.