search

pop-os / pop

A project for managing all Pop!_OS sources
https://system76.com/pop
2.44k stars 87 forks source link

Pop!_OS install hang w/ encrypted disk #510

Open jdpatdiscord opened 5 years ago

jdpatdiscord commented 5 years ago

NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.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=disco UBUNTU_CODENAME=disco

Regarding disk encryption utility pre-installed with Pop!_OS

Issue/bug: Cannot unlock disk during startup, hangs after "cryptsetup: set up successfully"

Reproduce: Boot to Pop!_OS 19.04 image via USB flash drive Go through setup and enable disk encryption Agree to restart when prompted by Pop!_OS Enter disk key Hang occurs here

Details of host: Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz; 1 physical processor; 4 cores; 4 threads 16342688KiB RAM ASRock H310M-HDV MOBO NVIDIA GTX 1050 Ti GPU ATA TEAML5LiteD240G SSD ATA WDC WD10EZEX-08W HDD

I'm not entirely sure if this is an isolated issue or somehow user error, but I've reproduced it 3 times and it hangs indefinitely.

hardinfo_report.txt

PrismaPhonic commented 5 years ago

I just tried today with the same image and got the exact same error

gatechcomm commented 4 years ago

Having the same problem. This segment of the recovery process serves as a workaround:

sudo cryptsetup luksOpen /dev/sda3 cryptdata
sudo lvscan
sudo vgchange -ay
sudo mount /dev/mapper/data-root /mnt

Boots fine after that, but the next time I reboot it, I have to do this again.

crackwilding commented 4 years ago

The above comment was me; I was logged into my work account. A bit of additional information, if I hit esc at crypt login, everything looks good until gdm tries to start. It hangs.

crackwilding commented 4 years ago

Just realized this doesn't exactly match my problem. Nevermind.

arshbot commented 4 years ago

Seeing this now too, stock orynx pro. Will try to enter the given commands above, but not sure where.

Looks like it started gdm fine, but hange on a warning BIOS contains WGDS but no WRDS

sbeugen commented 4 years ago

I have the same problem with Pop!_OS 19.10. When I switch to my nvidia graphics card and do a reboot, I get stuck at the same screen ("...cryptsetup successfully...")

To be able to boot again, I have to boot into recovery mode, mount the encrypted drive and purge all nvidia packages.

Does any one understand, whats the actual problem here?

arshbot commented 4 years ago

This has happened to me a few times since - I've attempted to debug this multiple times, however the only tried and true solution is to boot to livedisk and perform a refresh. To this end I have a few livedisks on my keychain and setup scripts so I can refresh on the go if needed

rotemgb commented 4 years ago

I have the same problem on Pop_Os 19.10. I switched to Hybrid mode for the first time the night before and since then I am not able to log in to my computer. It's been a week...

Is there any solution to this problem?

Thank you

arshbot commented 4 years ago

You'll have to refresh the install. Unsure what a proper solutions is.

Contacting customer support hasn't yielded any real results

rotemgb commented 4 years ago

Thanks for the quick response.

Will I lose my files and have to reinstall all the apps with refresh install?

Edit: I see here that I won't lose files, only apps. Is it something that you have to do every time you use Nvidia GPU?

arshbot commented 4 years ago

You'll have to reinstall all your apps, but your file system under your user will be intact

On Fri, Apr 17, 2020, 10:48 PM Rotem Gabay notifications@github.com wrote:

Thanks for the quick response.

Will I lose my files and have to reinstall all the apps with refresh install?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pop-os/pop/issues/510#issuecomment-615543618, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD74JTCIIGPHEI6OKSUJPLDRNEIG7ANCNFSM4HHKWDFQ .

rotemgb commented 4 years ago

How about this?

Is it something that you have to do every time you use Nvidia GPU?

masonbee commented 3 years ago

If anyone is still having this problem I just had it on 20.04 and you can solve it in two stages. Open disks, go to your luks encrypted partition and click on the cog icon, choose edit encryption options and then set the luks lvm to be decrypted at boot. Enter the passphrase etc... OK, and then reboot to make sure it worked. After that go to the now open encrypted partition inside the lvm and then click on the cog and edit the mount points. I mounted mine in my home directory and gave it user,defaults as the options. (Pretty sure just defaults would work in most cases.) Then sudo mount -a to make sure it works and try booting again.

(If you bork it you can start up a live session of pop os or something and open up your /etc/fstab and manually take it out or correct it. I'll try and get around to putting a slightly better process of this up on https://masonbee.nz tonight if I can)

MartinFeineis commented 3 years ago

I had the same issue. When I pressed ALT + F2 it started a shell and loaded my .zshrc config, which got me to believe that the system booted and loaded normally and the issue might be with the Window or Login Manager. However I ran 

sudo apt clean
sudo dpkg --configure -a
sudo apt update -m
sudo apt upgrade

I think update and upgrade fixed the issue.

julianlam commented 3 years ago

For what it's worth, this problem began exhibiting for me when I put in an Nvidia card and installed the popOS Nvidia package.

My card is old old old, so the package did not contain drivers for it. I needed to go to https://www.nvidia.com/en-us/drivers/unix/, download the legacy drivers, and install them.

PopOS booted fine afterwards.