On 12/05/2014 at 01:05 PM, Brian wrote: > On Fri 05 Dec 2014 at 09:04:14 -0800, Eduardo Nogueira wrote: > >> With init, skipping a scheduled fsck during boot was easy, you just >> pressed Ctrl+c, it was obvious! Today I was late for an online >> conference. I got home, turned on my computer, and systemd decided >> it was time to run fsck on my 1TB hard drive. Ok, I just skip it, >> right? Well, Ctrl+c does not work, ESC does not work, nothing seems >> to work. I Googled for an answer on my phone but nothing. So, is >> there a mysterious set of commands they came up with to skip an >> fsck or is it yet another flaw? > > "fsck.mode=skip" on the kernel command line. That lets you prevent systemd from running fsck in the first place. Unless I'm greatly misunderstanding what I've read so far, it does not let you cancel a systemd-initiated boot-time fsck which is already in progress. Discussion found via Google seems to indicate that even Ctrl-Alt-Delete or the power button (short of the hard-power-off form, which can corrupt the filesystem being checked) will be ignored by systemd while such a fsck is in progress. https://bugzilla.redhat.com/show_bug.cgi?id=719952 seems like it might be related. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature