I’m not sure if this is the best community to post in, but I just bought a used computer and slotted in an RX480 as the GPU. I installed KDE Neon 5.27 on it, and it worked flawlessly for 2 days.

Then, even though it was working earlier today, it slept and then would not wake up. So I turned off the power and turned it back on again, and was greeted with this error screen:

The only prior error message I’d gotten from the system was when I tried to install wine for one application, it told me some packages weren’t up to date, without a way to fix it. I can enter the BIOS just fine.

What is going on? How do I fix this?

  • djtech@lemmy.world
    3·
    11 months ago

    The Shell where you typed “systemctl reboot” and “exit”.

    If you are running KDE neon, try “apt update” and “apt upgrade”. If It doesn’t work do “sudo apt update” and “sudo apt upgrade”

    • SuperSpruce@lemmy.zipOP
      4·
      11 months ago

      I ran apt update and some index files failed to download. It was just a warning though.

      But systemctl reboot and exit still fail the same way.

      • djtech@lemmy.world
        3·
        11 months ago

        Before the “systemctl” command: try removing the GPU and booting it up without the GPU If it works, you can skip the “systemctl” commands

      • djtech@lemmy.world
        3·
        11 months ago

        Run “journalctl --lines 200” and send photos of output.

        NOTE: This is all of the logging of the computer, and it’s long (that command select the last 200 entries), so you might have to scroll down using the PageDown key (or arrow down) in order make the photos of everything

        • SuperSpruce@lemmy.zipOP
          3·
          11 months ago

          Note: The computer has an SSD where the OS lives and two HDDs, sda and sdb, set up in RAID 1 because the computer is 3.5 years old.

          • chameleon@kbin.social
            4·
            11 months ago

            The RAID1 seems to be failing according to that screenshot. That breaks the “Local File Systems” task and since quite a lot of things tend to depend on that, many things usually end up failing in an annoying cascade failure. It’s also failing with a timeout instead of a strict error, which is odd.

            Either way, I’d try commenting that line for /mnt/raid in /etc/fstab for now and seeing if that makes the system boot. It’s possible that journalctl -u dev-md0.service or systemctl status dev-md0.service might tell you more, but it’s 50/50 if it’ll be anything useful.

            • SuperSpruce@lemmy.zipOP
              1·
              11 months ago

              How do I edit /etc/fstab if I’m not even able to boot the system? Or am I already booted in the system, just in a CLI environment?

              • chameleon@kbin.social
                10·
                11 months ago

                You’re most likely booted, otherwise you might need a live USB. Hopefully, the system isn’t in read-only mode. What I’d recommend doing is:

                cp /etc/fstab /etc/fstab.backup

                To make a copy once. Then, nano /etc/fstab to run nano, a basic CLI editor. You can use the arrow keys to navigate and type freely in it. The hints like ^O shown on the bottom mean ctrl+o.

                You’d use the arrow keys to go down to the line that probably says /dev/md0 /mnt/raid morecrap, put a # in front of it, press ctrl+w then enter to save. If that worked, ctrl+x to exit and try a reboot again.

                Obviously can’t promise this is “the” error preventing the system from booting, but it’s generally a good idea to disable broken stuff like this to get the system working again, then fix it from there. Hopefully, this does the trick. Your RAID setup will not be activated on reboot after you do this but it’s not going to permanently delete data or anything.

                • SuperSpruce@lemmy.zipOP
                  2·
                  11 months ago

                  I used nano to edit /etc/fstab and commented out the last line and the system booted into GUI mode!

                  This leaves me with some questions:

                  1. Why does fstab fail to mount the NTFS raid array?
                  2. Why does the raid array failing to mount block the EDID signal? It’s not like the OS lives on the raid array.
                  3. How do I properly mount the raid array and how do I automate it every boot if I can’t use fstab?
                  • mvirts@lemmy.world
                    1·
                    11 months ago

                    Looks like you need to look for messages about /dev/md0 and why it may be timing out. Also maybe add nofail to the raid entry in fstab so you can still boot if the root fs is not on it and it fails ( is root on NTFS possible or good?)

                    I don’t think the edid message is a problem, just an artifact of your monitor not talking to your video card?

                    Maybe NTFS is the problem, I think it needs special options to automatically remove the dirty bit and replay the journal