this post was submitted on 21 Dec 2023
56 points (91.2% liked)

Linux

48145 readers
614 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
nooter692@lemmy.ml
AgreeableLandscape@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
56
Super weird error, what's happening? (lemmy.zip)
submitted 10 months ago by SuperSpruce@lemmy.zip to c/linux@lemmy.ml
36 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] chameleon@kbin.social 10 points 10 months ago (1 children)

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.zip 2 points 10 months ago (1 children)

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 points 10 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