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 D89FA1381F3 for ; Tue, 3 Sep 2013 02:45:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DDF84E0DCC; Tue, 3 Sep 2013 02:45:07 +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 AC3D6E0D72 for ; Tue, 3 Sep 2013 02:45:06 +0000 (UTC) Received: from gmx.net ([84.133.147.18]) by mail.gmx.com (mrgmx003) with ESMTPA (Nemesis) id 0MBWTO-1V7MwR0kMQ-00AZxk for ; Tue, 03 Sep 2013 04:45:05 +0200 Received: by gmx.net (nbSMTP-1.00) for uid 1001 meino.cramer@gmx.de; Tue, 3 Sep 2013 04:45:05 +0200 (CEST) Date: Tue, 3 Sep 2013 04:45:04 +0200 From: meino.cramer@gmx.de To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Need help: Filesystem (ext4) corrupted! Message-ID: <20130903024504.GB3409@solfire> References: <20130902161515.GA3446@solfire> <52250FF3.6050305@gmail.com> 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: <52250FF3.6050305@gmail.com> User-Agent: mutt-ng/devel-r804 (Linux) X-Provags-ID: V03:K0:VWs5Z55MX2jmDVupOC3TOjfDlhu0MIcwjkcqF93PJL+AMkwx3+k dPympTeZs6Qq2DwX9pkBOAnVroqrSeRDdRE4eRKowWOhtQ6jD18jN3PM3SdiMwbAHTHepvI loRQoZa5rUO6l1Bh4oR4H+W5IC+DTOYAl755tLa6oiGphIUeUvqlgQSTGP1LD8zBqcZ4rnj u4uZ3A45LYqCTDaaLKw6Q== X-Archives-Salt: 3926d207-092d-46b8-9efd-002dd8c113cd X-Archives-Hash: be1a4bc98b3b0b3e65fc53a119a90d39 walt [13-09-03 04:15]: > On 09/02/2013 09:15 AM, meino.cramer@gmx.de wrote: > > 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 > > Does it hang at a predictable point, like during boot, or poweroff? > > I know almost nothing about SD cards (yet). Do they develop bad > blocks like other storage media? I notice fsck.ext4 has a -c flag > to check for bad blocks. > No, it hangs while compiling or while updateing (eix-sync; emerge ...). I did the following now: I did a binary image backup with dd of the sdcard. I made a backup of the all files from the bad fs with tar. I say "YES" to fsck to fix what it found. I made another backup of the all files from the bad fs with tar. I md5summed both tar archives and found them identical. Now...is the conclusion correct, that the identical md5sum indicate, that the fixed error of the fs only had impact to already invalidated data? Or whatelse could this indicate? Best regards, mcc PS: What come mind just in this moment: Can I ran fsck on an binary image of the fs which I made with dd somehow?