Pandu Poluan <pa...@poluan.info> [13-09-02 18:40]: > On Sep 2, 2013 11:16 PM, <meino.cra...@gmx.de> wrote: > > > > 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! > > > > I'm not really sure how to fix the corrupt fs, but don't forget to backup > the whole disk using dd > > Rgds, > --
Currently doing exactly this... mcc
