this post was submitted on 23 Sep 2024
579 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
[email protected]
[email protected]
579
Average systemd debate (lemmy.world)
submitted 14 hours ago* (last edited 14 hours ago) by [email protected] to c/[email protected]
90 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 1 points 2 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 57 minutes 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.