[systemd-bugs] [Bug 85200] No way to repair root FS in emergency mode

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Feb 4 09:58:13 PST 2015


https://bugs.freedesktop.org/show_bug.cgi?id=85200

Milan Bouchet-Valat <nalimilan at club.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW

--- Comment #10 from Milan Bouchet-Valat <nalimilan at club.fr> ---
My general issue is simply that when / gets corrupt for some reason, people get
a console screen without any clear way of fixing the problem unless they are
experts of the boot process. This sounds too bad since simply running fsck
before mounting / would fix the problem.

Now, going into the technical details, I'd say that the #1 problem is that when
/ is corrupt, systemd goes to rescue.target instead of emergency.target. In the
former mode, / is already mounted, which means you cannot run fsck on it. Not
everybody knows that you're supposed to reboot into emergency.target (even more
so since the prompt says "Welcome to emergency mode" and not "rescue mode").

So I think it would be more useful to boot/reboot into emergency.target when /
fails to mount. Even better, the prompt could say "Failed to mount root
partition. Do you want to automatically try to repair it? [Y/n]" I suspect 90%
of people merely call 'fsck -y' without in those cases anyway.

IMHO this is really required if we want Linux to be as reliable as other OSes
for average-technical users, for which systemd is only a vague name and boot
targets something they never heard of.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150204/f3307f3c/attachment.html>


More information about the systemd-bugs mailing list