[Bug 924488] New: fstab entry prevents booting no emergency shell
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488 Bug ID: 924488 Summary: fstab entry prevents booting no emergency shell Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: osynge@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Dear all, Today I rebooted my file system. And could not boot the OS or access the emergency shell. The cause was an incorrect line in /etc/fstab /usr/local/share/store/iso/SUSE-CLOUD-3-x86_64-GM-DVD1.iso /srv/www/htdocs/SUSE-CLOUD-3-x86_64-GM-DVD1 iso9660 ro,relatime 1 0 The iso disk was missing. so boot failed. Nicely the system asked me to login to emergency shell and correct the failed mount. changing the mount options to "0 0" did not also seem to help. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
Dr. Werner Fink
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
--- Comment #4 from Owen Synge
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
--- Comment #6 from Dr. Werner Fink
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
Thomas Blume
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
Dr. Werner Fink
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
--- Comment #11 from Thomas Blume
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
Thomas Blume
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
--- Comment #13 from Owen Synge
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
http://bugzilla.suse.com/show_bug.cgi?id=924488#c16
--- Comment #16 from Thomas Blume
(In reply to Thomas Blume from comment #12)
Felix, Owen, can you please check wheter the systemd version from:
http://download.opensuse.org/repositories/home:/tsaupe:/branches:/openSUSE:/ 13.1:/Update:/bsc924488/standard/
fixes this issue on your machines?
Tried comment 12 solution on 64 bit host gx62b after trying the comment 3 solution on more than a half dozen hosts, both 32 and 64 bit, with detrimental side effect on (apparently only) 32 bit reported at http://lists.opensuse.org/opensuse-factory/2015-09/msg00617.html . I need to try a 32 bit version to see if the other solution's side effect is also avoided as it is with 64 bit.
For 13.1 the systemd version will be updated to 210, so please forget comment#12 and go for updating to version 210 instead. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
http://bugzilla.suse.com/show_bug.cgi?id=924488#c17
Thomas Blume
On i586 host kt400, upgrading to BaseSystemLegacy's systemd-210 and its deps solves the defective emergency shell problem, but introduces a new one described in http://lists.opensuse.org/opensuse-factory/2015-09/msg00671.html that I've yet to search for in Bugzilla, and for which a fix or workaround exists in /usr/lib/systemd/system/network@.service thus:
--- .network@.service.01 2014-04-10 03:46:57.000000000 -0400 +++ .network@.service.03 2015-09-27 21:40:40.000000000 -0400 @@ -4,7 +4,7 @@ PartOf=network.service BindsTo=sys-subsystem-net-devices-%i.device IgnoreOnIsolate=yes -Before=network-online.target +Before=network.target
[Service] Type=forking
Can you please make sure that you add the option: _netdev to all nfs mounts in /etc/fstab? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
http://bugzilla.suse.com/show_bug.cgi?id=924488#c18
--- Comment #18 from Andrei Borzenkov
Can you please make sure that you add the option:
_netdev
to all nfs mounts in /etc/fstab?
It is different problem - he speaks about manual mounts, for them _netdev is irrelevant. The problem is that with manual NFS mounts network-online.target is not pulled in so on shutdown there is nothing to synchronize stopping of interfaces against. I am afraid it was my mistake to order network@.service against network-online.target instead of network.target. I cannot say what was the reason for this. I think we need to apply suggested patch indeed. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
http://bugzilla.suse.com/show_bug.cgi?id=924488#c19
--- Comment #19 from Thomas Blume
(In reply to Thomas Blume from comment #17)
Can you please make sure that you add the option:
_netdev
to all nfs mounts in /etc/fstab?
It is different problem - he speaks about manual mounts, for them _netdev is irrelevant. The problem is that with manual NFS mounts network-online.target is not pulled in so on shutdown there is nothing to synchronize stopping of interfaces against. I am afraid it was my mistake to order network@.service against network-online.target instead of network.target. I cannot say what was the reason for this. I think we need to apply suggested patch indeed.
Ah ok, indeed I wasn't aware that the mounts are manual. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=924488
http://bugzilla.suse.com/show_bug.cgi?id=924488#c21
--- Comment #21 from Thomas Blume
(In reply to Thomas Blume from comment #17)
Can you please make sure that you add the option:
_netdev
to all nfs mounts in /etc/fstab?
Comment 18 cancels reason for needinfo, correct?
Well, if you have network dependent mounts in fstab you should still add _netdev. But as Andrei wrote, this is not the root cause of this bug. So, no needinfo. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com