Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Unable to boot after 20.04 install on multiple O/S setup

  1. #1
    Join Date
    May 2020
    Beans
    6

    Unable to boot after 20.04 install on multiple O/S setup

    I had a working ubuntu 16.04 LTS and windows 10 dual boot setup with spare space, so after booting up with a usb 20.04 image to ensure it worked fine I decided to install it to a new empty partition.
    I now find that I'm unable to boot any partition, even after following various boot-repair tutorials.

    My current boot-repair diagnostic file is on https://paste.ubuntu.com/p/9fc8q8hbpq/

    My BIOS say's I have legacy mode enabled, but boot-repair claims it's set to UEFI. Don't understand why that is.
    If I set UEFI (secure mode or insecure mode) I don't get any options other than booting the HD, which when selected just goes back to the error.

    The message I get when the BIOS is set to legacy shows:

    'System BootOrder not nofound'
    'Creating boot entry "Boot0000" with label "ubuntu" for file "\EFI\ubuntu\sGNU GRUB version 2.04"'

    I have tried the following from grub:
    grub> ls
    (proc) (hd0) (hd0,msdos7) (hd0,msdos6) (hd0,msdos5) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1)
    grub> set root=(hd0,msdos1)
    grub> linux /vmlinuz
    grub> initrd /initrd.gz
    grub> boot

    this will take me to initramfs with the error "can't find /root in /etc/fstab"

    I'm totally stumped, and would appreciate help on getting my O/S's booting agian.
    Thanks.

  2. #2
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Unable to boot after 20.04 install on multiple O/S setup

    You cannot mix BIOS/MBR and UEFI/gpt.
    And Ubuntu lets you install in UEFI Mode to MBR drive, and it really should not.

    Windows only boots in BIOS mode from MBR partitioned drive. It has to have boot flag on the primary NTFS partition with its boot files. You have all the Windows boot files in sda3, so need to have boot flag on sda3.

    UEFI requires boot flag (really esp flag) on ESP - efi system partition which is FAT32. But you can only have one boot flag per drive
    So move boot flag back to sda3.

    You may need to reinstall BIOS grub (grub-pc) in BIOS boot mode, to have correct grub in MBR.

    New UEFI systems have 3 ways to boot, UEFI with Secure Boot, UEFI (without Secure Boot), and BIOS/CSM/Legacy (which also requires Secure Boot to be off).

    Default boot settings in UEFI are for installed systems.

    But you can boot external devices in either UEFI or BIOS mode, just by selecting correct entry in UEFI menu.
    Some installers seem to make USB flash drive in boot one mode or other, although ISO is configured to boot in either mode and most install tools create a bootable flash drive that will boot either way.
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  3. #3
    Join Date
    May 2020
    Beans
    6

    Re: Unable to boot after 20.04 install on multiple O/S setup

    Still no luck I'm afraid.

    I moved the boot flag back to sda3 and eventually completely reinstalled grub via:

    root@ubuntu:~# mount /dev/sda1 /mnt
    root@ubuntu:~# mount -t proc proc /mnt/proc
    root@ubuntu:~# mount -t sysfs sys /mnt/sys
    root@ubuntu:~# mount -o bind /dev /mnt/dev
    root@ubuntu:~# chroot /mnt

    Code:
    root@ubuntu:~/grub_restore# apt purge -y grub*-common
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Note, selecting 'grub-common' for glob 'grub*-common'
    Note, selecting 'grub2-common' for glob 'grub*-common'
    The following packages will be REMOVED:
      grub-common* grub-gfxpayload-lists* grub-pc* grub-pc-bin* grub2-common* os-prober*
    0 upgraded, 0 newly installed, 6 to remove and 19 not upgraded.
    After this operation, 16.8 MB disk space will be freed.
    E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
    (Reading database ... 290045 files and directories currently installed.)
    Removing os-prober (1.70ubuntu3.3) ...
    dpkg: warning: while removing os-prober, directory '/var/lib/os-prober' not empty so not removed
    Removing grub-gfxpayload-lists (0.7) ...
    Removing grub-pc (2.02~beta2-36ubuntu3.23) ...
    Purging configuration files for grub-pc (2.02~beta2-36ubuntu3.23) ...
    Removing grub2-common (2.02~beta2-36ubuntu3.23) ...
    Removing grub-pc-bin (2.02~beta2-36ubuntu3.23) ...
    Removing grub-common (2.02~beta2-36ubuntu3.23) ...
    Purging configuration files for grub-common (2.02~beta2-36ubuntu3.23) ...
    Processing triggers for man-db (2.7.5-1) ...
    Processing triggers for install-info (6.1.0.dfsg.1-5) ...
    
    oot@ubuntu:~/grub_restore# apt install -y grub-pc
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following additional packages will be installed:
      grub-common grub-gfxpayload-lists grub-pc-bin grub2-common os-prober
    Suggested packages:
      multiboot-doc grub-emu xorriso desktop-base
    The following NEW packages will be installed:
      grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common os-prober
    0 upgraded, 6 newly installed, 0 to remove and 19 not upgraded.
    Need to get 2,238 kB/3,326 kB of archives.
    After this operation, 16.8 MB of additional disk space will be used.
    Get:1 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 grub-common amd64 2.02~beta2-36ubuntu3.23 [1,704 kB]
    Get:2 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 grub2-common amd64 2.02~beta2-36ubuntu3.23 [511 kB]
    Get:3 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 grub-gfxpayload-lists amd64 0.7 [3,658 B]
    Get:4 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 os-prober amd64 1.70ubuntu3.3 [19.1 kB]
    Fetched 2,238 kB in 0s (3,830 kB/s)
    Preconfiguring packages ...
    E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
    Selecting previously unselected package grub-common.
    (Reading database ... 289597 files and directories currently installed.)
    Preparing to unpack .../grub-common_2.02~beta2-36ubuntu3.23_amd64.deb ...
    Unpacking grub-common (2.02~beta2-36ubuntu3.23) ...
    Selecting previously unselected package grub2-common.
    Preparing to unpack .../grub2-common_2.02~beta2-36ubuntu3.23_amd64.deb ...
    Unpacking grub2-common (2.02~beta2-36ubuntu3.23) ...
    Selecting previously unselected package grub-pc-bin.
    Preparing to unpack .../grub-pc-bin_2.02~beta2-36ubuntu3.23_amd64.deb ...
    Unpacking grub-pc-bin (2.02~beta2-36ubuntu3.23) ...
    electing previously unselected package grub-gfxpayload-lists.
    Preparing to unpack .../grub-gfxpayload-lists_0.7_amd64.deb ...
    Unpacking grub-gfxpayload-lists (0.7) ...
    Selecting previously unselected package grub-pc.
    Preparing to unpack .../grub-pc_2.02~beta2-36ubuntu3.23_amd64.deb ...
    Unpacking grub-pc (2.02~beta2-36ubuntu3.23) ...
    Selecting previously unselected package os-prober.
    Preparing to unpack .../os-prober_1.70ubuntu3.3_amd64.deb ...
    Unpacking os-prober (1.70ubuntu3.3) ...
    Processing triggers for systemd (229-4ubuntu21.28) ...
    Processing triggers for ureadahead (0.100.0-19.1) ...
    ureadahead will be reprofiled on next reboot
    Processing triggers for man-db (2.7.5-1) ...
    Processing triggers for install-info (6.1.0.dfsg.1-5) ...
    Setting up grub-common (2.02~beta2-36ubuntu3.23) ...
    update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
    Running in chroot, ignoring request.
    Setting up grub2-common (2.02~beta2-36ubuntu3.23) ...
    Setting up grub-pc-bin (2.02~beta2-36ubuntu3.23) ...
    Setting up os-prober (1.70ubuntu3.3) ...
    Setting up grub-pc (2.02~beta2-36ubuntu3.23) ...
    
    Creating config file /etc/default/grub with new version
    Installing for i386-pc platform.
    Installation finished. No error reported.
    Generating grub configuration file ...
    Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
    Found linux image: /boot/vmlinuz-4.4.0-178-generic
    Found initrd image: /boot/initrd.img-4.4.0-178-generic
    Found linux image: /boot/vmlinuz-4.4.0-177-generic
    Found initrd image: /boot/initrd.img-4.4.0-177-generic
    grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
    Found Ubuntu 20.04 LTS (20.04) on /dev/sda7
    Adding boot menu entry for EFI firmware configuration
    done

    But I still get the BIOS error 'System BootOrder not nofound' on boot.

    current boot-repair diagnostic is: https://paste.ubuntu.com/p/Z5TJgq9BzF/
    Last edited by oldfred; 1 Day Ago at 02:27 PM. Reason: please use code tags for long terminal output # icon in Advanced Editor

  4. #4
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Unable to boot after 20.04 install on multiple O/S setup

    You booted live installer in UEFI mode.

    BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.
    But it looks like it correctly installed grub-pc.
    So is system trying to boot in UEFI mode. That is the BIOS/Legacy/CSM boot mode setting in UEFI.

    To boot my system in UEFI mode, all the UEFI settings were under the CSM setting which seemed backwards to me?
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  5. #5
    Join Date
    May 2020
    Beans
    6

    Re: Unable to boot after 20.04 install on multiple O/S setup

    It definitely says 'Legacy' in the BIOS. This is just so confusing - I now find that running boot-repair (after usb boot in 20.04) it seems to suggest it will reinstall grub-efi-amd64-signed etc.
    https://pastebin.ubuntu.com/p/7QgnzNjnSW/

    Not sure if I should attempt that. I'd rather not loose the ability to boot windows, but I just can't live without my Ubuntu being bootable!
    Last edited by losange13; 1 Day Ago at 05:00 PM.

  6. #6
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Unable to boot after 20.04 install on multiple O/S setup

    Pastebin link not working.

    But you need to always boot in BIOS mode.
    Boot Ubuntu live in BIOS mode from UEFI boot menu & add Boot-Repair using ppa.

    Make sure you get BIOS screen when booting live installer:
    Shows installer with screen shots. Both BIOS purple accessibility screen & UEFI black grub menu screen
    https://help.ubuntu.com/community/UEFI
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  7. #7
    Join Date
    May 2020
    Beans
    6

    Re: Unable to boot after 20.04 install on multiple O/S setup

    Sorry - corrected the pastebin like above, but will try to boot live in BIOS mode...

  8. #8
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Unable to boot after 20.04 install on multiple O/S setup

    Because you booted live installer with Boot-Repair in UEFI mode and have an ESP, it wants to reinstall grub in UEFI boot mode.
    You have to always be in BIOS mode.

    You also need to use advanced mode and choose install & drive to place grub bootloader.
    Otherwise it installs grub for first install found. I think you want grub from 20.04.

    https://sourceforge.net/p/boot-repair/home/Home/

    Anyone with multiple drives or multiple installs, should use Boot-Repair's advanced mode with then give options to choose correct drive or correct install. Default with multiples often is not best alternative.
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  9. #9
    Join Date
    May 2020
    Beans
    6

    Re: Unable to boot after 20.04 install on multiple O/S setup

    getting further now, although not quite there - I'm able to boot in BIOS mode to my 18.04 on /dev/sda1 using a utility from Ultimate Boot CD iso.

    UBCD iso boot -> Boot Management -> Smart Boot Manager -> 'selected boot from HD partition 0' to get to old 18.04 grub menu.

    boot-repair still shows that it wants to reinstall grub-efi-amd64-signed of sda1, which is not actually installed on sda1.

    http://pastebin.ubuntu.com/p/Xw4xkGwxsp/

    Still not convinced those are the actions I want to carry out.

    But with advanced mode, there's quite a lot of options that I'll need to review before I commit to any changes.
    At least for now, I can use my system booting via Smart Boot Manager.

  10. #10
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Unable to boot after 20.04 install on multiple O/S setup

    Because you have the ESP and your fstab has the mount of your ESP, Boot-Repair is seeing your install as UEFI.
    I thought the grub-pc install would remove the mount of the ESP. But you reinstalled grub for the install in sda1, not the newer 20.04 install.

    # /boot/efi was on /dev/sda6 during installation
    UUID=22DB-370F /boot/efi vfat umask=0077 0 1
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

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