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 90BE71381F3 for ; Mon, 2 Sep 2013 16:39:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 21ECFE0CF6; Mon, 2 Sep 2013 16:39:20 +0000 (UTC) Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1CB03E0CAB for ; Mon, 2 Sep 2013 16:39:19 +0000 (UTC) Received: from mail-ve0-f178.google.com ([209.85.128.178]:40462) by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1VGX9t-001Rls-2L for gentoo-user@lists.gentoo.org; Mon, 02 Sep 2013 23:39:21 +0700 Received: by mail-ve0-f178.google.com with SMTP id ox1so3223058veb.37 for ; Mon, 02 Sep 2013 09:39:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=4jTRgUL1jwGIutvdhIos4z8x2vlToTSNY5HPtTHprSw=; b=MQaLDiZQoYigVWE4QGDjuenbAbWD9Tyj1auYdrGYYAZSpkGpbPPjpWbM3m/J+ybIuf kiq8Agw2H4y6zOFDlYNa7/Me1LsiH+BxClGJ2UFcSgsHJvpPAv0VfyAg+XaHZMN83xf+ Don0gy6wXy9nz1DfG+pltOx6QwPpFXfAV2MTkLfre6Xsc7gQynZhOKCc9jW4F9tfPepH 0P89wL7zrEmyJJEivABNq3pnN9TeMWPKGSzanw38Z9rQc8Eivw+Nz2flfwYUOpsozUTA AKI/APdFXUEzMPr8ZjSGN1AGYYzLtWCg+CYgEM++LDRrB6wsWuNXsM2VM/ZONQxBvIPi xnKg== 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 X-Received: by 10.52.232.165 with SMTP id tp5mr19361054vdc.11.1378139957945; Mon, 02 Sep 2013 09:39:17 -0700 (PDT) Received: by 10.220.163.69 with HTTP; Mon, 2 Sep 2013 09:39:17 -0700 (PDT) Received: by 10.220.163.69 with HTTP; Mon, 2 Sep 2013 09:39:17 -0700 (PDT) In-Reply-To: <20130902161515.GA3446@solfire> References: <20130902161515.GA3446@solfire> Date: Mon, 2 Sep 2013 23:39:17 +0700 Message-ID: Subject: Re: [gentoo-user] Need help: Filesystem (ext4) corrupted! From: Pandu Poluan To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=089e0122f480a4f07c04e5693639 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - poluan.info X-Get-Message-Sender-Via: svr-us4.tirtonadi.com: authenticated_id: rileyer+pandu.poluan.info/only user confirmed/virtual account not confirmed X-Archives-Salt: 2f8011b5-5c99-4dc9-a001-4f980a254e4c X-Archives-Hash: 3963df5a632d5b5dcf03d7a7b803345d --089e0122f480a4f07c04e5693639 Content-Type: text/plain; charset=UTF-8 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, -- --089e0122f480a4f07c04e5693639 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sep 2, 2013 11:16 PM, <meino.c= ramer@gmx.de> 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:
>
> =C2=A0 =C2=A0 solfire:/root>fsck.ext4 -f -p /dev/sdb2
> =C2=A0 =C2=A0 rootfs: Inodes that were part of a corrupted orphan link= ed list found.
>
> =C2=A0 =C2=A0 rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 (i.e., without -a or -p options)
> =C2=A0 =C2=A0 [1] =C2=A0 =C2=A018644 exit 4 =C2=A0 =C2=A0 fsck.ext4 -f= -p /dev/sdb2
>
>
> Return code 4 means
>
> =C2=A0 =C2=A0 4 =C2=A0 =C2=A0- 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<= br> > 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&#= 39;t forget to backup the whole disk using dd

Rgds,
--

--089e0122f480a4f07c04e5693639--