Ubuntu 24.04 UUID =/

[yancek]

You indicate that when you boot you see the grub menu. Have you followed the suggestion above when seeing that menu to hit the e key on your keyboard. This will change the screen and you should see the entry and there should be a line beginning with the work search and on that line it will show the root UUID. Make note of this and then boot the Ubuntu installer and use the Try option and when you get to a Desktop, open a terminal and enter the command blkid, hit the enter key and check the output and compare the UUID you wrote down earlier to the one on the drive which you installed Ubuntu to. From your posts above, it showed as sdb2. How many drives do you have and what are the sizes?

You indicate that you have reinstalled Ubuntu at least once. You do understand that the UUID for these partitions will change on each install, correct?

I noticed in post 5 your gparted output showed it was unable to read the vfat EFI partition. Do you still see this error when using gparted? Is the error you continue to get the same, the ALERT UUID ?? not found?

[userubu64]

You indicate that when you boot you see the grub menu. Have you followed the suggestion above when seeing that menu to hit the e key on your keyboard. This will change the screen and you should see the entry and there should be a line beginning with the work search and on that line it will show the root UUID. Make note of this and then boot the Ubuntu installer and use the Try option and when you get to a Desktop, open a terminal and enter the command blkid, hit the enter key and check the output and compare the UUID you wrote down earlier to the one on the drive which you installed Ubuntu to. From your posts above, it showed as sdb2. How many drives do you have and what are the sizes?

Yes, the system cannot detect the UUID of the sdb2 disk. Everything is identical, this can be seen in the screenshots on the 1st page.
In total, I have 2 flash drives for loading in live mode and installing the OS, as well as my internal M.2 SSD.
What do you mean when you ask how many disks do I have? I hope I answered this question.

You indicate that you have reinstalled Ubuntu at least once. You do understand that the UUID for these partitions will change on each install, correct?

Sure. I understand what a unique ID is, what it is needed for and that it is not static when reinstalling the system

I noticed in post 5 your gparted output showed it was unable to read the vfat EFI partition. Do you still see this error when using gparted? Is the error you continue to get the same, the ALERT UUID ?? not found?

The answer to all questions: Yes, it is.

[userubu64]

Are you doing LVM/encrypted install?
Since reinstalling try just ESP & / (root) as ext4.
If it does not boot, then run Boot-Repair and post link to summary report.

I'm using Ubuntu 24.04 LTS for installation.
Root is initially formatted as ext4, but if I change the ESP partition, the system is no longer detected in the BIOS
Link to the report: https://paste.ubuntu.com/p/ktkNjXM7k9/
(Remember that I reinstalled the system again and changed the ESP partition to ext4)
Bug fix has not run at this time

Please copy & paste the pastebin link to the BootInfo summary report ( do not post report), do not run the auto fix till reviewed. Use often updated ppa version with your USB installer or any working install over somewhat older ISO.
https://help.ubuntu.com/community/Boot-Repair &
https://sourceforge.net/p/boot-repair/home/Home/

It’s also interesting that the keyboard didn’t work on this laptop before, on UNIX systems
I know this because I first wanted to install Debian, which has an older kernel,
but I couldn't write a anything using the keyboard.
Now after updating Ubuntu 24.04 the keyboard works and I can write again =)
I think this suggests that the problem lies in the drivers for working with the SSD drive.

[tea for one]

Root is initially formatted as ext4, but if I change the ESP partition, the system is no longer detected in the BIOS
Link to the report: https://paste.ubuntu.com/p/ktkNjXM7k9/
(Remember that I reinstalled the system again and changed the ESP partition to ext4)
Bug fix has not run at this time

I think that you have misinterpreted oldfred's suggestion from post 20.
The suggestion was to allow the installer to create the essential partitions.
i.e. ESP which has to be FAT32 and system root ext 4.

It is no surprise that there were problems after changing the ESP to ext4.

I suggest that you re-install using only two partitions (ESP = FAT32 and root = ext4)
After installation, remove all USB devices.
If the PC doesn't boot successfully, then boot into a live session and run boot-repair again and post the link.

[userubu64]

I think that you have misinterpreted oldfred's suggestion from post 20.
The suggestion was to allow the installer to create the essential partitions.
i.e. ESP which has to be FAT32 and system root ext 4.

It is no surprise that you had problems after changing the ESP to ext4.

I suggest that you re-install using only two partitions (ESP = FAT32 and root = ext4)
After installation, remove all USB devices.
If the PC doesn't boot successfully, then boot into a live session and run boot-repair again and post the link.

I do this every time I install an operating system. I have 2 partitions after installing sdb1(ESP == FAT32) and sdb2(root == ext4)

Remarque:
I tried manual disk partitioning, at this time 3 partitions ESP, MBR, EXT4 are created.
But this also does not give any results (Which is not surprising, because nothing changes for me, because I boot via EFI)

[oldfred]

The Boot-Repair report says this:

Grub-efi would not be selected by default because no ESP detected.

It does look like you now have FAT32 on sda, your flash drive, but none on sdb.

All your UEFI entries show booting from GUID or partUUID that does not exist.
You can see partuuid on line 59 in report or by this:
sudo efibootmgr -v
and then partitions with the partuuids:
lsblk -e 7 -o name,fstype,size,fsused,label,partlabel,mountpoint ,uuid,partuuid

Minimum requirement for UEFI install is ESP - efi system partition and / (root). Root must be a Linux format, Ubuntu's default is ext4.
The ESP must be FAT32 with boot,esp flags if using gparted.
It can be small 50 to 100MB if planning only one instal wit grub on smaller drives, but for larger drives and potential future use or other boot loaders, 500 to 600MB is suggested.

You should eventually delete all the invalid UEFI entries. Years ago having too many entries caused issues. But no reason to have entries that will never work.
to see entries:
sudo efibootmgr -v
to delete entry where XXXX is number from above.
sudo efibootmgr -b XXXX -B
See also
man efibootmgr

[userubu64]

This issue has been resolved by other community members. If you want, I can insert a link to the solution.

[sidylaye]

Gg

[supertomk1]

Hopefully, I get out of this never ending craziness, also.
24.04 LTS
LTS because they know they have to work on too many issues. Anyway, installing 24.04.01 triggered some problems here and there for me. I quickly decided to go back to a plain 22.04 installation which now I know it's not so plain. I also fell into the UUID hell with many storage devices and USB drives including plugging into a different port generating new UUID's. It has been really crazy. A good things is that I know something like this can happen. Solving this mess was not very easy on me until now. EFI partitions including ones on the USB sticks, and EFI's have been living in our system setting module (let's just call it BIOS). I also tried zeroing HDDs. However, somehow, those UUID's managed to survive full-formatting, dismembering controllers and HDDs, totally being disconnected from any power source. I felt like someone is making a sick joke on me.

I am still insane after working on this issue for days, now always a week, and I feel that I am very close to the end. Right now, it's like my break time because I finally got to the point all the UUID's are clean and matching but getting the exact same error!

[supertomk1]

https://forums.linuxmint.com/viewtopic.php?t=418455