From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ocw1h-0001Gi-6f for garchives@archives.gentoo.org; Sun, 25 Jul 2010 07:53:37 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E98D0E0801; Sun, 25 Jul 2010 07:52:28 +0000 (UTC) Received: from mail-ew0-f53.google.com (mail-ew0-f53.google.com [209.85.215.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 5D83EE0801 for ; Sun, 25 Jul 2010 07:52:28 +0000 (UTC) Received: by ewy19 with SMTP id 19so680193ewy.40 for ; Sun, 25 Jul 2010 00:52:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=cg0w+augu3b97mTOVyGOHZz2qVy2FASB4J+YA+QyHg8=; b=FGigvooHVcYqtACzkU34DXncYfZq5ZJqpyzN11n5fWbn1G/4YcIKc2ona8uAdqiXeo ftpcTZFxQo7zcR/YbW0sIkE/BD+T6t7/Aplg+ZVBRl7kDtJyOptBELqcHwpZvHF8cj1m CQigZIbJyE7uzyYQbzH/hUdARern6YwV/uBs4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=Ba9B7qZsF7rCtPhG0h9gLNWqRu9k/IxSvzoG2k4+bJR5gRAQtdubigNOWETeF3by0C p6qMAvcmsNt/V9/5mDf0U/NmIgLyQNlhOJ8TpieknR7RuI1QK0VGRUkfYZtqr3Gms5dN c6mneyq+S0SKq8QN5D2vMOZw+EAGDLcm5qu8Q= Received: by 10.213.22.201 with SMTP id o9mr2342155ebb.93.1280044347703; Sun, 25 Jul 2010 00:52:27 -0700 (PDT) Received: from nazgul.localnet (196-210-183-170.dynamic.isadsl.co.za [196.210.183.170]) by mx.google.com with ESMTPS id a48sm3471266eei.7.2010.07.25.00.52.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 25 Jul 2010 00:52:26 -0700 (PDT) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Problems booting my server - ext2 - e2fsck Date: Sun, 25 Jul 2010 09:49:17 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.34-ck-r1; KDE/4.4.5; x86_64; ; ) Cc: KH References: <4C4B45B2.4000508@konstantinhansen.de> <201007242221.12550.alan.mckinnon@gmail.com> <4C4BC447.6010803@konstantinhansen.de> In-Reply-To: <4C4BC447.6010803@konstantinhansen.de> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201007250949.17739.alan.mckinnon@gmail.com> X-Archives-Salt: ce07c64f-d420-4419-9c84-02193dfcb7eb X-Archives-Hash: 4384d362fe2040a342d76b48bc8171c3 On Sunday 25 July 2010 06:57:43 KH wrote: > > You said you ran e2fsck and it was OK. What was the command? > > > > > > > > Normally with an e2fsck on a journalled fs, the app will replay the > > journal and make a few minor checks. This takes about 4 seconds, not > > the 40 minutes it takes to do a ful ext2 check. > > > > > > > > I think you might need to fsck without the journal. I know there's a way > > to do this but a cursory glance at the man page didn't reveal it. Maybe > > an ext user will chip in with the correct method > > > > > > > > > > Hi, > > I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3 > /dev/sde3 . Yes, it only took some seconds. It's been a long time since I used ext3 so some of this might be wrong. An fsck that takes a few seconds is using the journal, which might not uncover deeper corruption. You should try disabling the journal (I couldn't find the way to do that though), but this will also work: Boot of a LiveCD, mount your root partition somewhere using type "ext2" and fsck it. This will invalidate the journal but that's OK, it gets recreated on the next proper boot. Let the fsck finish - it will take a while on a large fs. When done, reboot as normal and see if the machine boots up properly. -- alan dot mckinnon at gmail dot com