Where Does Pop!_OS Keep Boot Entries and Recovery Files?
Pop!_OS boots with systemd-boot entries in /boot/efi/loader/entries, keeps a recovery partition mounted at /recovery, and caches apt packages in /var/cache/apt/archives.
Last updated
Pop!_OS looks like Ubuntu but boots differently, which is where people get lost. It uses systemd-boot instead of GRUB. Each boot option is a small text file in /boot/efi/loader/entries, so troubleshooting a missing kernel means reading those files, not running update-grub.
The recovery partition is the other Pop specific location. A standard install reserves space mounted at /recovery with a full recovery image. That partition is what powers the refresh install option, and deleting it to reclaim space removes your built in rescue system.
Where Pop!_OS stores this, by platform
/boot/efi/loader/entries
One .conf file per boot entry. Kernel updates add and remove these automatically. Edit loader.conf in the parent loader folder to change the default entry or timeout.
/recovery
Holds the recovery image used by refresh install. Do not delete it to free space unless you have other recovery media. Reach it at boot by holding Space for the systemd-boot menu.
/var/cache/apt/archives
Downloaded .deb files stay here after install. Run sudo apt clean to empty it or check du -sh first. Standard Ubuntu behavior, Pop changes nothing about this folder.
Frequently asked questions
How do I boot into Pop!_OS recovery?
Reboot and hold Space to reach the systemd-boot menu, then pick the recovery entry or boot into the recovery partition. The recovery system can refresh the install while keeping files in your home folder. Back up first anyway since refresh reinstalls system files.
Does Pop!_OS use GRUB?
Yes. Unlike Ubuntu it does not use GRUB by default, so there is no grub.cfg to edit. Boot entries are text files in /boot/efi/loader/entries and the loader config is loader.conf one level up. Kernel updates rewrite these automatically.
Notice an outdated path? Let us know.