From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 5E2161381F3 for ; Mon, 2 Sep 2013 16:41:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7A6F3E0D70; Mon, 2 Sep 2013 16:41:38 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3C6D6E0D43 for ; Mon, 2 Sep 2013 16:41:37 +0000 (UTC) Received: from gmx.net ([84.133.149.78]) by mail.gmx.com (mrgmx101) with ESMTPA (Nemesis) id 0LpObx-1Vt97y0omj-00fASQ for ; Mon, 02 Sep 2013 18:41:35 +0200 Received: by gmx.net (nbSMTP-1.00) for uid 1001 meino.cramer@gmx.de; Mon, 2 Sep 2013 18:41:35 +0200 (CEST) Date: Mon, 2 Sep 2013 18:41:34 +0200 From: meino.cramer@gmx.de To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Need help: Filesystem (ext4) corrupted! Message-ID: <20130902164134.GB3446@solfire> References: <20130902161515.GA3446@solfire> 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=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: mutt-ng/devel-r804 (Linux) X-Provags-ID: V03:K0:Pc7/TAY1qN7eSTUP3u6ptbNtTbSgdEHPF+zlM5Z5c3UsO7v7vKw TGIZwN7HCjLsnAB66QBCKQQRDmrUaIThHIsvRtSeBBUPZz1Lpmnkz7u7GqjTMY+xK7oZ3rc XlAt/FEAj2dT7oe/Kf/jNTZyjxXVGae33P5geMODQEQFiJbqnjbFLRFctxWgODenYVkIIY7 ZEMujDxMh+op15s1r3TuQ== X-Archives-Salt: d137dab9-afd9-42d6-b53d-a412361dcaa0 X-Archives-Hash: 7f9037de5b11a7d439a64e16bcc60c93 Pandu Poluan [13-09-02 18:40]: > On Sep 2, 2013 11:16 PM, wrote: > > > > Hi, > > > > > > > > I need some urgent help... > > > > > > > > The rootfs and $HOME of my embedded system is stored > > on a 16GB SD-card (about 5GB used, rest free). The FS > > is ext4. > > > > Since the system hangs for unknown reasons several times I > > removed the sdcard, put it in a card reader and did an > > ext4.fsck on it. > > > > "Clean" was the result. > > > > Then I forced a check with "-f -p". > > > > The result was: > > > > solfire:/root>fsck.ext4 -f -p /dev/sdb2 > > rootfs: Inodes that were part of a corrupted orphan linked list found. > > > > rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > > (i.e., without -a or -p options) > > [1] 18644 exit 4 fsck.ext4 -f -p /dev/sdb2 > > > > > > Return code 4 means > > > > 4 - File system errors left uncorrected > > > > which indicates nothing and all at the same time. > > > > > > At this point I started to write this mail. > > > > Before I fscked the sdcard I mounted the FS and tar'ed everything on > > it into a backup file. > > > > The tar process did not return an error. > > > > Since it costs A LOT OF TIME to compile everything from source on a > > 1GHz CPUed embedded system natively - and for abvious different other > > reasons - I am very interested in doing the next steps correctly. > > > > What can I do to eliminate the problem without data loss (best > > case) or to save the most while knowing what and where the corrupted > > data are located on the system? > > > > Thank you very much in advance for any help! > > > > I'm not really sure how to fix the corrupt fs, but don't forget to backup > the whole disk using dd > > Rgds, > -- Currently doing exactly this... mcc