Its only a question to naming of boot sector

I got the following answer by https://askubuntu.com/questions/1562519/how-do-i-go-about-partitioning-my-hard-drive-for-an-ubuntu-installation/1562584#1562584

I could not agree, your meaning ?

what is the question?

1 Like

If you are trying to assign a LABEL (name) to the partition that has Ubuntu, the running OS cannot be Ubuntu.

To assign a label to that partition,

  • boot from a Live ISO and "Try Ubuntu"
  • open GParted
  • select the internal drive from the drop down
  • right click on the ext4 partition
  • choose "Label Filesystem"
  • enter the Label for your filesystem, and Apply the change
  • right-click on renamed partition and choose the "Information" option
  • take note of the UUID (I believe that may have changed ... and you will need to update the fstab and the grub settings after booting from the disk image of ubuntu)
  • in Terminal session, enter "sync"
  • exit GParted
  • reboot to Linux
2 Likes

As given in the comment by ChanganAuto : ESP is not boot partition.

I see in the given picture of GParted a fat32 partition, for me it is the boot partition. The ESP (EFI system partition) it is a part of the boot partition, mounting point /boot/efi. Is my understanding wrong ?

@ericmarceau The given partitions of my system (Dual-Boot) created automatically by WIN11, Ubuntu-Mate 22.04 installation procedure (to delete the former used Ubuntu-Gnome, Ubuntu-Mate 24.04 installation procedure had to that time no option (I did denied expert modus) to replace Ubuntu-Gnome by Ubuntu-Mate 24.04) and further installation via command line to get Ubuntu-Mate 24.04.. I did use during installation of Ubuntu-Mate only automatically default options, the given Labels are done by Ubuntu-Mate installation procedure (via GUI or command line). And to make it clear the given picture by Gparted of my system, it is a running DUAL-Boot system.

2 Likes

Maybe we would understand better if you share the snapshot of your GParted window displaying all the partitions & details for the disk in question. :slight_smile:

1 Like

The picture is given, refer to the Ask-Ubuntu link.

"Default" configuration doesn't really apply when you are trying to perform multi-boot, especially when Windows is involved.

Boot to Live ISO, then during the install process, you can choose "custom disk layout".

At that point it will bring you to something that looks like GParted but not quite. That is where you need to

  • choose the target partition to overwrite,
  • assign the filesystem type to perform formatting (do it even if not necessary because of possible updates to ext4),
  • assign a LABEL to the partition, if you want one for recognition,

then do the install.

Have you tried that sequence at any point?

1 Like

Default does mean not related to all possible installations, default does mean in respect to DUAL boot with WIN.

The theme is not how to get the system what I have. I described my way, I'm not interested in other ways (I have a working system), installed in the “space” of DUAL-Boot with WIN, only with default options given by Ubuntu-Mate.

The theme, as given in the comment by ChanganAuto : ESP is not boot partition. From my side of view this is wrong. Can someone agree or not ?

I am not sure if we have a terminology problem here.

'/boot/efi' contains all UEFI requirements, including boot-specifics for GRUB etc, for various OSs, each under their own folder.

So, if that is your viewpoint/stance/theme, then yes, you are correct.

Is that what you were asking?

1 Like

@ericmarceau Yes, thank you first.

It is not the original question, but can you also explain /boot.

From my side of view (but only embedded systems are my home) /boot only must have provide an address of executable code, the address given by BIOS-UEFI, to the address of /boot/efi, GRUB.

Is it correct ? (yes of course its not the original question, but the context is correct to complete the theme).

1 Like

/boot is where the kernel and initial RAM disk (initramfs) needs to go for a Linux installation.

A separate boot partition (like a ext4 partition) is optional. A /boot partition makes sense if you have an encrypted root partition (LUKS). A /boot wouldn't be the best idea If one disk boots multiple Linux OS since they may overwrite the other's kernel and cause boot issues.

The EFI partition (ESP) usually mounted at /boot/efi and stores the bootloader (EFI executable) for the UEFI system to boot the OS (Windows, Linux). In GRUB's case I think the executable will find its configuration on another partition (usually the one with /boot/grub).

I don't use GRUB. My system uses systemd-boot which I find much simpler. By design, it can use the kernel, bootloader (EFI executable) and configuration directly on the EFI (FAT32 ESP) partition, mounted under /boot. No separate /boot/efi mount is necessary because the ESP partition already has an EFI folder.

So I think it depends which bootloader you use. Both approaches are valid. In systemd-boot case, you'd need a larger EFI partition big enough to fit the kernel and initramfs too.

3 Likes

Yes of course, you did go further, but it is not my intention,

Yes or No ? It would be nice, you would give your additional reflection on AskUbuntu.