That is different. That is your EFI system partition(ESP). You would need an additional partition for /boot.
1 Like
Ok, how big?
It has to be big enough to hold your kernels, initrams and firmware files. It depends on how much of that you have but I would say 1GB would probably be enough for most people.
You can check the current size of /boot with the command du -sh /boot
Well, how can I subsequently move the bootloader from /root to /boot?
The files you need are already in /boot. So the steps you need to follow are something like:
- Create the new partition
- Mount it somewhere other than
/boot. For the purposes of this example I will use/mnt/bootbut it could be anywhere. sudo umount /boot/efi- move all the files and directories in
/bootto/mnt/boot /bootshould now be empty.sudo umount /mnt/boot- Update
/etc/fstabwith an entry for/boot sudo mount /bootsudo mount /boot/efi
I haven’t tested that but it should give you the general concept.
It is important that you not reboot in the middle of that process.
3 Likes
Thank you all, you have helped me a lot! 
1 Like
I can confirm the suggested size is a go. I have a separate boot for several builds because I use f2fs on them, and have similar issues with not being easily readable at startup.
Here’s the blkid output for an example /boot:
/dev/nvme0n1p4: LABEL="f2fs-boot" UUID="8eaed965-8c54-442a-8ade-7ceb9e236fc4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="f2fs-boot" PARTUUID="9ef18220-ed7d-5645-bf71-891bcd1a51c8"
and the lsblk of the same partition:
├─nvme0n1p4 259:4 0 1000M 0 part
and the resulting system has been just fine…
The suggested procedure to change it over sounds good to me too. Fairly “safe” too, if done carefully (and with no reboot until fully finished!)
OK, now I have the time … thanks a lot, friends!
Everything fine with the boot partition in ext, problem solved and something learned again 
3 Likes
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.