22
lsblk:
I need to enlarge nvme0n1p2 by shrinking nvme0n1p3 (LUKS)
do I have to do something with /boot/efi? enlarge as well?
backing up as of now
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Aug 2025
22 points (100.0% liked)
Linux
57274 readers
249 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
Misleading, I have a dual boot set-up with multiple UKIs that require ~300MiB each and therefore have a 4GB EFI part, there is no strict required size for a EFI partition and no it does not affect boot times. OP, If I were you, I would familiarise myself with chroot. When you resize your Linux partition to accommodate a larger boot partition (the first partition) often times partition UUIDs (unique universal identifier) have a quirk of wanting to change that then requires you to update your /etc/fstab to tell Linux where to look for all your partitions, without being able to directly boot your OS. Is it possible to grow your EFI and resize your Linux Part? Yes. Is is an easy risk free process? Absolutely not. If you prefer doing a clean instal with less manual work I would follow the resize and reinstall all approach described above.