On Fedora 43 KDE, I accidentally deleted an EFI partition using Partition Manager

Ask Fedora
1

This happened because in Dolphin I right-clicked on a third-party HDD mounted as NTFS that I wanted to format as ext4. I right-clicked on this drive and selected “Format or open with Partition Manager.” Partition Manager opened on my system SSD, and I started deleting the existing partitions before realizing what I’d done: I deleted the first one, nvme0n1p1.
This was the EFI one.

I booted from the live USB, but I’m stuck trying to repair this partition.

I even considered reinstalling the system, but I’m having the same problem. I can’t launch the installation, neither with the graphical tool nor via the command line.

I’m encountering a problem every minute, which is why I need your help.

Here is the technical information about my disks :

$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0   2.7G  1 loop /run/rootfsbase
sda           8:0    0   1.8T  0 disk
└─sda1        8:1    0   1.8T  0 part
sdb           8:16   0   1.8T  0 disk
├─sdb1        8:17   0    16M  0 part
└─sdb2        8:18   0   1.8T  0 part
sdc           8:32   0   1.8T  0 disk
└─sdc1        8:33   0   1.8T  0 part
sdd           8:48   0 111.8G  0 disk
└─sdd1        8:49   0 111.8G  0 part
sde           8:64   0 447.1G  0 disk
└─sde1        8:65   0 447.1G  0 part
sdf           8:80   1   7.3G  0 disk
├─sdf1        8:81   1     3G  0 part /run/initramfs/live
└─sdf2        8:82   1    30M  0 part
zram0       251:0    0     8G  0 disk [SWAP]
nvme0n1     259:0    0 465.8G  0 disk
├─nvme0n1p1 259:1    0     1M  0 part
├─nvme0n1p2 259:2    0     2G  0 part
└─nvme0n1p3 259:3    0 463.8G  0 part


$ sudo lsblk -f
NAME        FSTYPE    FSVER            LABEL                                       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       erofs                                                                  c49c3ecb-832b-440f-89b5-a601286ebff0       0   100% /run/rootfsbase
sda
└─sda1      BitLocker 2                HELEANA BarraCuda_2To 26/11/2024            d1a85847-3166-4483-920b-f08d25c4256a
sdb
├─sdb1
└─sdb2      BitLocker 2                HELEANA SSD_Crucial_2024_2TB 15/12/2024     4ebccd8f-8494-4df2-a84d-b70481ad288d
sdc
└─sdc1      BitLocker 2                HELEANA Hitachi_2To 04/11/2024              e77f97f7-0cc7-4f00-b037-2654791ce8ec
sdd
└─sdd1      BitLocker 2                HELEANA SSD_Intel_120 04/11/2024            dbc0210c-b4fa-4ee1-9fb4-43822d30ed9f
sde
└─sde1      BitLocker 2                HELEANA SSD_SanDisk_Ultra_II_480 04/11/2024 79e6d440-1bef-48cc-a7f0-6221af0d71fc
sdf         iso9660   Joliet Extension Fedora-KDE-Live-43                          2025-10-23-04-17-29-00
├─sdf1      iso9660   Joliet Extension Fedora-KDE-Live-43                          2025-10-23-04-17-29-00                     0   100% /run/initramfs/live
└─sdf2      vfat      FAT16            BOOT                                        BA0E-CF8F
zram0       swap      1                zram0                                       402c2c06-9950-436c-ab95-5f1bf914d695                [SWAP]
nvme0n1
├─nvme0n1p1 vfat      FAT32                                                        CF50-9EC9
├─nvme0n1p2 ext4      1.0                                                          51b106bd-07f4-41ff-9957-12de55aa0e58
└─nvme0n1p3 btrfs                      fedora                                      074f4156-a745-4959-8bfd-0b3dd0d48a63


$ sudo fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: PNY CS3030 500GB SSD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: EB2F669F-CF37-47CD-8FFE-1E3B247BFC5D

Device           Start       End   Sectors   Size Type
/dev/nvme0n1p1    2048      4095      2048     1M BIOS boot
/dev/nvme0n1p2    4096   4198399   4194304     2G Linux extended boot
/dev/nvme0n1p3 4198400 976773119 972574720 463.8G Linux filesystem

Thank you

2

It’ll be fine. I’m going to reinstall the system.

The problem with the installer is that I have to boot the live environment with the Troubleshooting → Simple graphics mode option.

3

This tells me you installed in legacy boot mode and not uefi mode. Was that intentional or an oversight?

To use uefi booting and installation the bios must boot the live media in uefi mode which is selected by the bios boot menu (usuaily the F10 or F11 key from the bios splash screen) or by setting bios to use only uefi booting in the bios setup menus.