this post was submitted on 23 Sep 2024
584 points (96.8% liked)

linuxmemes

20703 readers
1233 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
584
submitted 15 hours ago* (last edited 14 hours ago) by [email protected] to c/[email protected]
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 4 hours ago (1 children)

I'm gonna laugh if it's something as simple as a botched fstab config.

In the past, it's usually been the case that the more ignorant I am about the computer system, the stronger my opinions are.

When I first started trying out Linux, I was pissed at it and would regularly rant to anyone who would listen. All because my laptop wouldn't properly sleep: it would turn off, then in a few minutes come back on; turns out the WiFi card had a power setting that was causing it to wake the computer up from sleep.

After a year of avoiding the laptop, a friend who was visiting from out of town and uses Arch btw took one look at it, diagnosed and fixed it in minutes. I felt like a jackass for blaming the linux world for intel's non-free WiFi driver being shit. (in my defense, I had never needed to toggle this setting when the laptop was originally running Windows).

The worst part is that I'm a sysadmin, diagnosing and fixing computer problems should be my specialty. Instead I failed to put in the minimum amount of effort and just wrote the entire thing off as a lost cause. Easier then questioning my own infallibility, I suppose.

[–] [email protected] 1 points 3 hours ago (1 children)

A typo in fstab shouldn't wreck the system. Why is that not resilient ? I added an extra mount point to an empty partition but forgot to actually create it in LVM.

During boot, device not found and boot halted, on a computer with no monitor/keyboard

[–] [email protected] 1 points 1 hour ago

It will cause a critical error during boot if the device isn't given the nofail mount option, which is not included in the defaults option, and then fails to mount. For more details, look in the fstab(5) man page, and for even more detail, the mount(8) man page.

Found that out for myself when not having my external harddrive enclosure turned on with a formatted drive in it caused the pc to boot into recovery mode (it was not the primary drive). I had just copy-pasted the options from my root partition, thinking I could take the shortcut instead of reading documentation.

There's probably other ways that a borked fstab can cause a fail to boot, but that's just the one I know of from experience.