Ubuntu 20.04.2 LTS will not boot [duplicate]
Solution 1:
When you install Windows, Windows assumes it is the only operating system (OS) on the machine, or at least it does not account for Linux. So it replaces GRUB with its own boot loader. What you have to do is replace the Windows boot loader with GRUB. I've seen various instructions for replacing GRUB by mucking around with GRUB commands or some such, but to me the easiest way is to simply chroot
into your install and run update-grub
. chroot
is great because it allows you to work on your actual install, instead of trying to redirect things here and there. It is really clean.
Here's how:
- Boot from the live CD or live USB, in "Try Ubuntu" mode.
-
Determine the partition number of your main partition.
sudo fdisk -l
,sudo blkid
or GParted (which should already be installed, by default, on the live session) can help you here. I'm going to assume in this answer that it's/dev/sda2
, but make sure you use the correct partition number for your system!If your main partition is in an LVM, the device will instead be located in
/dev/mapper/
, most likely,/dev/mapper/{volume}--{os}-root
where{volume}
is the LVM volume name and{os}
is the operating system. Executels /dev/mapper
for the exact name. -
Mount your partition:
sudo mount /dev/sda2 /mnt #Replace sda2 with the partition from step 2
If you have a separate
/boot
,/var
or/usr
partitions, repeat steps 2 and 3 to mount these partitions to/mnt/boot
,/mnt/var
and/mnt/usr
respectively. For example,sudo mount /dev/sdXW /mnt/boot sudo mount /dev/sdXY /mnt/var sudo mount /dev/sdXZ /mnt/usr
replacing
sdXW
,sdXY
, andsdXZ
with the respective partition numbers. -
Bind mount some other necessary stuff:
for i in /sys /proc /run /dev; do sudo mount --bind "$i" "/mnt$i"; done
-
If Ubuntu is installed in EFI mode (see this answer if you're unsure), use
sudo fdisk -l | grep -i efi
or GParted to find your EFI partition. It will have a label ofEFI
. Mount this partition, replacingsdXY
with the actual partition number for your system:sudo mount /dev/sdXY /mnt/boot/efi
-
chroot
into your Ubuntu install:sudo chroot /mnt
-
At this point, you're in your install, not the live session, and running as root. Update grub:
update-grub
If you get errors or if going up to step 7 didn't fix your problem, go to step 8. (Otherwise, it is optional.)
-
Depending on your situation, you might have to reinstall grub:
grub-install /dev/sda update-grub # In order to find and add windows to grub menu.
-
If Ubuntu is installed in EFI mode, and EFI partition UUID has changed, you may need to update it in
/etc/fstab
. Compare it:blkid | grep -i efi grep -i efi /etc/fstab
If current EFI partition UUID (from
blkid
) differs from the one in/etc/fstab
, update/etc/fstab
with current UUID. -
If everything worked without errors, then you're all set:
exit sudo reboot
At this point, you should be able to boot normally.
If you cannot boot normally, and didn't do step 8 because there were no error messages, try again with step 8.
- Sometimes giving GRUB2 the correct configuration for your partitions is not enough, and you must actually install it (or reinstall it) to the Master Boot Record, which step 8 does. Experience helping users in chat has shown that step 8 is sometimes necessary even when no error messages are shown.
Solution 2:
The Windows installer doesn't care about other OS in the system. So it writes own code over the master boot record. Fortunately the solution is easy too.
You need to repair the MBR. Do the following
Boot using a live usb/cd of ubuntu.
Use boot-repair
to fix the problem.
After booting with live usb/cd, run following command in terminal:
sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
Use Recomended Repair
.
More info - https://help.ubuntu.com/community/Boot-Repair
Solution 3:
Boot from a live Ubuntu USB pendrive or CD
and
Install Boot-Repair on ubuntu by following steps
Open the terminal and run the following commands
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install boot-repair
After completing the installation you can launch it from System->Administration->Boot-Repair menu if you use Gnome, or search "boot-repair" in the dash if you use Unity. Then follow the following screenshots:
Method 1
- Click on the advanced options
- Tick the options shown below
- Change the tab to Grub Location Tab and Tick The options Shown in the figure
Press Apply and Reboot the system
Method 2
- Select the recommended Boot repair options as shown in the first screenshot
Documentation :
Solution 4:
Just install easyBCD
in Windows 7 and do
Add New Entry > Linux/BSD > (select ) Grub2 > (push) Add Entry
Then you can choose Ubuntu on the Windows 7 bootloader to go to Grub2 (previous bootloader).
Solution 5:
On EFI-based systems (such as most systems that shipped with Windows 8 or later), Windows will sometimes update its boot loader or reset it to be the default boot loader. This is particularly common when re-installing the OS or performing a major system update (upgrading to the latest Windows release, for instance). Note that Windows is unlikely to actually erase any GRUB files on an EFI-based computer. Everything needed to boot Ubuntu is still in place; it's just being bypassed. In these cases, a complete re-installation of GRUB is overkill, and in fact that carries a (small) chance that it will create new problems.
Thus, instead of re-installing GRUB in these cases, I recommend resetting GRUB (or whatever boot loader or boot manager you prefer) to be the default. There are several ways to do this, including:
-
EasyUEFI -- The easiest way to adjust the boot order, if the system is booting straight to Windows, is to use EasyUEFI, which is a free (for the basic version) third-party GUI tool for managing the EFI boot order. It's pretty self-explanatory -- locate the
ubuntu
entry in the list of boot options and move it to the top of the list. The next time you reboot, GRUB should come up. (If you use something other than GRUB, you'll need to locate its entry.) -
bcdedit
-- The Windowsbcdedit
tool can be used to set GRUB to the default boot order. The commandbcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi
, typed in an Administrator Command Prompt window, will do this; however, if your computer boots with Secure Boot active,bcdedit /set {bootmgr} path \EFI\ubuntu\shimx64.efi
will be required instead. In fact, the latter command will usually work even if Secure Boot is not in use, so I'd use that command first. Note that there's a more advanced Windows shell tool that requires a slightly different syntax than I've presented, but I don't recall the details. -
One-time boot to Ubuntu -- Most EFIs provide a built-in boot manager, accessed by hitting a function key, Esc, or Enter early in the system start process. Chances are the
ubuntu
entry to boot Ubuntu will show up in this boot manager menu, enabling you to boot to Ubuntu. Alternatively, you could boot to an Ubuntu emergency medium, like the installer booted in "try before installing" mode. Either way, you can then useefibootmgr
to adjust the boot order:- Type
sudo efibootmgr
to see the boot entries. - Note the current
BootOrder
line. - Locate the entry for
ubuntu
and note itsBoot####
number. - Type
sudo efibootmgr -o xxxx[,yyyy,zzzz,....]
to change the boot order, makingxxxx
the number for Ubuntu. What comes after that is most likely not very important, although I've noted that Windows seems to be likely to add itself back to the start of the boot order if it's not in the list. Thus, you should probably ensure that Windows is in the list, and it may be safest to re-order the list so that all the original entries are there, just with theubuntu
entry moved to the top of the list.
- Type
- Firmware setup utility -- Some EFIs' setup utilities enable you to adjust the boot order. Details vary greatly from one EFI to another, so I won't go into specifics, but you could look for such an option in your setup utility.
There are other variants on these procedures, such as using bcfg
in an EFI shell, using bless
in macOS, using my rEFInd to do a one-time boot, etc. I'd start with EasyUEFI, though; it's likely to be the simplest solution. Sometimes Windows insists on making itself the default every time it starts up, though, and reports indicate that bcdedit
may do a better job of dealing with that problem.
Note that none of the preceding applies to BIOS-mode installations; however, as most computers that shipped with Windows 8 or later boot in EFI mode, BIOS-mode installations are becoming increasingly rare, so in many cases it's better to deal with the issue in the EFI way rather than by blindly re-installing GRUB.