Screenshot as text (excuse me if I have mistyped anything)

DMAR: [Firmware Bug]: No firmware reserved region can cover this
Contact BIOS vendor for fixes
x86/cpu: SGX disabled by BIOS.
ima: Error Communicating to TPM chip
ima: Error Communicating to TPM chip
ima: Error Communicating to TPM chip
ima: Error Communicating to TPM chip
ima: Error Communicating to TPM chip
ima: Error Communicating to TPM chip
ima: Error Communicating to TPM chip
ima: Error Communicating to TPM chip
/dev/sda2: clean, 529831/31162368 files, 8432995/1246456392 blocks
Timed out waiting for device dev-disk-by\x2duuid-1ee4Scef\x2deb91\x2...
Dependency failed for drive.mount - /drive.
Dependency failed for local-fs.target - Local File Sustems.
You are in emergency mode mode. After logging in, type “journalctl -xb" to view
system logs, "systemctl reboot" to reboot, “systemctl default" or "exit"
to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):

I installed an m.2 SATA SSD into the device in addition to the old SATA SSD. However, it wouldn’t boot properly. I decided to take it out, and now it won’t boot using the existing SSD either. Does anyone know what could be the issue? So far, I’ve tried the following:

  1. Checking boot media order in BIOS
  2. Resetting BIOS
  3. Ensuring fstab used UUID’s (it already did)
  4. Updating initramfs

I’m using Debian 6.1.38-2 (2023-07-27).

EDIT: Dran’s suggestion to remove the /drive entry from fstab resolved the issue.

  • Dran@lemmy.worldEnglish
    5·
    11 months ago

    The output of journalctl might be helpful for troubleshooting.

    Also a cat of /etc/fstab

    Initial guesses from what I can see: Do you have some sort of drive encryption on and does that encryption rely on your tpm?

    Is that disk being enumerated properly? What does lsblk say? Do you see the partition/filesystem at all?

    • qaz@lemmy.worldOPEnglish
      3·
      11 months ago

      The output of journalctl might be helpful for troubleshooting.

      These errors seemed important. If there is anything specific to look for, let me know.

      Also a cat of /etc/fstab

      Initial guesses from what I can see: Do you have some sort of drive encryption on and does that encryption rely on your tpm?

      I don’t use disk encryption as far as I’m aware

      Is that disk being enumerated properly? What does lsblk say? Do you see the partition/filesystem at all?

      It looks normal to me.

      • Dran@lemmy.worldEnglish
        4·
        11 months ago

        /drive is not a standard mount in a Debian install. Presumably that’s something you did.

        There’s also no unaccounted for partitions on /sda

        If you comment that like out for the /drive mount, it should boot. I’d say better than 50/50 the rest of that is red herrings that have been there since you installed

          • Dran@lemmy.worldEnglish
            3·
            11 months ago

            Glad to hear. If there’s a lesson to be taken from here, it’s to make sure after installing a distro, make note of anything odd in dmesg, journalctl, etc. There’s about eight rabbitholes you could have gone down for weeks and overlooked the obvious here just because we didn’t know what “normal” looked like for your system.