Since you cannot mount the EFI partition from within the current session, you must use a **Live USB** to "chroot" into your installation and fix it from the outside.
**Step 1: Prepare the Environment**
1. Boot from a **Pop!_OS Live USB**.
2. Open a terminal in the Live environment.
3. Unlock your encrypted drive:
```
sudo cryptsetup luksOpen /dev/nvme0n1p3 cryptdata
```
1. Mount your root partition (adjust if your LVM names differ):
```
sudo mount /dev/mapper/data-root /mnt
```
**Step 2: Mount System Directories & EFI**
You need to bind your system directories so the "repair" environment has access to your hardware:
```
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
```
Now, mount your **actual** EFI partition. Since `lsblk` showed two identical UUIDs, we'll try the one that likely holds the boot files:
```
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
```
_If this fails with the same charset error, the Live USB kernel should at least have the modules to let you run `fsck.vfat -a /dev/nvme0n1p1` first._
**Step 3: Chroot and Repair**
Enter your installed system to run repairs as if you were logged in normally:
```
sudo chroot /mnt
```
Inside the chroot, run these commands in order:
1. **Clear broken configurations**:
```
dpkg --configure -a
```
1. **Force-reinstall the kernel and modules**:
```
apt install --reinstall linux-image-generic linux-headers-generic linux-modules-extra-$(uname -r)
```
1. **Update the initramfs** (this builds the "missing" drivers back into the boot process):
```
update-initramfs -c -k all
```
1. **Update the bootloader**:
```
kernelstub
```
**Step 4: Cleanup & Reboot**
Exit the chroot and unmount everything safely:
```
exit
sudo umount -R /mnt
reboot
```
**Why you have two EFI partitions**
The duplicate UUIDs on `p1` and `p2` suggest a "cloned" partition or a failed recovery attempt. If the repair above works, check `/etc/fstab` once you're back in. To avoid the charset issue forever, ensure your EFI line in `fstab` includes `iocharset=utf8`.
Do you have a **Pop!_OS Live USB** ready to start the chroot process?
```
sudo dpkg —configure -a
Sudo apt upgrade
Sudo kernelstub -v
```