I have been working on adding Ubuntu to my PC for ROS2. I added a Samsung 990 to my computer so I could install it to a separate SSD.
I first did the "Try Ubuntu", and ran lsblk --nvme. This told me that nvme0n1 was the old Samsung 970 (which I have windows on), and nvme1n1 is Samsung 990, the new empty drive.
I tried installing Ubuntu with "Erase disk and install Ubuntu" and specified nvme1n1, however after it was completed, the BIOS showed that Ubuntu was on 970, and the windows boot was gone.
So then I tried a flash drive bootable windows install, and specified Disk 1. This seems to have worked correctly; I can launch both Windows or Ubuntu from the BIOS.
However, my one problem is that in the BIOS, under Boot Priority, it says...
- Windows Boot Manager (M.2_3: Samsung SSD 970 EVO Plus 1 TB)
- Ubuntu (M.2_3: Samsung SSD 970 EVO Plus 1 TB)
AKA that they are both on 970, even though in GParted, it seems to show all the Microsoft stuff/ntfs is on nvme1 (see the image below). Additionally, when GRUB first opens before Linux, there is no option to launch windows, I have to launch it from BIOS.
GParted shows that ubuntu is on nvme0 and windows is on nvme1:
Does anyone know what has caused the inconsistency between my install and what the BIOS is showing? Thanks!
It's not an inconsitency, it's only the boot loader which has been installed into the already existing ESP (EFI System Partition).
You can check with the terminal comand
lsblk -f
in Ubuntu which partitions are used for your/
- partition and the ESP.If grub doesn't show Windows in the grub menu, Windows hybernation may be the cause. It may also caused by grub configuration, you may need to add the line
to
/etc/default/grub
and runsudo update-grub
after doing so.But before doing so, just run
sudo update-grub
and look at it's output, it will tell you exactly if grub is checking for other operating systems or not. Here an example from my system: