no bootable device after upgrade to 29... help?
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 14 of 14
  1. #1
    Join Date
    Feb 2015
    Location
    Online
    Posts
    48
    Linux (Fedora) Firefox 62.0

    no bootable device after upgrade to 29... help?

    I did in place upgrade from 28 to 29 beta. After update I did dnf clean all and reboot. It stopped booting since throwing no bootable devices found. Hard drive is fine and changing it to legacy does not make it boot.

    This is my first time dealing with this... Is there a boot repair disk or something along those lines?

  2. #2
    Join Date
    Aug 2007
    Posts
    269
    Linux Firefox 52.0

    Re: no bootable device after upgrade to 29... help?

    I did in place upgrade from 28 to 29 beta.
    So you "upgraded" from a working F28 installation to a test version of F29 in the process wiping out your working F28 installation. This is one of those situations where dual booting would be appropriate. You could have cloned your F28 installation with rysnc before doing an 'upgrade' on the copy.

    Can you use a live disc to examine your disk and efi boot variables ?

  3. #3
    Join Date
    Feb 2015
    Location
    Online
    Posts
    48
    Linux (Fedora) Firefox 61.0

    Re: no bootable device after upgrade to 29... help?

    I've booted via live-usb. Fdisk shows this for boot.... any advice would be great.

    Device Boot Start End Sectors Size Id Type
    /dev/sda1 * 0 3727359 3727360 1.8G 0 Empty
    /dev/sda2 116884 136827 19944 9.8M ef EFI (FAT-12/16/32)
    /dev/sda3 136828 178811 41984 20.5M 0 Empty

    whole fdisk output
    Disk /dev/nvme0n1: 477 GiB, 512110190592 bytes, 1000215216 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: 77DB2AF6-BEA8-4BFE-9666-54FC089F5440

    Device Start End Sectors Size Type
    /dev/nvme0n1p1 2048 411647 409600 200M EFI System
    /dev/nvme0n1p2 411648 2508799 2097152 1G Linux filesystem
    /dev/nvme0n1p3 2508800 1000214527 997705728 475.8G Linux LVM


    Disk /dev/mapper/fedora-swap: 7.8 GiB, 8401190912 bytes, 16408576 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/fedora-home: 417.9 GiB, 448736002048 bytes, 876437504 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/fedora-root: 50 GiB, 53687091200 bytes, 104857600 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/sda: 7.2 GiB, 7748222976 bytes, 15133248 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: 0x21233848

    Device Boot Start End Sectors Size Id Type
    /dev/sda1 * 0 3727359 3727360 1.8G 0 Empty
    /dev/sda2 116884 136827 19944 9.8M ef EFI (FAT-12/16/32)
    /dev/sda3 136828 178811 41984 20.5M 0 Empty


    Disk /dev/loop0: 1.7 GiB, 1805836288 bytes, 3527024 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/loop1: 6.5 GiB, 6981419008 bytes, 13635584 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/loop2: 32 GiB, 34359738368 bytes, 67108864 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-rw: 6.5 GiB, 6981419008 bytes, 13635584 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: 6.5 GiB, 6981419008 bytes, 13635584 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
    [root@localhost liveuser]#
    Last edited by Anonymous; 29th September 2018 at 03:27 AM.

  4. #4
    Join Date
    Aug 2007
    Posts
    269
    Linux Firefox 52.0

    Re: no bootable device after upgrade to 29... help?

    Since you have two disks with two ESP partitions you need to post your efi variables and boot order so we know which partition is set to boot.

    sudo efibootmgr -v

  5. #5
    Join Date
    Feb 2015
    Location
    Online
    Posts
    48
    Linux (Fedora) Firefox 61.0

    Re: no bootable device after upgrade to 29... help?

    Verbatim is the usb thumb drive that I use for live-usb. I dont have windows installed on this machine so I'm very confused as to why it says Windows Boot Manager..... Thank you Amiga.

    [liveuser@localhost ~]$ su
    [root@localhost liveuser]# efibootmgr -v
    BootCurrent: 0001
    Timeout: 0 seconds
    BootOrder: 0001
    Boot0000* Windows Boot Manager HD(1,GPT,ffdd7c6d-458a-45d8-93a3-187d2cc59e7f,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS..... ....x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
    Boot0001* UEFI: VerbatimMICRO PLUS PMAP, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(1,MBR,0x21233848,0x1c894,0x4de8)..BO
    [root@localhost liveuser]#

  6. #6
    Join Date
    Aug 2007
    Posts
    269
    Linux Firefox 52.0

    Re: no bootable device after upgrade to 29... help?

    Verbatim is the usb thumb drive that I use for live-usb. I don't have windows installed on this machine so I'm very confused as to why it says Windows Boot Manager..... Thank you Amiga.
    This explains everything. You don't have an EFI entry to boot Fedora at all. I am assuming that Windows was previously installed on this motherboard. You will have to use the live usb to create an EFI entry for F29. However first you should check that the F29 boot partition looks fine and that grub efi exists in the ESP.

    /dev/nvme0n1p1 2048 411647 409600 200M EFI System
    /dev/nvme0n1p2 411648 2508799 2097152 1G Linux filesystem
    Use the live usb to mount these two partitions and list (ls) the contents. Please post the listings. The ESP should have grub 64 efi and a grub.cfg file. Please post the grub.cfg file in a CODE block. The 1G boot partition should have a kernel and initrd.

  7. #7
    Join Date
    Feb 2015
    Location
    Online
    Posts
    48
    Linux (Fedora) Firefox 61.0

    Re: no bootable device after upgrade to 29... help?

    /dev/nvme0n1p1 2048 411647 409600 200M EFI System
    dad235a5179e4fa792091681a5f65d21 EFI mach_kernel System
    EFI has 3 folders
    BOOT Dell fedora
    fedora folder content - grub.cfg grubenv
    grub.cfg content
    Code:
    #
    # DO NOT EDIT THIS FILE
    #
    # It is automatically generated by grub2-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    #
    
    ### BEGIN /etc/grub.d/00_header ###
    set pager=1
    
    if [ -s $prefix/grubenv ]; then
      load_env
    fi
    if [ "${next_entry}" ] ; then
       set default="${next_entry}"
       set next_entry=
       save_env next_entry
       set boot_once=true
    else
       set default="${saved_entry}"
    fi
    
    if [ x"${feature_menuentry_id}" = xy ]; then
      menuentry_id_option="--id"
    else
      menuentry_id_option=""
    fi
    
    export menuentry_id_option
    
    if [ "${prev_saved_entry}" ]; then
      set saved_entry="${prev_saved_entry}"
      save_env saved_entry
      set prev_saved_entry=
      save_env prev_saved_entry
      set boot_once=true
    fi
    
    function savedefault {
      if [ -z "${boot_once}" ]; then
        saved_entry="${chosen}"
        save_env saved_entry
      fi
    }
    
    function load_video {
      if [ x$feature_all_video_module = xy ]; then
        insmod all_video
      else
        insmod efi_gop
        insmod efi_uga
        insmod ieee1275_fb
        insmod vbe
        insmod vga
        insmod video_bochs
        insmod video_cirrus
      fi
    }
    
    terminal_output console
    if [ x$feature_timeout_style = xy ] ; then
      set timeout_style=menu
      set timeout=5
    # Fallback normal timeout code in case the timeout_style feature is
    # unavailable.
    else
      set timeout=5
    fi
    ### END /etc/grub.d/00_header ###
    
    ### BEGIN /etc/grub.d/01_users ###
    if [ -f ${prefix}/user.cfg ]; then
      source ${prefix}/user.cfg
      if [ -n "${GRUB2_PASSWORD}" ]; then
        set superusers="root"
        export superusers
        password_pbkdf2 root ${GRUB2_PASSWORD}
      fi
    fi
    ### END /etc/grub.d/01_users ###
    
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Fedora (4.18.9-300.fc29.x86_64) 29 (Workstation Edition)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.8.6-300.fc25.x86_64-advanced-cdce2fe9-34b2-4427-b4ef-f1b9332db9e7' {
    	load_video
    	set gfxpayload=keep
    	insmod gzio
    	insmod part_gpt
    	insmod ext2
    	if [ x$feature_platform_search_hint = xy ]; then
    	  search --no-floppy --fs-uuid --set=root  2b6a0dfc-890c-417a-8903-d4add903700e
    	else
    	  search --no-floppy --fs-uuid --set=root 2b6a0dfc-890c-417a-8903-d4add903700e
    	fi
    	linuxefi /vmlinuz-4.18.9-300.fc29.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_US.UTF-8
    	initrdefi /initramfs-4.18.9-300.fc29.x86_64.img
    }
    menuentry 'Fedora (4.18.5-300.fc29.x86_64) 29 (Workstation Edition)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.8.6-300.fc25.x86_64-advanced-cdce2fe9-34b2-4427-b4ef-f1b9332db9e7' {
    	load_video
    	set gfxpayload=keep
    	insmod gzio
    	insmod part_gpt
    	insmod ext2
    	if [ x$feature_platform_search_hint = xy ]; then
    	  search --no-floppy --fs-uuid --set=root  2b6a0dfc-890c-417a-8903-d4add903700e
    	else
    	  search --no-floppy --fs-uuid --set=root 2b6a0dfc-890c-417a-8903-d4add903700e
    	fi
    	linuxefi /vmlinuz-4.18.5-300.fc29.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_US.UTF-8
    	initrdefi /initramfs-4.18.5-300.fc29.x86_64.img
    }
    menuentry 'Fedora (4.18.9-200.fc28.x86_64) 28 (Workstation Edition)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.8.6-300.fc25.x86_64-advanced-cdce2fe9-34b2-4427-b4ef-f1b9332db9e7' {
    	load_video
    	set gfxpayload=keep
    	insmod gzio
    	insmod part_gpt
    	insmod ext2
    	if [ x$feature_platform_search_hint = xy ]; then
    	  search --no-floppy --fs-uuid --set=root  2b6a0dfc-890c-417a-8903-d4add903700e
    	else
    	  search --no-floppy --fs-uuid --set=root 2b6a0dfc-890c-417a-8903-d4add903700e
    	fi
    	linuxefi /vmlinuz-4.18.9-200.fc28.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_US.UTF-8
    	initrdefi /initramfs-4.18.9-200.fc28.x86_64.img
    }
    menuentry 'Fedora (0-rescue-dad235a5179e4fa792091681a5f65d21) 25 (Workstation Edition)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-0-rescue-dad235a5179e4fa792091681a5f65d21-advanced-cdce2fe9-34b2-4427-b4ef-f1b9332db9e7' {
    	load_video
    	insmod gzio
    	insmod part_gpt
    	insmod ext2
    	if [ x$feature_platform_search_hint = xy ]; then
    	  search --no-floppy --fs-uuid --set=root  2b6a0dfc-890c-417a-8903-d4add903700e
    	else
    	  search --no-floppy --fs-uuid --set=root 2b6a0dfc-890c-417a-8903-d4add903700e
    	fi
    	linuxefi /vmlinuz-0-rescue-dad235a5179e4fa792091681a5f65d21 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet
    	initrdefi /initramfs-0-rescue-dad235a5179e4fa792091681a5f65d21.img
    }
    
    ### END /etc/grub.d/10_linux ###
    
    ### BEGIN /etc/grub.d/20_linux_xen ###
    
    ### END /etc/grub.d/20_linux_xen ###
    
    ### BEGIN /etc/grub.d/20_ppc_terminfo ###
    ### END /etc/grub.d/20_ppc_terminfo ###
    
    ### BEGIN /etc/grub.d/30_os-prober ###
    ### END /etc/grub.d/30_os-prober ###
    
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries.  Simply type the
    # menu entries you want to add after this comment.  Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f  ${config_directory}/custom.cfg ]; then
      source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
      source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    /dev/nvme0n1p2

    config-4.18.5-300.fc29.x86_64
    config-4.18.9-200.fc28.x86_64
    config-4.18.9-300.fc29.x86_64
    efi
    elf-memtest86+-5.01
    extlinux
    grub2
    initramfs-0-rescue-dad235a5179e4fa792091681a5f65d21.img
    initramfs-4.18.5-300.fc29.x86_64.img
    initramfs-4.18.9-200.fc28.x86_64.img
    initramfs-4.18.9-300.fc29.x86_64.img
    loader
    lost+found
    memtest86+-5.01
    mydrive
    System.map-4.18.5-300.fc29.x86_64
    System.map-4.18.9-200.fc28.x86_64
    System.map-4.18.9-300.fc29.x86_64
    vmlinuz-0-rescue-dad235a5179e4fa792091681a5f65d21
    vmlinuz-4.18.5-300.fc29.x86_64
    vmlinuz-4.18.9-200.fc28.x86_64
    vmlinuz-4.18.9-300.fc29.x86_64
    Last edited by Anonymous; 1st October 2018 at 03:12 AM.

  8. #8
    Join Date
    Feb 2015
    Location
    Online
    Posts
    48
    Linux (Fedora) Firefox 59.0

    Re: no bootable device after upgrade to 29... help?

    So i've tried to fix it and failed... Please advice.

    [root@localhost-live liveuser]# mount /dev/nvme0n1p2 /mnt/sysimage
    [root@localhost-live liveuser]# mount /dev/nvme0n1p1 /mnt/sysimage/boot
    [root@localhost-live liveuser]# mount --bind /dev /mnt/sysimage/dev
    [root@localhost-live liveuser]# mount --bind /proc /mnt/sysimage/proc
    [root@localhost-live liveuser]# mount --bind /sys /mnt/sysimage/sys
    [root@localhost-live liveuser]# chroot /mnt/sysimage
    chroot: failed to run command ‘/bin/bash’: No such file or directory
    Last edited by Anonymous; 2nd October 2018 at 04:40 AM.

  9. #9
    Join Date
    Aug 2007
    Posts
    269
    Linux (Fedora) Firefox 61.0

    Re: no bootable device after upgrade to 29... help?

    So i've tried to fix it and failed... Please advice.

    [root@localhost-live liveuser]# mount /dev/nvme0n1p2 /mnt/sysimage
    [root@localhost-live liveuser]# mount /dev/nvme0n1p1 /mnt/sysimage/boot
    Your two mounts are wrong. /dev/nvme0n1p2 is your boot partition and should be mounted to /mnt/sysimage/boot. /dev/nvme0n1p1 is your EFI partition and should be mounted to /boot/efi. Your / root partition is on LVM so you actually need three mounts.

    Code:
    # mount /dev/nvme0n1p1 /mnt/sysimage/boot/efi
    # mount /dev/nvme0n1p2 /mnt/sysimage/boot
    # mount /dev/mapper/fedora-root /mnt/sysimage
    I have noticed something very wrong. Do you not have an actual grub executable grub_x64.efi ?

    EFI has 3 folders
    BOOT Dell fedora
    fedora folder content - grub.cfg grubenv
    grub.cfg content
    You need to retry the chroot with the three new mounts above and then install grub_x64.efi. Instructions are in the following page. This should also put an EFI boot variable in the list.

    https://fedoraproject.org/wiki/GRUB_...n_UEFI_systems

    dnf install grub2-efi shim

    Make sure that /boot/efi is mounted when you do this.
    This installs the signed shim and the GRUB 2 binary.

  10. #10
    Join Date
    Jun 2005
    Location
    Montreal, Que, Canada
    Posts
    5,402
    Linux (Android 8.0.0) Chrome 69.0.3497.100

    Re: no bootable device after upgrade to 29... help?

    Every iso usb that you create will have a section titled troubleshooting. There you will see "rescue a system". Run that and follow the instructions, including the chariot. Them run grub2-mkinstall /dev/SD? where SD? refers to the drive. Subsequently, run grub2-mkconfig /dev/SD?
    Try first with the F29 usb.
    Leslie in Montreal

    Interesting web sites list
    http://forums.fedoraforum.org/showth...40#post1697840

  11. #11
    Join Date
    Feb 2015
    Location
    Online
    Posts
    48
    Windows NT 10.0 Firefox 62.0

    Re: no bootable device after upgrade to 29... help?

    Quote Originally Posted by lsatenstein
    Every iso usb that you create will have a section titled troubleshooting. There you will see "rescue a system". Run that and follow the instructions, including the chariot. Them run grub2-mkinstall /dev/SD? where SD? refers to the drive. Subsequently, run grub2-mkconfig /dev/SD?
    Try first with the F29 usb.
    Ive used network f29 iso and was able to use rescue mode. From that I did chroot and tried dnf install grub2-efi shim it installed but the grub_x64.efi is still not found and not being recreated.... i have shimx64.efi Please advice and thank you for your help.

  12. #12
    Join Date
    Feb 2015
    Location
    Online
    Posts
    48
    Windows NT 10.0 Firefox 62.0

    Re: no bootable device after upgrade to 29... help?

    As much as I was determined to get it fixed I give up and did the reinstall. Thank you for helping out.

  13. #13
    Join Date
    Aug 2007
    Posts
    269
    Linux Firefox 52.0

    Re: no bootable device after upgrade to 29... help?

    Them run grub2-mkinstall /dev/SD? where SD? refers to the drive.
    There is no grub2-mkinstall. It is grub2-install. Also you didn't appear to read the other posts as the OP has an NVMe drive so it would be /dev/nvme0n1.

    Also you should specify the target explicitly as in grub2-install --target=x86_64-efi /dev/nvme0n1.

  14. #14
    Join Date
    Jun 2005
    Location
    Montreal, Que, Canada
    Posts
    5,402
    Linux (Fedora) Firefox 62.0

    Re: no bootable device after upgrade to 29... help?

    The last ISO for F29 is buggy, I have the same error. The preceding version is OK.
    But tomorrow, the official Beta2 for F29 is being presented. Wait for that one or install
    If you can't wait, these are the ones you want
    Code:
    1875902464 Oct  1 08:43 Fedora-KDE-Live-x86_64-29-20181001.n.0.iso
    1307 Oct  1 16:04 Fedora-Spins-29-x86_64-20181001.n.0-CHECKSUM
    401 Oct  1 16:04 Fedora-Workstation-29-x86_64-20181001.n.0-CHECKSUM
    1922039808 Oct  1 09:03 Fedora-Workstation-Live-x86_64-29-20181001.n.0.iso
    621805568 Oct  1 04:45 Fedora-Workstation-netinst-x86_64-29-20181001.n.0.iso



    https://kojipkgs.fedoraproject.org/compose/branched/
    Leslie in Montreal

    Interesting web sites list
    http://forums.fedoraforum.org/showth...40#post1697840

Similar Threads

  1. No Bootable Device
    By Ditrex001 in forum Installation, Upgrades and Live Media
    Replies: 8
    Last Post: 3rd November 2015, 12:15 AM
  2. Beta RC3 = A bootable device has not been detected
    By nimnull22 in forum F16 Development
    Replies: 16
    Last Post: 28th September 2011, 01:28 AM
  3. Fedora 14 - No bootable device found
    By alfoos in forum Installation, Upgrades and Live Media
    Replies: 1
    Last Post: 10th November 2010, 02:10 PM
  4. usb bootable device?
    By Jeff Sadowski in forum Using Fedora
    Replies: 1
    Last Post: 12th August 2005, 09:39 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •