Uncertain regarding mount locations—would appreciate any help with understanding.
Uncertain regarding mount locations—would appreciate any help with understanding.
I aimed to isolate Windows Boot Manager and GRUB onto separate partitions. I made a new partition, formatted it with fat32, and applied esp and boot flags. In fstab I updated the UUID to point to this new partition (sdb5). However, fstab needs a mount point. The original mount point was /boot/efi, which is where the Windows Boot Manager resides. If I leave the mount point unchanged, how does Ubuntu know to place GRUB on the correct partition? I assumed /boot/efi would contain the EFI files, but it seems confusing since I only changed the UUID and didn’t adjust the mount point yet. Instead of creating a new directory inside sdb5 and mounting it, I wondered if there’s another way to set up GRUB correctly.
For UEFI, the boot partition must always be the first one on the drive (like /dev/sda1 in your case), and it's not possible to have two separate UEFI partitions on the same drive. Therefore, your /dev/sdb5 cannot be used for /boot/efi. Your options are either to split your Linux and Windows installations onto different SSDs or SSDs, or to keep them sharing the same UEFI partition as before.
No, I'm not installing Android 86 on your Windows tablet. Let me know if you need help with anything else!
It varies by distribution. Generally, /dev/sda1 is mounted as /boot for EFI systems, while Windows uses a boot manager. Please specify your distro so I can give more accurate details. You might also want to share your /etc/fstab file.
It seems you're asking about file locations and mount points. On SDA2, /boot/efi is typically where the EFI system partition resides. It's not just a folder inside a partition but a special area marked for bootloaders. In your case, it was likely sdb1, which is a common mount point for the EFI system. The umask and permissions matter too, as they control access to that directory. This setup helps Linux recognize the correct files during boot.
The EFI directory is simply a folder in your root filesystem where you can mount files, though the system requires a boot partition. The "esp" label is just a temporary name for your EFI partition, which in your scenario is /boot/efi.
Your system setup is a bit confusing. When you create a new fat32 partition, it's usually assigned to a specific device like sdb4. If you don't explicitly tell it where to place it, it might default to the first available space on that device. However, using mount options like esp and boot can help guide the system, but it still depends on how the filesystem is managed. When you use tools like mount or mount-agent, they often handle partition assignment automatically. So even without explicit instructions, the system should recognize the correct location based on its logic.
You don't need to think about partitions when working with directories. There is only one folder tree and it's /, which points to your root partition. If you mounted /dev/sdb4 to / then that's where new directories will be placed unless one of the intermediate directories has another partition mounted to it. If you want a better understanding of how this works try reading this . It doesn't because it isn't. It's created in your root tree and then /dev/sb3 is mounted to it, if you specify that in your fstab file or do it manually of course - it won't happen automagically.
The folder resides on the sdb4 partition, which is mounted at the root. Inside, you create a directory called /boot/ubuntu within that directory, and then mount sdb3 over /boot/ubuntu, which sits inside sdb4. This means sdb3 is mounted at the top of sdb4? Clarify your setup if you're unsure about the layers.