[RESPONDED] Framework 13 (11th gen Intel) Pop!_OS Recovery partition is missing Refresh option

Framework Laptop 13 Linux
1

After installing Pop!_OS 22.04 LTS (jammy), I had to manually create the Recovery partition. It boots fine but it doesn’t have a refresh option and I’m wondering what I did wrong.

Here is the info from Pop:

Screenshot from 2024-01-26 22-13-36
Screenshot from 2024-01-26 22-13-361455×1022 135 KB

In regular Pop, I can see the Refresh option available:
Screenshot from 2024-01-26 22-17-08
Screenshot from 2024-01-26 22-17-081455×1022 150 KB

But booting in Recovery, it isn’t available:

Screenshot from 2024-01-27 04-18-22
Screenshot from 2024-01-27 04-18-221794×1298 193 KB

blkid partition info:

/dev/nvme0n1p3: 
	LABEL="pop_os" 
	UUID="1fbc84e5-e6af-4a7d-b6ba-a3bb236644ce" 
	BLOCK_SIZE="4096" 
	TYPE="ext4" 
	PARTLABEL="pop_os" 
	PARTUUID="6faccb30-243f-499b-983c-c375e7e5f2e9"
/dev/nvme0n1p4: 
	UUID="6487-0A30" 
	BLOCK_SIZE="512" 
	TYPE="vfat" 
	PARTUUID="526f3efd-19d4-44cf-b846-54faedcfdbec"
/dev/nvme0n1p6: 
	LABEL_FATBOOT="RECOVERY" 
	LABEL="RECOVERY" 
	UUID="7B5A-4D83" 
	BLOCK_SIZE="512" 
	TYPE="vfat" 
	PARTLABEL="RECOVERY" 
	PARTUUID="c3c166e0-cfec-4ed3-b541-d4af27a50da2"

mount info:

/dev/nvme0n1p3 on / type ext4 (rw,noatime,errors=remount-ro)
/dev/nvme0n1p4 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/nvme0n1p6 on /recovery type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,x-gvfs-name=recovery)

/etc/fstab:

UUID=1fbc84e5-e6af-4a7d-b6ba-a3bb236644ce / ext4 noatime,errors=remount-ro 0 1
PARTUUID=526f3efd-19d4-44cf-b846-54faedcfdbec  /boot/efi  vfat  umask=0077  0  0
/dev/disk/by-partuuid/c3c166e0-cfec-4ed3-b541-d4af27a50da2 /recovery vfat umask=0077,x-gvfs-name=recovery 0 0

/boot/efi/loader/entries/Recovery.conf:

title Pop!_OS recovery
linux /EFI/Recovery-7B5A-4D83/vmlinuz.efi
initrd /EFI/Recovery-7B5A-4D83/initrd.gz
options boot=casper hostname=recovery userfullname=Recovery username=recovery live-media-path=/casper-7B5A-4D83 live-media=/dev/disk/by-partuuid/c3c166e0-cfec-4ed3-b541-d4af27a50da2 noprompt

/recovery/recovery.conf:

HOSTNAME=pop-os
LANG=en_US.UTF-8
KBD_LAYOUT=us
KBD_MODEL=
KBD_VARIANT=
EFI_UUID=PARTUUID=526f3efd-19d4-44cf-b846-54faedcfdbec
RECOVERY_UUID=PARTUUID=c3c166e0-cfec-4ed3-b541-d4af27a50da2
ROOT_UUID=PARTUUID=6faccb30-243f-499b-983c-c375e7e5f2e9
LUKS_UUID=
OEM_MODE=0
UPGRADE=1
2

I tried these two changes to my /recovery/recovery.conf:

  1. Using the UUID instead of PARTUUID: ROOT_UUID=1fbc84e5-e6af-4a7d-b6ba-a3bb236644ce
  2. Adding this line: REFRESH=1

No luck so far. These are the very helpful guides that I have been using as a reference:

  1. Add Recovery To Your Pop!_OS, Alejandro Baez, May 3, 2020
  2. Creating a Recovery Partition in Pop!_OS, Diego Zaccariotto, Feb 2, 2023
3

I feel like the better question is why it didn’t make the recovery partition. Did you pick to do a custom installation?

4

I’m not sure, I’ve been running Pop for awhile without issue. I recently tried to install Windows on a separate partition so that I could update the BIOS and not only did Windows not install correctly but managed to corrupt the boot process of the Pop partition.

I had Ubuntu on another partition and I didn’t want to lose that because it still worked. My old recovery partition didn’t have the Refresh option either. I went through the steps in the posts above to create the Recovery partition for the new install. From the Pop side of things it looks fine, but booting into it there is only the Clean Install option.

5

Aaron asked the same question that occurred to me. If it was me, as that is not normal Pop behavior, I’d try again with a new ISO, reformatted USB and install again from scratch.

6

Yeah, I don’t think it’s worth the effort of doing a clean install from scratch just to get the Refresh option working in the Recovery partition. I was mostly curious if it was a common issue (it doesn’t sound like it), or if there was someone familiar with the process that knew of some documentation of the recovery process or something that I could go through. I can still manually copy out /home if I need to. I’ll be sure to use a fresh USB and ISO next time though.

1 Like