Created attachment 792306 [details] screenshot Description of problem: I configured the "Installation Destination" spoke, but now it's stuck saying "Error checking storage configuration". There is no way to proceed from here. See attached screenshot. This is a KVM guest with a blank 50 GB disk, backed by a raw format logical volume on the host. Version-Release number of selected component (if applicable): Fedora-20-Nightly-x86_64-Live-xfce-20130828.08-1.iso How reproducible: Unknown. Steps to Reproduce: 1. Run anaconda (manually, because the liveinst script is broken): # anaconda --liveinst --method=livecd:/dev/mapper/live-osimg-min 2. Get to the Installation Destination spoke and select your hard drive, all defaults for partitioning etc. Actual results: Stuck, cannot proceed.
Created attachment 792309 [details] Various anaconda log files (tarball)
AIUI, the "liveinst" command is the only supported way of starting the installer from the command-line. The "ANACONDA BLUESKY INSTALLATION" string in the upper right corner of the screenshot shows that the installer was not started with "liveinst". Did you try the "liveinst" command? (I am guessing the answer is "yes": Bug 1003106.)
(In reply to Richard W.M. Jones from comment #0) > ... the liveinst script is broken ... Sorry, I missed that you had tried "liveinst".
Created attachment 793244 [details] anaconda.log
Created attachment 793246 [details] anaconda-tb-0RaZPo
Created attachment 793247 [details] anaconda-tb-ajwxFh
Created attachment 793249 [details] anaconda-tb-iRnuOo
Created attachment 793250 [details] ifcfg.log
Created attachment 793251 [details] program.log
Created attachment 793252 [details] storage.log
Created attachment 793253 [details] storage.state
(In reply to Richard W.M. Jones from comment #1) > Created attachment 792309 [details] > Various anaconda log files (tarball) In the future, please attach log files as individual text/plain attachments so that we can search for them in bugzilla. Thanks.
I can confirm it's still present in the FC20 Beta.
It seems that Anaconda needs to make its own configuration, with a /boot partition containing /boot/uefi, root partition and swap. So when making a custom configuration without the boot partition, the error pops up.
Bogdan: can you duplicate with the current test candidate and attach all the logs please? http://dl.fedoraproject.org/pub/alt/stage/20-TC5/ Beta is very ancient at this point.
I will download the latest build and attach all the logs, but for the record, I've read the anaconda log and the error seems to be "21:01:59,850 ERR anaconda: Your BIOS-based system needs a special partition to boot from a GPT disk label. To continue, please create a 1MB 'biosboot' type partition." Making a 1MB biosboot partition will indeed fix the issue. Also, disabling bootloader installation if you already have GRUB installed and can make it see the Fedora system.
Created attachment 834071 [details] anaconda log
Created attachment 834072 [details] storage log
Bogdan, you should be seeing a storage error on the status hub, and when you enter the installation destination spoke and click on the orange bar at the bottom it will tell you the error. This is not, as far as I can tell, the same as Richard's report which seems to be that he was stuck and could not re-enter the spoke.
Didn't notice that, but I think it should be more obvious (like a pop-up appearing when clicking on Done, saying "you can't install Fedora without a biosboot partition"). It's really frustrating not knowing what's happening.
I believe rjones' issue was fixed long ago, and the visibility of the issues in Bogdan's issue has been improved by keeping you in custom partitioning if there are errors unless you hit Done twice or resolve them.
Indeed, the team was really quick and solved it before the final release. Great job!