[Bug 900558] New: Impossible to boot in single user mode with root mounted read only
http://bugzilla.opensuse.org/show_bug.cgi?id=900558 Bug ID: 900558 Summary: Impossible to boot in single user mode with root mounted read only Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: archie@dellroad.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I have a 13.1 system with all the latest updates as of today and it is spitting out the UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY message for the root filesystem, and then booting normally with root mounted root read-write. First of all, I would expect it to not boot normally in this case, but whatever. Anyway, when I try to do what it says, it's impossible! Here's why: even though I reboot with "single ro" on the boot line and it does in fact go into single user mode, it still mounts root read-write (after complaining of the same fsck errors). Since the 1980's single user mode has always left root mounted read-only so you can run fsck if needed, and you can always remount it read-write if you want. Why did this change? Of course "mount -o remount,ro /" doesn't work. Because root is mounted read-write and it's impossible to get the system to boot with root mounted read-only, then even in single user mode, it's impossible to run fsck and fix the problem. So it's impossible to resolve this problem without the use of a rescue disk. Please fix, this is a bad dead-end people can fall into. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900558 --- Comment #1 from Archie Cobbs <archie@dellroad.org> --- See also Bug #873919 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900558 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |bwiedemann@suse.com, | |trenn@suse.com Assignee|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | --- Comment #2 from Bernhard Wiedemann <bwiedemann@suse.com> --- I was able to reproduce it here (appending ro 1), except that mount -o remount,ro / worked for me (possibly depending on rootfs type or services running) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900558 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkubecek@suse.com Assignee|systemd-maintainers@suse.de |ohering@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900558 http://bugzilla.opensuse.org/show_bug.cgi?id=900558#c21 --- Comment #21 from Archie Cobbs <archie@dellroad.org> --- Hi folks. Can someone please explain what is the status of this bug? Is this fixed in 13.1 now? If not, is there a workaround? I need a little practical advice. I have a funny desire to have my machines to be recoverable. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900558 http://bugzilla.opensuse.org/show_bug.cgi?id=900558#c23 --- Comment #23 from Archie Cobbs <archie@dellroad.org> --- Thanks. I am still wondering: is there a workaround that I can use today, on a 13.1 system, until this is resolved? For example, would adding "rd.break=pre-mount" as a boot parameter work? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900558 http://bugzilla.opensuse.org/show_bug.cgi?id=900558#c75 - - <mikccc@tutanota.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikccc@tutanota.com --- Comment #75 from - - <mikccc@tutanota.com> --- I'm trying to boot a snapshot read-only on Tumbleweed. With "ro rootflags=ro,subvol=/@/.snapshots/212/snapshot systemd.unit=rescue.target" both "ro" options are ignored, while "subvol" is respected. Is it intended behaviour? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com