Bug 985534
Summary: | Physically missing harddrive with fstab entry will cause systemd to boot in emergency mode | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | nospam |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | johannbg, lnykryn, mschmidt, msekleta, notting, plautrba, systemd-maint, vpavlin, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-19 06:36:48 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
nospam
2013-07-17 17:11:06 UTC
What was the mount path that failed or better yet can you boot with "systemd.log_level=debug" without that hd on the kernel command line and then attach the output of the command "journalctl -b" along with that /etc/fstab so we can properly map what's happening This is expected behaviour. systemd does not know with mounts are essential to the system's integrity and which aren't, so it goes into fail-safe (ie. the emergency mode). You can however mark non-essential mounts with the "nofail" option to avoid it. For a longer explanation see https://bugzilla.redhat.com/show_bug.cgi?id=888835#c6 |