public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Need help: Filesystem (ext4) corrupted!
Date: Tue, 3 Sep 2013 04:45:04 +0200	[thread overview]
Message-ID: <20130903024504.GB3409@solfire> (raw)
In-Reply-To: <52250FF3.6050305@gmail.com>

walt <w41ter@gmail.com> [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?






  parent reply	other threads:[~2013-09-03  2:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 16:15 [gentoo-user] Need help: Filesystem (ext4) corrupted! meino.cramer
2013-09-02 16:39 ` Pandu Poluan
2013-09-02 16:41   ` meino.cramer
2013-09-02 22:23 ` [gentoo-user] " walt
2013-09-02 22:46   ` Francisco Ares
2013-09-03  2:39     ` meino.cramer
2013-09-03  2:45   ` meino.cramer [this message]
2013-09-03  3:07     ` William Kenworthy
2013-09-03  3:26       ` meino.cramer
2013-09-03  3:47         ` William Kenworthy
2013-09-03  5:13           ` Pandu Poluan
2013-09-03 16:06             ` meino.cramer
2013-09-03 20:55               ` Alan McKinnon
2013-09-03 14:13           ` Francisco Ares
2013-09-03 15:56             ` meino.cramer
2013-09-03 16:11           ` meino.cramer
2013-09-03 23:26             ` Francisco Ares
2013-09-04  0:22               ` meino.cramer
2013-09-06 15:18                 ` Francisco Ares
2013-09-03  6:18     ` J. Roeleveld
2013-09-18 17:54     ` Daniel Wagener

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130903024504.GB3409@solfire \
    --to=meino.cramer@gmx.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox