From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KIZRG-0006R9-5H for garchives@archives.gentoo.org; Tue, 15 Jul 2008 01:34:46 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E64C0E0468; Tue, 15 Jul 2008 01:34:43 +0000 (UTC) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by pigeon.gentoo.org (Postfix) with ESMTP id 8C70CE0468 for ; Tue, 15 Jul 2008 01:34:43 +0000 (UTC) Received: by ug-out-1314.google.com with SMTP id z27so330073ugc.49 for ; Mon, 14 Jul 2008 18:34:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=lHZ4mnaeuZVUh9VL63HO7N/eV/trASblgiwfkdlNp0Q=; b=EwVYCdmQTOd3uL2K5R0mS+xy4oHj2vB1M4Lg5gTKEh/TrjjycS/Mu67WyZoMZfHh1B e8z8BCw6WRAjwpI+oaiSuR8BSpywYoC5TZFFYSfCpmD2eP+bTjmxJR9tse25DNY/m0WJ FpkQIRkn7zqzYjCm+DepQ2qZ1ZVJhOcblRtQo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=XGiTJX+sVXNcOpZ+WktGFjlJrWcbq8iQhdZGp2TC6skxE81mvzAep8+G/Eg6xqWpI6 n6ltiVgKQQpprrtK3ClELVAUTxOFk0hHqreYiYNKQIjFAXSmmpw5pRvlMjtcDP+M1aHa 44Kdiwbrrf/0xLCYQrMDQ4qtpK5beoeju36bs= Received: by 10.103.11.7 with SMTP id o7mr2451355mui.103.1216085682726; Mon, 14 Jul 2008 18:34:42 -0700 (PDT) Received: by 10.103.18.5 with HTTP; Mon, 14 Jul 2008 18:34:42 -0700 (PDT) Message-ID: Date: Tue, 15 Jul 2008 02:34:42 +0100 From: "Duane Griffin" Sender: duaneg@gmail.com To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Unable to mount root dir, Segmentation failure with mount In-Reply-To: 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-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1216064454-20755-mlmmj-6fbde1ed@lists.gentoo.org> X-Google-Sender-Auth: 1c7f65fed9affca5 X-Archives-Salt: ad98c606-cdb7-42fa-b46f-88d47dce0b93 X-Archives-Hash: dd58085d5ab41499c679b500b3f600b7 2008/7/14 : > Hi gentoo-users, > > I'm running Gentoo flawlessly on my laptop for nearly one year now, but > since yesterday, I'm in big trouble. At some instance (surfing in the web,.. > nothing horrible) the screen froze and the only thing I was able to do, was > pressing the power button 4seconds to shut the computer down. > > I was never able to boot my system since then. > > It sayed always things like: Not able to find root file system (or > likewise) Ouch. > So I plugged in my live-cd to recover the whole thing... Good idea. > But I wasn't able to mount the root partition, so I tried e2fsck, which > turned out to find a whole lot of errors and told me that it corrected them. Not such a good idea. For future reference, unless you don't mind losing the data, always take a block-level snapshot, if possible, before doing anything else. You don't know what state things are in, writing to it could make the situation worse. > Thus I retried to mount the file system, which resulted in an big error of > mount, saying something about Kernel BUG (?!?) D'oh! Congratulations, you found a kernel bug! :) > At that point I realized that this could become a major problem for me, > since all my personal data is on my root partition (I know, I should't do > that...but thats the way things are right now) Oh dear. You have backups, right? > I used dd to make a copy of this partition to an external hard disk, and > begun to recover it from there. Excellent! > dd gave no errors as it copied the partition, so I think this is no hardware > failure Hopefully. I'd be extra careful about backups for a while, though. > I rerun e2fsck on the partition, it corrected a little more, but after that, > it didn't found anything new, but I still wasn't able to mount the partition > (nor the partition dump) > > The crutial part of the dmesg output seems to be: > > Assertion failure in cleanup_journal_tail() at fs/jbd/checkpoint.c:430: > "blocknr != 0" > > Is this a known issue with ext3 filesystems? Google says someone else hit it once upon a time, but it doesn't seem to be listed on the kernel bugzilla. Your journal is corrupted and the kernel is not being as careful as it should before using on-disk data. If you remove the journal you will hopefully get some or all of your data back. On a *COPY* of the partition image do the following to replace the old journal with a new one: tune2fs -O ^has_journal e2fsck -f tune2fs -j e2fsck -f If everything looks OK and the data you care about is all there then you can go ahead and fix up your real disk. If you wouldn't mind though, please keep a copy of the corrupted image. I'll prepare a patch to fix the BUG and it would be helpful if you could test it once it is ready. > Thaks in andvance for any help, > > Carsten Cheers, Duane. -- "I never could learn to drink that blood and call it wine" - Bob Dylan -- gentoo-user@lists.gentoo.org mailing list