| 1 |
walt <w41ter@×××××.com> [13-09-03 04:15]: |
| 2 |
> On 09/02/2013 09:15 AM, meino.cramer@×××.de wrote: |
| 3 |
> > The rootfs and $HOME of my embedded system is stored |
| 4 |
> > on a 16GB SD-card (about 5GB used, rest free). The FS |
| 5 |
> > is ext4. |
| 6 |
> > |
| 7 |
> > Since the system hangs for unknown reasons several times |
| 8 |
> |
| 9 |
> Does it hang at a predictable point, like during boot, or poweroff? |
| 10 |
> |
| 11 |
> I know almost nothing about SD cards (yet). Do they develop bad |
| 12 |
> blocks like other storage media? I notice fsck.ext4 has a -c flag |
| 13 |
> to check for bad blocks. |
| 14 |
> |
| 15 |
|
| 16 |
No, it hangs while compiling or while updateing (eix-sync; emerge ...). |
| 17 |
|
| 18 |
|
| 19 |
I did the following now: |
| 20 |
I did a binary image backup with dd of the sdcard. |
| 21 |
I made a backup of the all files from the bad fs with tar. |
| 22 |
I say "YES" to fsck to fix what it found. |
| 23 |
I made another backup of the all files from the bad fs with tar. |
| 24 |
I md5summed both tar archives and found them identical. |
| 25 |
|
| 26 |
Now...is the conclusion correct, that the identical md5sum |
| 27 |
indicate, that the fixed error of the fs only had impact to |
| 28 |
already invalidated data? |
| 29 |
Or whatelse could this indicate? |
| 30 |
|
| 31 |
Best regards, |
| 32 |
mcc |
| 33 |
|
| 34 |
PS: What come mind just in this moment: |
| 35 |
Can I ran fsck on an binary image of the fs which I made with dd somehow? |
Archives