I was reinstalling slowroll due to a separate update issues that broke my system. Near the end of the install process I was given the following warning:
What size is your EFI partition? There are alot of threads with the same topic. As TW and SR switched to grub2-bls, the size requirements for the EFI oartition increased to at least some GB (2-4).
You either need to increase the size in the partitioning step or switch to grub2-efi at the end of the installation (summary) screen.
Do a fresh reinstallation.
Unless I am misinterpreting what you are saying, the picture was taken during the install process
You need to erase the drive and do an expert partition.
Ok so, from what I am getting, I would:
I also typically do full disk encryption at this stage. Would I encrypt the EFI drive in this case, checking the “Encrypt Device” option in expert partition?
When I have more than one distro installed on the same machine, I’ve sometimes found 2GB to a be a bit tight - resulting in zypper-dup failing (btrfs with snapshots makes this worse). If space isn’t a problem, I suggest future proofing and picking at least 4GB, or use good old grub2.
Is this an old windows drive? It shouldn’t be proposing a 200MB EFI.
If this is an entire drive you want to format. I assume the installer didn’t format the existing EFI, I would do it again, use guided partitioner, select your disk, and select to remove everything in the dialog afterwards.
I decided to go about this using @Shortwave8115’s proposal, since it was the most familiar especially with enable disk encryption and other options like LVM. Here is what my partitions looks like now:
sudo fdisk -l
[sudo] password for root:
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: SAMSUNG MZVLQ1T0HBLB-00B00
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disklabel type: gpt
Disk identifier: 9D1196A9-2C1A-4FBF-BD6C-F07F0E8FBD95
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 2099199 2097152 1G EFI System
/dev/nvme0n1p2 2099200 1953861631 1951762432 930.7G Linux LVM
/dev/nvme0n1p3 1981761536 2000409230 18647695 8.9G Linux LVM
/dev/nvme0n1p5 1953861632 1981760479 27898848 13.3G Microsoft basic data
Partition table entries are not in disk order.
Disk /dev/mapper/cr_nvme-eui.002538d611444445-part3: 8.88 GiB, 9530842624 bytes, 18614927 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disk /dev/mapper/cr_nvme-eui.002538d611444445-part2: 930.66 GiB, 999285587968 bytes, 1951729664 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disk /dev/mapper/system-swap: 38.58 GiB, 41427140608 bytes, 80912384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disk /dev/mapper/system-root: 310.32 GiB, 333199704064 bytes, 650780672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disk /dev/mapper/system-home: 590.63 GiB, 634187153408 bytes, 1238646784 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1 vfat FAT32 3022-A040 165.9M 84% /boot/efi
├─nvme0n1p2 crypto_LUKS 2 86309a3f-06f4-4a18-8580-943032582bf3
│ └─cr_nvme-eui.002538d611444445-part2 LVM2_member LVM2 001 6HtHF1-qLkc-VXVR-Ivkl-Dfz2-CjEh-IlyWKl
│ ├─system-swap swap 1 3ea26d79-020e-48f2-b922-e8f1827ede0f [SWAP]
│ ├─system-root btrfs cee78edf-441d-4bd0-b40d-a702e78fd6b5 286.3G 7% /var
│ │ /usr/local
│ │ /root
│ │ /srv
│ │ /opt
│ │ /.snapshots
│ │ /
│ └─system-home btrfs 5519621b-e063-4345-a95a-0f5938eee848 587.6G 0% /home
├─nvme0n1p3 crypto_LUKS 2 921683dc-b5ec-4f4b-81ac-c9e18532e038
│ └─cr_nvme-eui.002538d611444445-part3 LVM2_member LVM2 001 dQr9GX-ZYmP-dNoz-HiHk-Dedc-wjDX-bGop98
│ └─system-root btrfs cee78edf-441d-4bd0-b40d-a702e78fd6b5 286.3G 7% /var
│ /usr/local
│ /root
│ /srv
│ /opt
│ /.snapshots
│ /
└─nvme0n1p5 ntfs RESTORE 78DCBF11DCBEC920
The EFI partition only has 1GB of space :(. Don’t know why guided partition can’t make an EFI partition with 2-4GB. At this point however my system is somewhat back to normal. So unless I accidentally brick my system again, I’m gonna wait a bit till life around me calms down to reinstall with the proper EFI partition size.
Yes it’s annoying. Last time I made a 4GB EFI beforehand with cfdisk and mounted it in the installer instead
A few days ago I happen to come across someone else also asking if they can resize the /boot/efi. I found out about gparted, which might be my way to go since I really don’t want to go through the process of reinstalling again. I’ll mark this as resolved.
I do have one more, somewhat unrelated question. When I reinstalled and did the guided partitioning setup, I decided to try out LVM, since I looked around and found that I can do future re-installation without touching the /home folder. I did not touch much else, and was never asked to specify the sizes of these volumes/partitions. I was wondering why the installer decided that root volume should takes up around 270GB (or 310GB according to my Dolphin file manager). Is that typical?
Not 100% sure I understand your situation, but if your are using btrfs for root with a standard layout, then home would be a subvolume, so the root partition can consume all available space. I guess that’s what the installer would do - take anything available.
On my main desktop, I have /home in a separate partition on a seperate nvme. I have tended to manually restrict the root partition to 100 GB or less. Currently the root partition it is 122GB to take all the remaining space on the SSD - this leaves it about half full (and I installed a lot of cruft over the years).
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.