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 1Nmp8q-00084a-BR for garchives@archives.gentoo.org; Wed, 03 Mar 2010 14:01:36 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 874F3E09FF; Wed, 3 Mar 2010 14:01:24 +0000 (UTC) Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by pigeon.gentoo.org (Postfix) with ESMTP id 47FDBE09FF for ; Wed, 3 Mar 2010 14:01:24 +0000 (UTC) Received: by bwz19 with SMTP id 19so1211414bwz.26 for ; Wed, 03 Mar 2010 06:01:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=ns0dkjEbDj2uoLx//jv4ZrDeNVJS7hG7U0pNSQlhvwA=; b=HdNuz6KqxZa8ni7/Mii7mUnB13kEMVvulAQmPALiVmFozZdl8RzUlIb3MhOsugy+v6 t6q8kQxCrW32dcoB4D1lwcoph7EJRVdDz+pjTohZVOFxTjEkxF6MMO7LrHKPL6vV8VO/ 123Qy08WNejoHd9g+ApcjPAf3NVjfsv+Ciyok= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=uA0WiyMTEyi3zCrEpsJlaCTnhXWWTbIUJ0MRUv3keJJRGW0SdMLU1gOVjyLZrq4h5t OipfWZjsPfSMOC94Qz4CGSg1dhPCCXAoboM21BCaFa+USdzCF/HJeHj28Z3draNV/4wV WaZayFXjT36oBj+Q+xU9Ru43O0BEco0n4K92M= 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 Received: by 10.102.17.40 with SMTP id 40mr6105751muq.119.1267624878692; Wed, 03 Mar 2010 06:01:18 -0800 (PST) In-Reply-To: <084D821B-B1FA-461A-BEA2-2D231EB734C9@stellar.eclipse.co.uk> References: <838C106F-28D0-4DFB-822F-520EAECEE034@stellar.eclipse.co.uk> <20100303124248.GB2748@math.princeton.edu> <084D821B-B1FA-461A-BEA2-2D231EB734C9@stellar.eclipse.co.uk> Date: Wed, 3 Mar 2010 14:01:17 +0000 Message-ID: <358eca8f1003030601k15e6c8e7s978cf7eeaf9a50a9@mail.gmail.com> Subject: Re: [gentoo-user] Filesystem corruption - reiserfs? - won't boot, "filesystem couldn't be fixed :(" From: Mick To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 9839d286-c59c-44d2-b4fb-ed3681d43e18 X-Archives-Hash: fdaa8f7595a46c9815bafd9d441c627f On 3 March 2010 13:28, Stroller wrote: > > On 3 Mar 2010, at 12:42, Willie Wong wrote: > >> On Wed, Mar 03, 2010 at 12:24:42PM +0000, Stroller wrote: >>> >>> There seem to have been a few people posting with filesystem >>> corruption in the last week or two. It seems to be my turn, so I hope >>> it isn't contagious. The cause here is quite clear - whilst rummaging >>> in the server cupboard yesterday, power to the machine was >>> accidentally disconnected. >>> >>> I have booted with a live CD & run `reiserfsck --fix-fixable` on the >>> filesystem, but nevertheless when I attempt to boot the system I get a >>> "failed to open the device... no such file or directory" message, >>> followed by another error as per subject line. >> >> from the output it looks like you are mounting by label? What if you >> edit fstab to point to the device name /dev/hd?? instead of >> LABEL=root? Check the filesystem label to make sure it is ok? > > Many thanks for this suggestion, however following it makes no difference, > except in the trivia that it says "failed to open the device '/dev/hda3': No > such file or directory" (instead of "LABEL=..."). > > I also tried editing grub to point to /dev/sda3 (although admittedly with > the LABEL= entry in /etc/fstab) but that makes no difference. I have never > tried (intentionally) reconfiguring this kernel to use /dev/sdX instead of > /dev/hdX and I'm pretty sure it's booted using the current kernel & > configuration in the past. In my experience reiserfs is a very stable fs. I had a dodgy memory module once which I put up with for more than 9 months. The machine would lock up hard on a daily basis and the only way to get it going again would be to pull the plug. That would happen at random, midstream emerge --sync, package updates, updatedb, etc. It survived through hundreds of crashes by fsck at the next boot. Once or twice things went hairy and I would get a message similar to yours. On these rare occasions I booted with a LiveCD and with the partitions unmounted I ran --check, then --fix-fixable and finally --rebuild-tree. You may want to use an external drive with dd to image the current / partition and do all your recovery work on that. If you don't care too much about the risk of catastrophic failure then just run --rebuild-tree with a LiveCD and see what you get. Good luck. -- Regards, Mick