public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Kazantsev <mike_kazantsev@fraggod.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Failed to start /etc/init.d/checkroot
Date: Sun, 26 Apr 2009 20:09:00 +0600	[thread overview]
Message-ID: <20090426200900.634583ea@coercion> (raw)
In-Reply-To: <7797aa370904260431t14cd3458kb120ca40fde88cb@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

On Sun, 26 Apr 2009 19:31:12 +0800
Chuanwen Wu <wcw8410@gmail.com> wrote:

> Hi,
> My gentoo failed to boot up. When my gentoo is booting up, after the message
> devpts
> "mounting devpts at /dev/pts     OK",
> then it just stoped, and then I pressed "CTRL + c" to interrupt it, and the
> message:
> "Failed to start /etc/init.d/checkroot“ appeared.
...
> How to fix this problem?

It seems a bit strange that checkroot gave no output, just failure -
as if it's execution didn't even started, and, since it's one of the
first initscripts to start, prehaps there's a problem with bash
interpreter or access to init.d path.

Since you've mounted filesystem and it looks okay, you can try changing
last two columns in /etc/fstab for root filesystem to "0 0", so script
won't try to check it - that way you can see if it's something with
fsck - prehaps the system will just boot.
Then, if the rest of the initscripts won't throw some similar errors
(possibly exposing the real problem), you can probably insert a lot of
echoes/einfos to that initscript to see at which point everything hangs
and check what's wrong with the command causing it.

-- 
Mike Kazantsev // fraggod.net

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-04-26 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 11:31 [gentoo-user] Failed to start /etc/init.d/checkroot Chuanwen Wu
2009-04-26 14:09 ` Mike Kazantsev [this message]
2009-04-27 11:38   ` Chuanwen Wu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090426200900.634583ea@coercion \
    --to=mike_kazantsev@fraggod.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox