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