Hi all,

Today my system was working fine until I reboot. It do not boot into my desktop anymore. It boot into shell. It look like this:

https://ibb.co/TMmj6d88

I am not really an expert in file system, so I am not really sure what is the first step or is this recoverable. Which mean I will need a lot of help from you guys. Any help would be appreciated thanks.

I followed this fix https://blog.fyralabs.com/btrfs-corruption-issues/

  • bacon_pdp@lemmy.world
    0·
    1 day ago

    First

    lsblk to get the list of block devices (you can use size to figure out your file system)

    Then: mount -o remount,rw /dev/${name found in previous step} /

    Then check for bad entries in your /etc/fstab and fix them

    Then check for failed services: systemctl —failed

    Then you should be able to:

    systemctl set-default graphical.target to boot

            • Kiuyn@lemmy.mlOP
              0·
              1 day ago

              This is the painful part I don’t know why my fstab is nuked. It is completely empty. I am writing it rn and it is painful. I have a question to ask tho. After I finish writing it what do I do? Do I reboot?

              Edit: Okay after I finish the fstab I do mount -a it did not work. ;). I am not sure if what I did is good though. I just copy fstab of a new installation of arch on my laptop and change the UUID

              • bacon_pdp@lemmy.world
                0·
                1 day ago

                You don’t need to use the uuid for /etc/fstab (which should make it much easier)

                You don’t need to reboot just set the run level via: systemctl set-default graphical.target

                  • bacon_pdp@lemmy.world
                    0·
                    1 day ago

                    But you will want to clear out the failed systemd services first to ensure that you can boot.

                    systemctl --failed will list what failed

                    After you make your /etc/fstab

                    systemctl daemon-reload will regenerate the units files in /run/systemd/generator but doesn’t start new automounts or stop ones removed from fstab.

                    systemctl start newmount.automount will start the mount. The .automount extension is required, as systemd assumes .service if not extension is specified.

                    systemctl stop oldmount.automount will remove a mount not longer in fstab

                    systemctl reset-failed will stop a previously failed removed mount from appearing in status messages