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.

  • Possibly linux@lemmy.zipM
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Check your fstab as its probably trying to mount something that doesn’t exist.

    Why are you reinstalling to upgrade to testing? Can’t you just update sources.list?

    • s12@sopuli.xyzOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      I just tried doing the install without the encrypted partition and only a root user to check that would still boot after using expert mode to do the install. I’ll do the install as I did before and try to compare fstab to the available partitions.

      I’m sure I already tried updating the sources.list, but I’d already installed a desktop and there were errors when I tried to apt update and apt upgrade/dist-upgrade.

        • s12@sopuli.xyzOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          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.