walt <w41...@gmail.com> [13-09-03 04:15]: > On 09/02/2013 09:15 AM, meino.cra...@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?
