<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - systemd-208-10: Hangs if a partition referenced in fstab has been formatted" href="https://bugs.freedesktop.org/show_bug.cgi?id=74724#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - systemd-208-10: Hangs if a partition referenced in fstab has been formatted" href="https://bugs.freedesktop.org/show_bug.cgi?id=74724">bug 74724</a> from <a class="email" href="mailto:Richard.Holt@gmail.com" title="Richard <Richard.Holt@gmail.com>"> Richard</a> <pre>in Manjaro-0.8.9 with systemd-212-3 here are 2 scenarios: Config1: broke fstab by mangling a UUID by removing some digits 1-Reboot Manjaro ..a-systemd stops and offers several commands for after login, but also offers Ctrl-D to fix the problem; however, it did not respond to Ctrl-D after 5 minutes. ..b-entered root password and logged in. ..c-entered systemctl reboot which rebooted 2-Reboot Manjaro ..a-systemd stops and offers several commands for after login, but also offers Ctrl-D to fix the problem ..b-Applied Ctrl-Alt-Del and the system rebooted. Config2: broke fstab by reformatting the swap file when installing another distro 1-Reboot Manjaro ..a-systemd stops with a message that a start script is running: it starts a countdown of (x of 1.5 minutes). This seems an excessive time to wait for the UUID to fix its self? Perhaps it is waiting for some other action to complete. ..b-after 1.5 minutes it continues booting but there is no indication of what the problem might have been. All in all, systemd works as expected. I have learned to not automount other partitions for automounting in Manjaro with systemd. I was not using automount. That may be the problem that fstab configuration is different from sysv?</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>