From: Jason Stewart <support@eggplantsd.com>
To: initramfs@vger.kernel.org
Subject: fsck to RAM?
Date: Sat, 11 Jul 2026 13:05:10 -0400 [thread overview]
Message-ID: <alJ3xij28IW6tfkS@newcore.egp2.pro> (raw)
Does anyone know what the obstacles are to putting fsck for common
filesystems into RAM before the rest of fstab is mounted?
I'm dealing with a number of older persons dipping their toes into
Linux, and whenever there is a power event, they all get the dreaded
root prompt requesting an fsck on their mounted root partition.
Everything on the internet points to booting from a live cd/usb, and
fsck-ing it from there, but that is kinda terrible. If it were in the
initramfs, then they could unmount root & do the fsck without having to
reach for a livecd.
js
reply other threads:[~2026-07-11 17:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alJ3xij28IW6tfkS@newcore.egp2.pro \
--to=support@eggplantsd.com \
--cc=initramfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox