From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-150310-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id A387B1381F3
for <garchives@archives.gentoo.org>; Mon, 2 Sep 2013 16:15:26 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id AD87DE0D39;
Mon, 2 Sep 2013 16:15:18 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21])
(using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 8BC56E0D30
for <gentoo-user@lists.gentoo.org>; Mon, 2 Sep 2013 16:15:17 +0000 (UTC)
Received: from gmx.net ([84.133.149.78]) by mail.gmx.com (mrgmx101) with
ESMTPA (Nemesis) id 0MWwp6-1VSeHv3BMC-00VzWl for
<gentoo-user@lists.gentoo.org>; Mon, 02 Sep 2013 18:15:15 +0200
Received: by gmx.net (nbSMTP-1.00) for uid 1001
meino.cramer@gmx.de; Mon, 2 Sep 2013 18:15:15 +0200 (CEST)
Date: Mon, 2 Sep 2013 18:15:15 +0200
From: meino.cramer@gmx.de
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Need help: Filesystem (ext4) corrupted!
Message-ID: <20130902161515.GA3446@solfire>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
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
User-Agent: mutt-ng/devel-r804 (Linux)
X-Provags-ID: V03:K0:1YZXVW7uEpg5giJ16SEcEIBuBtA3K2ZA8ZNZME/1xC3omI+oxgZ
wpzgAm4qbrYmHSh5UrObU2lwXTcsMf8ZZ5NZYdAd0XPMAyhfv3RNLwjMGTlz7qJXdJdZS1b
+pn1y2mNMZc56l+YtBZZc2v4+8YYwN0KekAef0YFTh/ne28cslOyHUORU/GQ+ypqZbU4//i
2lNQmcKWXG8NHMK3tdbkg==
X-Archives-Salt: 76f85777-14e1-435a-8120-f1f62125e55e
X-Archives-Hash: 9d7ed2c9727e897ad96ed26884ef12f7
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!
Best regards,
mcc