You wiped the partition but the boot menu still shows Fedora
You installed Fedora alongside Windows or another Linux distribution six months ago. The experiment is over. You want the disk space back and a clean boot menu. You cannot just delete the partition in Disk Management and reboot. The bootloader still expects Fedora to be there. A missing partition leaves the boot menu broken and your remaining operating system inaccessible.
What the bootloader is actually doing
Dual-boot systems share one boot manager. Fedora's installer defaults to installing GRUB in the EFI System Partition or the master boot record. GRUB acts as a traffic cop. It loads first, reads a configuration file, and hands control to whichever kernel you select. When you wipe the Fedora root partition, GRUB's configuration file still contains a menu entry pointing to a filesystem that no longer exists. The remaining operating system is fine. The boot manager is just confused. You need to reclaim the disk space and then retrain the boot manager to ignore the missing entry.
Modern Linux distributions generate their GRUB configuration automatically. The file you see at boot lives in /boot/grub2/grub.cfg. That file is read-only by design. You never edit it manually. The real configuration lives in /etc/default/grub and /etc/grub.d/. Running the configuration generator scans your disk, finds available kernels, and rebuilds /boot/grub2/grub.cfg from scratch. If Fedora is gone, the scanner skips it and the menu entry disappears.
Reboot before you debug. Half the time the symptom is gone.
Reclaim the disk space and fix the boot menu
Start by booting into your remaining operating system. Open a terminal and verify you are looking at the correct disk. Deleting the wrong partition destroys data permanently. Run lsblk to see the current layout. This command shows device names, mount points, and filesystem types in a clean tree structure.
# Show all block devices with filesystem labels and mount points
lsblk -f
# Identify the Fedora root partition by its ext4/xfs label or mount path
# Note the device name like /dev/nvme0n1p3 or /dev/sda2
If you are on a system with multiple drives, lsblk prevents accidental cross-disk mistakes. Look for the partition that matches your Fedora installation. It will typically be formatted as ext4 or xfs and will not have a mount point if you are currently booted into a different OS.
Once you have confirmed the device name, use fdisk to remove the partition. The partition table does not store data. It only tells the kernel where partitions begin and end. Removing the entry from the table marks the space as unallocated.
# Open the disk containing the Fedora partition in interactive mode
sudo fdisk /dev/sdX
# Replace sdX with your actual disk, not the partition number
# Type 'p' to print the current table and confirm the partition number
# Type 'd' to delete, then enter the partition number when prompted
# Type 'w' to write the new table to disk and exit
# The kernel may print a warning about remounting the disk
The w command updates the partition table immediately. The filesystem data remains on the disk until you overwrite it, but the operating system no longer recognizes it as a valid volume. You can now expand your remaining partition or leave the space unallocated for future use.
Next, regenerate the GRUB configuration. The command differs slightly depending on your remaining distribution. Debian and Ubuntu derivatives use update-grub. RHEL, Fedora, and their derivatives use grub2-mkconfig. Both commands perform the same operation: scan the disk, rebuild the menu, and write the new configuration.
# Debian/Ubuntu/Mint: regenerate GRUB config from /etc/default/grub
sudo update-grub
# RHEL/Fedora/CentOS: explicitly output to the boot directory
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
# The command scans /boot and /etc/grub.d for available kernels
# It will print a line for each OS it detects
If your remaining OS is Windows, GRUB is not managing the boot process. Windows uses its own Boot Manager. In that case, you do not need to run any Linux commands. Windows Disk Management handles the partition deletion, and the firmware boot order automatically falls back to the Windows Boot Manager. Only run the GRUB commands if your remaining OS is Linux.
Trust the package manager. Manual file edits drift, snapshots stay.
Verify the system boots cleanly
Restart the machine and watch the boot sequence. The GRUB menu should no longer list Fedora. If you are using UEFI, the firmware boot menu might still show a Fedora entry. That is normal. The firmware stores boot entries separately from the disk. You can clean them up later with efibootmgr. For now, verify that your remaining OS loads without interruption.
Once you are back in the terminal, confirm the space is actually free. Run lsblk again. The deleted partition should no longer appear. If you want to reclaim the space for your existing partition, use gparted or fdisk to extend it into the unallocated region. Never shrink a partition while it is mounted. Boot from a live USB if you need to resize your active filesystem.
Run journalctl -b | grep -i grub to check for boot-time warnings. A clean boot produces no GRUB errors. If you see error: unknown filesystem or no such partition, the configuration generator did not run correctly or you edited the wrong disk. Reboot into your live environment and rerun the configuration command.
Run journalctl first. Read the actual error before guessing.
Common pitfalls and what the error looks like
The most frequent mistake is deleting the EFI System Partition instead of the Fedora root partition. The ESP is a small FAT32 partition, usually 100 to 550 megabytes, mounted at /boot/efi. It holds bootloaders for every OS on the disk. Deleting it breaks booting for all operating systems. Always verify the filesystem type and size before running fdisk.
Another common issue is LVM confusion. Fedora often uses LVM for the root filesystem. The physical volume lives on a partition, but the logical volume sits on top. Deleting the underlying partition breaks the LVM metadata. Use sudo pvs and sudo vgs to identify LVM structures before touching fdisk. If you see fedora-root or fedora-swap in the output, you are dealing with LVM. Remove the volume group first with sudo vgremove fedora, then delete the physical partition.
Windows users sometimes see a black screen with GRUB loading. Please wait... followed by a blinking cursor. This happens when GRUB is still the primary boot entry in the UEFI firmware, but the Linux partition is gone. Open a Linux live USB, mount the ESP, and run sudo efibootmgr -b <bootnum> -B to remove the stale entry. Replace <bootnum> with the number shown by sudo efibootmgr. The firmware will then default to the Windows Boot Manager.
If the boot menu is gone, GRUB rescue is your friend, not your enemy.
When to use this approach versus alternatives
Use fdisk when you need a quick terminal-only partition wipe and are comfortable reading partition tables. Use GParted when you prefer a visual map of the disk layout and want to resize adjacent partitions immediately. Use Windows Disk Management when you are running Windows and only need to delete basic data partitions without touching bootloaders. Use efibootmgr when you want to completely remove GRUB from the firmware boot order and restore the native Windows boot manager. Stay on the upstream Linux boot manager if you only deviate from the defaults occasionally.