<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Systemd on initramfs won't get to emergency mode if root parameter is garbage" href="https://bugs.freedesktop.org/show_bug.cgi?id=76124#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Systemd on initramfs won't get to emergency mode if root parameter is garbage" href="https://bugs.freedesktop.org/show_bug.cgi?id=76124">bug 76124</a> from <a class="email" href="mailto:charles.costar@gmail.com" title="Mateus Rodrigues Costa <charles.costar@gmail.com>"> Mateus Rodrigues Costa</a> <pre>Hi, I have updated systemd to 211-1 and mkinitcpio to 17-1 and this still happens. mkinitcpio hooks: HOOKS="base systemd btrfs autodetect modconf block keyboard sd-vconsole resume filesystems" Also, here is some more information: This bug will happen to any non-dev device garbage root value and to not having a root value set. During the boot process, if your root value is a /dev device that is not available (in this case, because it doesn't exist) systemd will wait 1min30s for it and, after time outing, you will get immediately to emergency mode. However, if it not, then systemd may or may not take a long time to enter emergency mode, if it ever get to it. IMO, you should be dropped immediately to the emergency mode after systemd notices it can't mount $root because it is invalid. I'm considering it a minor bug, but you may consider it a feature request or enhancement.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>