<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - No way to repair root FS in emergency mode"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85200">85200</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>No way to repair root FS in emergency mode
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>nalimilan@club.fr
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>My F20 system crashed twice last week (once because of a kernel bug, and the
second time because of a broken battery), and each time it wouldn't boot after
that because of errors on the ext4 root. I was granted with an emergency boot
screen like this:
<a href="http://foobaring.blogspot.fr/2014/01/howto-run-fsck-on-emergency-mode-on.html">http://foobaring.blogspot.fr/2014/01/howto-run-fsck-on-emergency-mode-on.html</a>
The problem is, there's no (easy) way to run fsck on the unmounted root
partition to actually fix the errors. I had to create a Live USB and run fsck
manually from there. That's quite painful, and a non-technical user would be
completely stuck, thinking Linux is quite a fragile OS.
Apart from the blog post above, I've found other complaints or help requests
about this (and sometimes of course it triggers the usual rants about systemd,
which is a bit sad):
<a href="http://forums.fedoraforum.org/archive/index.php/t-299624.html">http://forums.fedoraforum.org/archive/index.php/t-299624.html</a> (Fedora)
<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754340">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754340</a> (Debian, there's an
interesting discussion there about potential explanations/solutions)
<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697962">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697962</a> (Debian)
<a href="https://bbs.archlinux.org/viewtopic.php?id=186201">https://bbs.archlinux.org/viewtopic.php?id=186201</a> (Arch)
<a href="http://bitsofmymind.com/2014/03/14/how-to-fix-fsck-your-root-file-system-that-you-have-to-boot-into-on-linux/">http://bitsofmymind.com/2014/03/14/how-to-fix-fsck-your-root-file-system-that-you-have-to-boot-into-on-linux/</a>
(Fedora)
<a href="http://forums.fedora-fr.org/viewtopic.php?id=62374">http://forums.fedora-fr.org/viewtopic.php?id=62374</a> (Fedora, in French)
One common remark is that unmounting / does not work (at least not without a
trick). But beyond that, I think it would be very useful to offer a simple
option to repair the FS automatically, for users who would run 'fsck -y' anyway
(most users, probably).
(There's also the problem that when Plymouth is enabled, you don't see the fsck
error message, only the "Welcome to emergency mode", without any explanation of
why normal boot failed. And journalctl -xb does not contain any information
about that either.)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>