(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·
    8 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·
      8 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·
        8 months ago

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

        • HouseWolf@lemm.eeOPEnglish
          1·
          8 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.

  • thingsiplay@beehaw.org
    4·
    8 months ago

    Check your /etc/fstab and uncomment all drives you have unplugged. But not sure if that helps in your case, beceause it cannot find /boot? I’m no expert, so not sure whats going on. Check if EFI or like that is installed on an unplugged drive.

    • HouseWolf@lemm.eeOPEnglish
      2·
      8 months ago

      I did that, I’ve had issues with fstab before giving me a similar error, but normal I can fix it from the tty still.

      But this time not even my keyboard works so I had to go into a live Mint USB I had laying around to change it. #'ed out any drive that wasn’t my main NVME

  • Sina@beehaw.org
    3·
    8 months ago

    6.7 kernel on btrfs is a removedshow, could be that here too. (btrfs subvolume corruption)

    • HouseWolf@lemm.eeOPEnglish
      1·
      8 months ago

      I’ve gone back to using EXT4 for now

      I only used BTFS for the first time on that install to try it out.

      • Sina@beehaw.org
        1·
        8 months ago

        You were super unlucky then, had you installed Endeavor with the same settings, it could have crashed the exact same way.

        The difference between Archinstall installed Arch & EndeavorOS is very minimal and overrated. In this case I think the fix would have been picking the LTS kernel until 6.8 is released.

        • HouseWolf@lemm.eeOPEnglish
          1·
          8 months ago

          Luckily I keep all my important files and backups on a separate drive so reinstalling an OS is only a “mild” annoyance for me.

          I was only on Arch for abit over a week just to “prove I could” but honestly didn’t see a huge upgrade over Endeavour for my personal use.

          • Sina@beehaw.org
            1·
            8 months ago

            I was only on Arch for abit over a week just to “prove I could” but honestly didn’t see a huge upgrade over Endeavour for my personal use.

            Arch, Endeavour is one and the same. So of course you wouldn’t see anything.

  • fl42v@lemmy.ml
    2·
    8 months ago

    So, what’s in the fstab, anyways? Full contents uploaded on pastebin or smth similar would be helpful. Same goes for the bootloader used and the method of installation (the proper way or archinstall)

    Anyway, you can boot into the arch iso, make mounts and re-genfstab -U it.

    • HouseWolf@lemm.eeOPEnglish
      2·
      8 months ago

      I kinda forgot about pastebin but here’s it is https://pastebin.com/VjighWKV

      I haven’t touched fstab since setting up my system and only edited it to mount my extra internal drives, my main drive was automatically configured through Archinstall

      • d3Xt3r@lemmy.nzM
        3·
        8 months ago

        @fl42v is on the right track. This is a common issue that occurs when restoring snapshots, the subvolid in your fstab might not match the subvolid that’s actually present on the disk.

        Run btrfs subvolume list / and check that the subvolids match. Also run blkid and verify that the UUIDs listed there matches your fstab.

    • fl42v@lemmy.ml
      1·
      8 months ago

      Huh, also, what kind of snapshot, {Btr,z}fs or smth like timeshift?