On Thursday 25 June 2015 08:33:25 The Wanderer wrote:
> On 06/25/2015 at 07:54 AM, Matthijs Wensveen wrote:
> > Hi,
> >
> > I'm running unstable / sid. Yesterday, I suddenly started booting
> > into emergency mode and I'm unsure why. I had a hang the day before,
> > right after a apt-get dist-upgrade, so it might be either one of
> > those, or something else altogether.
> >
> > Booting into emergency mode doesn't help me, as I can neither login
> > without a root password, nor continue to default mode with Ctrl-D
> > because that just throws me back into emergency mode.
>
> Why don't you have the root password? Is this not your system, but
> just one you've been given for ordinary use?
I have seen this also. The 1st users passwd (sudo) was not acceptable.
For some reason its asking for the root passwd, and the root passwd had
never been setup as everything up to that point had been done using sudo
by the first user. How it occurs I have no clue, but a re-install,
setting up a 1Gb first partition as /boot for the next install seems to
have fixed it. The box was quite ancient, with a 1Ghz Athlon cpu, and
the bios was incapable of dealing with a 500Gb Maxtor drive without that
1st /boot partition. But it was the last good IDE drive I had. No
further problems with that box other than its horrible IRQ latency have
been encountered. Yesterday I managed to make it turn motors, albeit
slowly from a session of LinuxCNC. I have a card and a faster BoB on a
truck someplace, which should fix the slow speeds rather nicely.
> > I'm rather stuck on how to analyze the situation. I can mount and
> > even chroot into the '/' partition from a live CD (LMDE 2) and even
> > run apt-get update && apt-get upgrade, but the boot problem
> > persists. I can also boot with init=/bin/sh, but I don't know what
> > to look for.
> >
> > Any ideas on what I should try? Any help is much appreciated.
>
> When booted from a LiveCD or with a different init, check to see what
> information may have made it into logs from the previous failed boot
> attempts.
>
> If nothing has, you might see if you can get any information out at
> the time of the boot failure, over a serial console or netconsole.
> (Good luck with that; I've never set one up myself, although I know
> the kernel developers use them routinely.)
>
> Make sure you have a valid init installed and configured, by
> reinstalling the appropriate packages ('apt-get install --reinstall
> packagename') if necessary.
>
> There's not really anything I can say to suggest the possible actual
> problem without knowing what the messages around the "hang" and/or the
> "drop into emergency mode" failures are.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201506251012.40550.ghesk...@wdtv.com
