[Bug 924488] New: fstab entry prevents booting no emergency shell
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.
http://bugzilla.suse.com/show_bug.cgi?id=924488 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |osynge@suse.com Flags| |needinfo?(osynge@suse.com) --- Comment #3 from Dr. Werner Fink <werner@suse.com> --- (In reply to Owen Synge from comment #2) Use systemd-210 from project Base:System:Legacy as it is known that emergency shell is fixed there. Please note that there will be no backport as in past this had break on 13.1. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=924488 --- Comment #4 from Owen Synge <osynge@suse.com> --- Dear Werner, As long as you are aware of this issue, and this is not an issue in SLE12 and later versions of OpenSUSE I dont really mind. It gives me the strongest reason for upgrading to later versions of OpenSUSE. It was however extremely embarrassing to have to go begging for a boot disk. Best regards Owen -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=924488 --- Comment #6 from Dr. Werner Fink <werner@suse.com> --- (In reply to Felix Miata from comment #5) Then just do it. I've burned several times my finger with systemd updates on 13.1 due to the fact that users had not been able to debug their real or pretended issues, that is without a crystal ball I was not able to help not to fix those issues. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=924488 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume@suse.com Flags| |needinfo?(werner@suse.com) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=924488 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(werner@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=924488 --- Comment #11 from Thomas Blume <thomas.blume@suse.com> --- Created attachment 634816 --> http://bugzilla.suse.com/attachment.cgi?id=634816&action=edit proposed patch Let emergency target run in isolate mode to prevent dependency loops with other active targets. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=924488 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mrmazda@earthlink | |.net) --- Comment #12 from Thomas Blume <thomas.blume@suse.com> --- Felix, Owen, can you please check wheter the systemd version from: http://download.opensuse.org/repositories/home:/tsaupe:/branches:/openSUSE:/... fixes this issue on your machines? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=924488 --- Comment #13 from Owen Synge <osynge@suse.com> --- I have since upgraded all my nodes and my vm's to opensuse 13.2. This makes testing hard. Second I am working in Lisbon this week and bandwidth is a little limited so will be better to test next week when I am back in Hamburg. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=924488 http://bugzilla.suse.com/show_bug.cgi?id=924488#c16 --- Comment #16 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Felix Miata from comment #14)
(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.
http://bugzilla.suse.com/show_bug.cgi?id=924488 http://bugzilla.suse.com/show_bug.cgi?id=924488#c17 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mrmazda@earthlink | |.net) --- Comment #17 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Felix Miata from comment #15)
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.
http://bugzilla.suse.com/show_bug.cgi?id=924488 http://bugzilla.suse.com/show_bug.cgi?id=924488#c18 --- Comment #18 from Andrei Borzenkov <arvidjaar@gmail.com> --- (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. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=924488 http://bugzilla.suse.com/show_bug.cgi?id=924488#c19 --- Comment #19 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Andrei Borzenkov from comment #18)
(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.
http://bugzilla.suse.com/show_bug.cgi?id=924488 http://bugzilla.suse.com/show_bug.cgi?id=924488#c21 --- Comment #21 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Felix Miata from comment #20)
(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