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 1Od1jI-0004nG-LO for garchives@archives.gentoo.org; Sun, 25 Jul 2010 13:59:01 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E43BCE07EB; Sun, 25 Jul 2010 13:57:28 +0000 (UTC) Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181]) by pigeon.gentoo.org (Postfix) with ESMTP id A2E45E07EB for ; Sun, 25 Jul 2010 13:57:28 +0000 (UTC) Received: by wyb36 with SMTP id 36so1995705wyb.40 for ; Sun, 25 Jul 2010 06:57:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=m35sr/Q6Xlxb+oc5pC8jxaBf5xPJlbHLji9xm/sch+A=; b=BggGLdwilxEODQ83lxDrK9P9Cv5rnXIDtfVSWmUFN3MRAuTQPajpoD5e12OucMnD1H By+3u7gXAge85MzApt1SgY4ro//ZaaNOSpDnzhCJVWpTG4mXoLpJ9eu3ZScBjUK0Uwqp 3jvmgHz0hudZPW5vXpG4LX4EKdT3CcLNfHV/0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=dtb2YaJh0QX44adm8wWopUpXpkca+IkY1eY6Zsj/GeFf5dNcqsXEYS/VHXqjVMg2mA gQGgoZyATuIjgMjYEGPXe/GLVwTUApi6XQezh4SxIzaYV93gxmJ/zjp8wWchm/njNUUG WqENrXHAihhApggxb9DmueKbbwR0DI80vGbxM= Received: by 10.216.157.81 with SMTP id n59mr6057169wek.84.1280066248001; Sun, 25 Jul 2010 06:57:28 -0700 (PDT) Received: from (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id o84sm1303304wej.37.2010.07.25.06.57.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 25 Jul 2010 06:57:27 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Problems booting my server - ext2 - e2fsck Date: Sun, 25 Jul 2010 14:57:15 +0100 User-Agent: KMail/1.13.3 (Linux/2.6.34-gentoo-r1; KDE/4.4.4; x86_64; ; ) References: <4C4B45B2.4000508@konstantinhansen.de> <201007250949.17739.alan.mckinnon@gmail.com> <4C4BF359.4020404@gmail.com> In-Reply-To: <4C4BF359.4020404@gmail.com> 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: multipart/signed; boundary="nextPart2645931.HHvie8V5jM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201007251457.24446.michaelkintzios@gmail.com> X-Archives-Salt: 2a8a3476-3406-4546-ab9e-a836d7a2cab3 X-Archives-Hash: 64c0a5724feafafa6abbc639b59718ca --nextPart2645931.HHvie8V5jM Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable On Sunday 25 July 2010 09:18:33 Dale wrote: > Alan McKinnon wrote: > > On Sunday 25 July 2010 06:57:43 KH wrote: > >>> You said you ran e2fsck and it was OK. What was the command? > >>>=20 > >>>=20 > >>>=20 > >>> 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. > >>>=20 > >>>=20 > >>>=20 > >>> 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 > >>=20 > >> Hi, > >>=20 > >> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3 > >> /dev/sde3 . Yes, it only took some seconds. > >=20 > > It's been a long time since I used ext3 so some of this might be wrong. > >=20 > > 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: > >=20 > > 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. > >=20 > > When done, reboot as normal and see if the machine boots up properly. >=20 > And I would stand guard to make sure housekeeping doesn't come around. > ;-) Cutting power during all this wold not be good. KH, I think that this may not be related to a fs error as such. Yes, pulling the plug may have caused fs corruption. However, more likely = is=20 that pulling the plug did not allow you to do something that you should hav= e=20 done after you finished upgrading to grub-0.97-r9. The latest installation= of=20 grub asks you to reinstall in the MBR and point its root to wherever your=20 /boot is. GRUB's fs and its drivers may have changed and therefore the old= =20 boot loader code is looking for files that no longer exist. So you'll probably be alright again if you boot with a fresh systemrescue=20 LiveCD and run grub and then root (hd....) and setup (hd0) before you quit = and=20 reboot. If that doesn't work then you most likely have a fs problem. HTH. =2D-=20 Regards, Mick --nextPart2645931.HHvie8V5jM Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAkxMQsQACgkQVTDTR3kpaLZVAgCgl5++KlzgKolU31ahzHrVy0TN HIAAoKHKaKGUA1QuBloFxUL+II3p4t5q =VAH6 -----END PGP SIGNATURE----- --nextPart2645931.HHvie8V5jM--