Bug 1051798 - failed to find a suitable stage1 device
Summary: failed to find a suitable stage1 device
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1051802
TreeView+ depends on / blocked
 
Reported: 2014-01-11 16:57 UTC by Germano Massullo (Thetra)
Modified: 2014-03-03 15:50 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-03-03 15:50:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
tty screenshot #1 (343.05 KB, image/jpeg)
2014-01-11 16:57 UTC, Germano Massullo (Thetra)
no flags Details
screenshot of anaconda error (65.37 KB, image/jpeg)
2014-01-11 17:05 UTC, Germano Massullo (Thetra)
no flags Details
tty screenshot #2 (541.57 KB, image/jpeg)
2014-01-11 17:06 UTC, Germano Massullo (Thetra)
no flags Details

Description Germano Massullo (Thetra) 2014-01-11 16:57:47 UTC
Created attachment 848653 [details]
tty screenshot #1

Description of problem:
I had a lot of troubles in installing Fedora on Dell laptop with a UEFI BIOS and windows 8.
I disabled UEFI secure boot on the BIOS, then I tried to install Fedora in dualboot mode. Obtaining everytime a generic error (see screenshot and tty screenshot) made me try to erase all partitions with GParted and to recreate the partition table (msdos).
Starting again the Fedora installer to install only Fedora, I got again the same generic error from Anaconda. So I tried to click on "automatically create tables" in Anaconda partitioning screen. That time Anaconda did not complain about, so I decided to go back in the partitioning screen to create an identical partitions layout but with different sizes. Again Anaconda gave me troubles with its generic error message. Then I was forced to let Anaconda automatically choose partitions and sizes (by clicking on "automatically create partitions" in Anaconda partitioning screen). 

Additional info:
Installing from Fedora 20 KDE 64bit iso.

fdisk output, taken when I was trying to install Fedora in dual boot mode.	

    Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 6194F704-5C3F-45E1-A08F-FF5E872C993A
     
    Device           Start          End   Size Type
    /dev/sda1         2048      1026047   500M EFI System
    /dev/sda2      1026048      2373631   658M Linux swap
    /dev/sda5      2373632   1519376383 723.4G Microsoft basic data
    /dev/sda6   1928976384   1953523119  11.7G Linux filesystem
     
     
    Disk /dev/sdb: 15.1 GiB, 16170164224 bytes, 31582352 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x00000001
     
    Device    Boot Start       End   Blocks  Id System
    /dev/sdb1 *     2048  31582207 15790080   b W95 FAT32
     
     
    Disk /dev/mapper/live-rw: 4 GiB, 4294967296 bytes, 8388608 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
     
    Disk /dev/mapper/live-base: 4 GiB, 4294967296 bytes, 8388608 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
     
    Disk /dev/mapper/live-osimg-min: 4 GiB, 4294967296 bytes, 8388608 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes

Comment 1 Germano Massullo (Thetra) 2014-01-11 17:05:28 UTC
Created attachment 848654 [details]
screenshot of anaconda error

Comment 2 Germano Massullo (Thetra) 2014-01-11 17:06:17 UTC
Created attachment 848655 [details]
tty screenshot #2

Comment 3 Germano Massullo (Thetra) 2014-01-11 17:14:49 UTC
I forgot to create this bug as clone of https://bugzilla.redhat.com/show_bug.cgi?id=1026825
But I think it has nothing to do with kickstarter (I did not use it)

Comment 4 David Shea 2014-03-03 15:50:32 UTC
You need to configure the EFI System partition as mountpoint at /boot/efi. The changes mentioned in bug 1051802 makes this more obvious. Attempting to leave custom partitioning without /boot/efi results in an error, and clicking on the error message will present a dialog with the following message:

"No valid bootloader target device found. See below for details.
For a UEFI installation, you must include an EFI System Partition on a GPT-formatted disk, mounted at /boot/efi."


Note You need to log in before you can comment on or make changes to this bug.