(Bonus update) I’m back on KDE6 and it’s actually working! I ran Cinnamon for about a day before missing KDE and tried a fresh install of EndeavourOS. It worked fine, Wayland still doesn’t work but I’m only getting minor bugs with x11 compared to when I tried to update from 5.27

(Update) Well finally back on my desktop but sadly not on my original install, Thanks for all the help and advice! Sadly every path just sent me into another brick wall, I’m starting to think my drive itself is physically failing as I couldn’t mount it in chroot and even had trouble reformatting it…I’ll keep an eye on it and not save anything important to it.

I’ve decided I’m just not cut out for vanilla Arch just yet and gone back to Endeavour but this time with Cinnamon (for now) Thanks again!

After upgrading to KDE 6 and experiencing too many bugs for it to be useable for me I went back to a snapshot I made right before upgrading.

Now I’ve spent half my Friday tracking down different systemctl errors and trying to fix corrupted conf files from live USB environments, physically unplugged all but my nvme boot drive.

Rn I’m in a situation where I’m getting

[FAILED] Failed to mount /boot. See ‘systemctl status boot.mount’ for details [DEPEND] Dependency failed for Local File System.

Then it’s asking to give root password or press control-D, which I’ve dealt with before but this time my keyboard just doesn’t work

I tried to just sort it myself reading the Arch Wiki before begging for help on forums but I’m kinda at my wits end, This is a pretty new Arch installed and the first time using btfs on my main drive, I last updated maybe 4 days ago before today. I’ve also successfully restored from timeshift snapshots on this install before without issues.

Any help where to go from here would be great, thanks in advance.

  • CeeBee@lemmy.world
    5·
    9 months ago

    FAILED] Failed to mount /boot.

    Something you did made your boot partition disappear.

    Then it’s asking to give root password or press control-D, which I’ve dealt with before but this time my keyboard just doesn’t work

    It dropped you into an emergency console. Which makes sense because something has gotten terribly messed up.

    It would be helpful if you have some extra details like system specs. Partition layout (is boot, root, and home all on the same drive?). Which FS are you using, etc.

    It’s likely you’re only going to get back to a working system with a live environment. You’ll have to manually mount the important partitions (root and /boot), chroot to those mounts, and then repair the bootloader.

    • HouseWolf@lemm.eeOPEnglish
      1·
      9 months ago

      I’ve loaded into a live Mint USB I had laying around, Didn’t notice anything too weird within fstab but I removed anything from it that wasn’t my main NVME

      My main drive contains everything system related, root, boot, home etc, they’re all still there in fstab

      My other drives are just game drives and a backup HDD for storage.

      • CeeBee@lemmy.world
        2·
        9 months ago

        Have you mounted each partition and checked the contents? That’s the first thing you should do.

        • HouseWolf@lemm.eeOPEnglish
          1·
          9 months ago

          I’ve sadly formatted over the drive at this point, I did manage to mount the home and root partitions to a live usb but didn’t have any luck getting the boot to mount to anything.