Linux Questions

1154 readers

4 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

stay on topic
be nice (no name calling)
do not post long blocks of text such as logs
do not delete your posts
only post questions (no information posts)

Tips for giving and receiving help

be as clear and specific
say thank you if a solution works
verify your solutions before posting them as facts.

Any rule violations will result in disciplinary actions

founded 1 year ago

MODERATORS

possiblylinux127

"sgx: There are zero EPC sections" When trying to install Debian with existing /home in encrypted lvm in vm. (sopuli.xyz)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/linuxquestions

5 comments fedilink hide all child comments

I want to install Debian over an existing Debian install with an existing home partition in an encrypted lvm (to upgrade to testing), and I have been practising in a vm.

After trying to follow the advice on https://www.blakehartshorn.com/installing-debian-on-existing-encrypted-lvm/, I successfully reached the end of the installation, but when I try to boot into my system, I get the error(s) shown in the attached screenshot.

Any idea what I did wrong/need to do?

Edit: "sgx: There are zero EPC sections" is something that displayes when booting successfully into a machine that works too.

you are viewing a single comment's thread
view the rest of the comments

[–] possiblylinux127 1 points 1 year ago (1 children)

Its going to be way easier to upgrade via apt. Can you share what errors you were seeing?

[–] [email protected] 1 points 1 year ago

I tried a dist-upgrade in a virtual machine with xfce then left it for a bit. When I got back, black screen with a terminal cursor in the top right. I left it for a bit more, then tried to get a tty terminal using the keyboard shortcuts that Boxes provides, but it would only show the login for a split second before returning to the blank screen with just a cursor.

I decided to try to soft restart with the button in boxes. It seemed to shutdown successfully, but when it tried to boot back up it gave a kernel panic instead.