The Recovery Partition is a full copy of the Pop!_OS installation disk. It can be used exactly the same as if a live disk copy of Pop!_OS was booted from a USB drive. The existing operating system can be repaired or reinstalled from the recovery mode. You can perform a refresh install, which allows you to reinstall without losing any user data or data in your home directory. Recovery can also perform a clean install, which resets all OS data.
To boot into recovery mode, bring up the systemd-boot menu by holding down SPACE while the system is booting, or by holding/tapping any function keys NOT used to Access the BIOS/Boot Menu (On non-System76 hardware, try the keys F1 through F12).
Note: These instructions assume Pop!_OS is the only OS running on your system. If you are booting more than one operating system you may need to change your boot order first, or manually select the Pop!_OS Disk from your BIOS/Boot menu.
Once the menu is shown, choose Pop!_OS Recovery.
Note: The Pop!_OS recovery environment will not have your WiFi password saved. Once booted into the live environment, you will need to reconnect manually to your WiFi in order to access the internet.
This option erases the current install along with all user files. It reformats the drive partitions and installs the version of Pop!_OS contained in the Recovery partition.
Steps to back up user-files from a Live Disk/Recovery can be found here.
**Note:**The Recovery partition OS version will either be the same as the OS version that shipped with your computer, or the latest version to which the Recovery partition has been updated.
The Refresh Install option allows you to reinstall the OS without losing user account information and data in the home directory.
Note: User-installed applications not stored in the Home folder (e.g. .deb or apt installed versions) will need to be re-installed.
Refresh Install option is not present on the install screen, one of two things may be true.
Your drive is encrypted. The Refresh install option may appear after decrypting the drive. A notice about decrypting the drive will be present above the install options.
The Recovery version is out of date. See the update instructions.
Once Recovery has booted, the Pop Installer will start automatically. If the system needs to be reinstalled, go ahead and continue the installation steps as demonstrated here.
If the existing install is encrypted, please see the encrypted disk instructions.
If the existing OS install needs to be repaired, the installer application should be closed. An app menu is located in the top-left of the screen with the name of the currently running application (in this case: "Install Pop!_OS"). Click on the app menu and select
Quit. Alternatively, you can use the installer app to select keyboard and language settings, and then click the
Try Demo Mode button in the lower-left corner of the install page.
Note: Do not choose any install or repair options, as this could result in data loss.
Follow the instructions below to access the existing OS drive:
First, press SUPER+T to open a terminal, then type this command:
This will show you the name of the main internal drive, which will have 4 partitions on it. We will be working with the 3rd partition. If the main drive is an NVMe drive, it will be called
/dev/nvme0n1p3 and if the drive is a SATA or regular M.2 drive, it will be called
Next, run this command:
|SATA Drives||NVMe Drives|
If the command fails and says
mount: /mnt: unknown filesystem type 'crypto_LUKS', then the hard drive has been encrypted, and additional commands are needed to unlock it.
To get access to an encrypted disk, these additional commands need to be run in order to unlock the disk. Please use the
lsblk command described above to determine the correct drive and partition.
|SATA Drives||NVMe Drives|
sudo lvscan sudo vgchange -ay
Note: Pay attention to what the
cryptdata group is called. If it is named something other than
data-root, substitute the correct info into this next command. Make sure that
-root is on the end:
sudo mount /dev/mapper/data-root /mnt
And now the existing hard drive can be accessed by going to the
/mnt folder. To use the Files program, go to '+ Other Locations' -> 'Computer' and then click on the
Chroot runs commands as if the existing operating system had been booted. Once these commands are run, package manager (
apt) and other system-level commands can be run.
The EFI partition is the next partition to be mounted. To help identify it, this partition is usually around 512MB, and is labeled as
|SATA Drives||NVMe Drives|
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done sudo chroot /mnt
With this last command, you will have root access to your installed system. Once the drive is accessed, commands for maintenance can be run on the installed system. For example, package manager repair commands. You can also access your files with Files via "Other Locations" -> "Computer" -> "mnt."
Once you are done accessing files or running commands in your installed OS, you can exit from
chroot and reboot the computer, by running these commands:
Update Recovery Partition
It is important to keep the Recovery Partition up to date as it is not updated with the installed OS. Updating the Recovery partition will allow you to reinstall the newest OS, instead of the previous Recovery version.
The Recovery Partition can be updated from within the OS by either using Settings or from a terminal.
If using Settings, click on OS Upgrade like in the screenshot below:
Update button is pressed you will see the below screenshot:
The screenshot below shows that the Recovery Partition has been upgraded successfully:
Update Recovery Partition from the command-line
Alternatively you can also upgrade the recovery partition from the command-line
pop-upgrade recovery upgrade from-release
You should see an output similar to what is pictured below confirming the recovery partition had been updated:
checking if pop-upgrade requires an update Recovery event: fetching recovery files Fetched 2932/2932 MiB Recovery event: verifying checksums of fetched files Recovery event: syncing recovery files with recovery partition Recovery event: recovery partition upgrade completed Recovery upgrade status: recovery partition refueled and ready to go