Full Disk Encrypted Stuck on cryptsetup: cryptdata set up successfully

[kendoori]

Distribution (run cat /etc/os-release):

NAME="Pop!_OS" VERSION="20.04 LTS" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 20.04 LTS" VERSION_ID="20.04" HOME_URL="https://system76.com/pop" SUPPORT_URL="http://support.system76.com" BUG_REPORT_URL="https://github.com/pop-os/pop/issues" PRIVACY_POLICY_URL="https://system76.com/privacy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal LOGO=distributor-logo-pop-os

Issue/Bug Description: Upon cold boot of system with full disk encryption, after entering the encryption password, the system hangs on cryptsetup: cryptdata set up successfully screen. Arrow up key will move past and reveal a start job that runs for 1 mm 30 seconds.

Steps to reproduce (if you know): Reboot

Expected behavior: System should just boot normally after entering password

Other Notes: Clean install on Thinkpad T480 with no special partitioning.

[ghost]

same problem on ThinkPad t495s using AMD

[AleVul]

Have the same problem, managed to get into recovery partition by following this article. But it is not clear what to do from there since the "repair commands" link lead to a 404 page.

Also when trying to update via chroot'ing into mount, the system throws error about /etc/os-release with message "Structure needs cleaning"

[AleVul]

Attempted to check partition via gparted, operation stops with "Nothing to read on input" message. Command used "cryptsetup -v resize 'sda3_crypt'"

[leviport]

@AleVul Sorry about that broken link, and thanks for the heads-up. It will be fixed soon. The correct link should go here: https://support.system76.com/articles/package-manager-pop/

[AleVul]

@leviport thank you, attempted to to use commands in article, stopped at "sudo dpkg --configure -a" since it throws same error about "Structure needs cleaning". I assume my partition is corrupted, any ideas on how i can check/fix it?

[AleVul]

managed to fix the partition by following this answer

[jnaulty]

Ran into this issue as well on a Lemur Pro

Followed the instructions in the following docs/resources:

• boot into recovery mode and unlock disk - https://support.system76.com/articles/pop-recovery/
• fix package manager issues and upgrade distribution - https://support.system76.com/articles/package-manager-pop/
• perform filesystem check - https://askubuntu.com/questions/279493/how-to-check-an-encrypted-disk-for-errors/279494#279494

System worked after rebooting from the recovery mode.

[vcg3rd]

Ran into the same problem today. I followed all the instructions provided by jnaulty, above.

It booted again, but boots to a shell and I have to startx. That works, but a lot of the appearance is off (desktop icons I can't get rid of with dcon-editor), icons sets I can't change with Gnome-Tweaks, PopOS keyboard shortcuts not working. Probably because now my DM is GNOME 3.38.2 and WM: Mutter. I can't logout to login to anything else because it drops me back to a shell.

Likely, I purged something I shouldn't have, but I looked carefully and also followed the advice:

Please pay attention when using a purge command. If the command looks like it will remove several additional packages besides the one you are trying to fix, don’t run it! If it’s only a few packages, it’s most likely safe. If additional packages are removed, make sure to install them again before restarting the computer. This command will make sure the core Pop!_OS components are installed after any purge commands:

sudo apt install pop-desktop

I had no idea which package was causing the problem, so I couldn't hone in on just fixing it. Of course, I have no record from the chroot purge because I'm not adept enough.

For now I'll settle for autostarting X with default PoPOS DE/WM, and go from there.

Update: So, the problem is gdm3 isn't starting. If I logout and sudo service gdm3 start I get the normal login screen, after which all those other problems are resolved. I'll research how to make gmd3 autostart, but leave this here in case someone encounters this in the future.

Update 2: Logout sudo service gdm3 stop because I had it running, then sudo update-rc.d gmd3 enable reboot

Probably obvious, but I didn't know.

After reboot, back to normal.

[poulad]

Removing apt's lock file resolved the issue for me on Pop!_OS 21.04.

1. Press CTRL + ALT + F2 or others to open a different terminal
2. Login to get a shell
3. See the lock file issue by running sudo apt update
4. remove it and reboot

   sudo rm -f /var/lib/apt/lists/lock
   reboot

[devkinetic]

I have the same issue on a new Dell Inspiron. Ran through @jnaulty @vcg3rd and @poulad steps progressively to no avail. I'm locked out of my system.

Rebooted to recovery with spacebar, setup WIFI.

# decrypt
lsblk
sudo cryptsetup luksOpen /dev/nvme0n1p3 sudo lvscan
sudo vgchange -ay
sudo mount /dev/data/root /mnt
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
# chroot
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
sudo cp -n /etc/resolv.conf /mnt/etc/
sudo chroot /mnt
# update
sudo apt clean
sudo apt update -m
sudo dpkg --configure -a
sudo apt install -f
sudo apt full-upgrade
sudo apt autoremove --purge
sudo apt install pop-desktop
exit
# fsck
sudo fsck /dev/data/root
reboot

This didn't have any effect so as stated I ran through the steps again to clear the lock file just in case...

# decrypt
# chroot
sudo rm -f /var/lib/apt/lists/lock
exit
reboot

Anything I did wrong here, or further suggestions? I tried the "up arrow to move past and reveal..." but the key doesn't do anything. Also tried mashing ctrl+alt+F2 and just nothing.

I will add that #510 mentions nvidia being an issue I have the rtx 3050 in this laptop. Installation from my flash drive went fine and detected it. I did my install with secureboot disabled. This started happening right after my first restart.

[Ajilagi]

Removing apt's lock file resolved the issue for me on Pop!_OS 21.04.

1. Press CTRL + ALT + F2 or others to open a different terminal

2. Login to get a shell

3. See the lock file issue by running `sudo apt update`

4. remove it and reboot
   ```shell
   sudo rm -f /var/lib/apt/lists/lock
   reboot
   ```

Removing apt's lock file also resolved my issue, but I need to go into Recovery Partition to do that