[opensuse] systemd.fsck looping
One of my backup systems failed last week, bad power supply. Having replaced the power supply, it now fails to complete boot - systemd.fsck is looping. It keeps fsck'ing something which fails, upon which systemd.fsck says "welcome to emergency mode", then starts over with the fsck. I guess the next thing is to boot a rescue system, then modify the fstab to omit mounting the failing filesystem. (unless there is a way of specifying that as a startup argument?) -- Per Jessen, Zürich (19.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 05/08/14 a las #4, Per Jessen escribió:
One of my backup systems failed last week, bad power supply. Having replaced the power supply, it now fails to complete boot - systemd.fsck is looping. It keeps fsck'ing something which fails, upon which systemd.fsck says "welcome to emergency mode", then starts over with the fsck.
I guess the next thing is to boot a rescue system, then modify the fstab to omit mounting the failing filesystem. (unless there is a way of specifying that as a startup argument?)
Boot with fsck.mode=skip -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2014 05:42 AM, Per Jessen wrote:
One of my backup systems failed last week, bad power supply. Having replaced the power supply, it now fails to complete boot - systemd.fsck is looping. It keeps fsck'ing something which fails, upon which systemd.fsck says "welcome to emergency mode", then starts over with the fsck.
I guess the next thing is to boot a rescue system, then modify the fstab to omit mounting the failing filesystem. (unless there is a way of specifying that as a startup argument?)
Or manually use fsck to repair the fs in question. BTDT. The "-a" used by boot if not always adequate and fsck needs a guiding hand. We humans still have uses even in this day of driverless cars and automated production lines. OBTW: Didn't 'emergency mode' offer you the opportunity of a root login? -- The Soft overcomes the Hard The Slow overcomes the Fast Let your workings remain a mystery Just show people the Results -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Tue, 05 Aug 2014 08:25:35 -0400 Anton Aylward <opensuse@antonaylward.com> пишет:
OBTW: Didn't 'emergency mode' offer you the opportunity of a root login?
https://bugzilla.novell.com/show_bug.cgi?id=852021 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrey Borzenkov wrote:
В Tue, 05 Aug 2014 08:25:35 -0400 Anton Aylward <opensuse@antonaylward.com> пишет:
OBTW: Didn't 'emergency mode' offer you the opportunity of a root login?
I'm not sure if that applies - I'm using syslog-ng and I get the emergency shell, it's just pretty difficult to work with. -- Per Jessen, Zürich (23.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrey Borzenkov wrote:
В Tue, 05 Aug 2014 08:25:35 -0400 Anton Aylward <opensuse@antonaylward.com> пишет:
OBTW: Didn't 'emergency mode' offer you the opportunity of a root login?
Um... emergency mode is what is run BEFORE any services or service managers are run -- ... before disks are mounted before udev or lvm has started... and certainly before systemd has run. Systemd requires too many things to already be setup to be usable for an emergency mode, IMO. Under sysvinit, emergency mode came up even before the initial boot scripts ran (which were before the single user scripts). How can one boot up into a shell mode before systemd starts? That's emergency mode, or pre-boot mode. That's the most common mode I've used in rescuing a system, since by runlevel 1, all my file systems are mounted along with devices. How do you run the pre-startup, pre-sysinit emergency mode? Can I interactively run each step in systemd's startup list to see what fails? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 05/08/14 a las #4, Linda Walsh escribió:
Andrey Borzenkov wrote:
How can one boot up into a shell mode before systemd starts?
That functionality is in the initrd.. boot with rd.break kernel parameter.
Can I interactively run each step in systemd's startup list to see what fails?
Boot with systemd.confirm_spawn=true , see init(1) for more details. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 08/05/2014 05:42 AM, Per Jessen wrote:
One of my backup systems failed last week, bad power supply. Having replaced the power supply, it now fails to complete boot - systemd.fsck is looping. It keeps fsck'ing something which fails, upon which systemd.fsck says "welcome to emergency mode", then starts over with the fsck.
I guess the next thing is to boot a rescue system, then modify the fstab to omit mounting the failing filesystem. (unless there is a way of specifying that as a startup argument?)
Or manually use fsck to repair the fs in question.
Sure, but that's only possible when I have access to the system, which the looping systemd.fsck prevents :-(
OBTW: Didn't 'emergency mode' offer you the opportunity of a root login?
Sort of, but it didn't work very well. I tried booting with "init S" as well as "systemd.unit=rescue.target", both modes worked, but the shell was weird and difficult to work with. Had to press enter twice to get input copied to the screen, for instance. Kept asking for the root password. -- Per Jessen, Zürich (23.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2014 11:37 AM, Per Jessen wrote:
Anton Aylward wrote:
On 08/05/2014 05:42 AM, Per Jessen wrote:
One of my backup systems failed last week, bad power supply. Having replaced the power supply, it now fails to complete boot - systemd.fsck is looping. It keeps fsck'ing something which fails, upon which systemd.fsck says "welcome to emergency mode", then starts over with the fsck.
I guess the next thing is to boot a rescue system, then modify the fstab to omit mounting the failing filesystem. (unless there is a way of specifying that as a startup argument?)
Or manually use fsck to repair the fs in question.
Sure, but that's only possible when I have access to the system, which the looping systemd.fsck prevents :-(
OBTW: Didn't 'emergency mode' offer you the opportunity of a root login?
Sort of, but it didn't work very well. I tried booting with "init S" as well as "systemd.unit=rescue.target", both modes worked, but the shell was weird and difficult to work with. Had to press enter twice to get input copied to the screen, for instance. Kept asking for the root password.
Hmmm. Sounds like there were two instances I've had that happen to me. Hard to tell them apart. You think you are giving a command at one shell when actually the input is going to the login process and its trying to get a password from you. I don't know why that kind of thing happens, but it does. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 08/05/2014 11:37 AM, Per Jessen wrote:
Anton Aylward wrote:
On 08/05/2014 05:42 AM, Per Jessen wrote:
One of my backup systems failed last week, bad power supply. Having replaced the power supply, it now fails to complete boot - systemd.fsck is looping. It keeps fsck'ing something which fails, upon which systemd.fsck says "welcome to emergency mode", then starts over with the fsck.
I guess the next thing is to boot a rescue system, then modify the fstab to omit mounting the failing filesystem. (unless there is a way of specifying that as a startup argument?)
Or manually use fsck to repair the fs in question.
Sure, but that's only possible when I have access to the system, which the looping systemd.fsck prevents :-(
OBTW: Didn't 'emergency mode' offer you the opportunity of a root login?
Sort of, but it didn't work very well. I tried booting with "init S" as well as "systemd.unit=rescue.target", both modes worked, but the shell was weird and difficult to work with. Had to press enter twice to get input copied to the screen, for instance. Kept asking for the root password.
Hmmm. Sounds like there were two instances I've had that happen to me. Hard to tell them apart. You think you are giving a command at one shell when actually the input is going to the login process and its trying to get a password from you.
I don't know why that kind of thing happens, but it does.
It felt a lot like a bug, happened every time I rebooted. -- Per Jessen, Zürich (23.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrey Borzenkov -
Anton Aylward -
Cristian Rodríguez -
Linda Walsh -
Per Jessen