1 |
Pandu Poluan <pandu@××××××.info> [13-09-02 18:40]: |
2 |
> On Sep 2, 2013 11:16 PM, <meino.cramer@×××.de> wrote: |
3 |
> > |
4 |
> > Hi, |
5 |
> > |
6 |
> > |
7 |
> > |
8 |
> > I need some urgent help... |
9 |
> > |
10 |
> > |
11 |
> > |
12 |
> > The rootfs and $HOME of my embedded system is stored |
13 |
> > on a 16GB SD-card (about 5GB used, rest free). The FS |
14 |
> > is ext4. |
15 |
> > |
16 |
> > Since the system hangs for unknown reasons several times I |
17 |
> > removed the sdcard, put it in a card reader and did an |
18 |
> > ext4.fsck on it. |
19 |
> > |
20 |
> > "Clean" was the result. |
21 |
> > |
22 |
> > Then I forced a check with "-f -p". |
23 |
> > |
24 |
> > The result was: |
25 |
> > |
26 |
> > solfire:/root>fsck.ext4 -f -p /dev/sdb2 |
27 |
> > rootfs: Inodes that were part of a corrupted orphan linked list found. |
28 |
> > |
29 |
> > rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. |
30 |
> > (i.e., without -a or -p options) |
31 |
> > [1] 18644 exit 4 fsck.ext4 -f -p /dev/sdb2 |
32 |
> > |
33 |
> > |
34 |
> > Return code 4 means |
35 |
> > |
36 |
> > 4 - File system errors left uncorrected |
37 |
> > |
38 |
> > which indicates nothing and all at the same time. |
39 |
> > |
40 |
> > |
41 |
> > At this point I started to write this mail. |
42 |
> > |
43 |
> > Before I fscked the sdcard I mounted the FS and tar'ed everything on |
44 |
> > it into a backup file. |
45 |
> > |
46 |
> > The tar process did not return an error. |
47 |
> > |
48 |
> > Since it costs A LOT OF TIME to compile everything from source on a |
49 |
> > 1GHz CPUed embedded system natively - and for abvious different other |
50 |
> > reasons - I am very interested in doing the next steps correctly. |
51 |
> > |
52 |
> > What can I do to eliminate the problem without data loss (best |
53 |
> > case) or to save the most while knowing what and where the corrupted |
54 |
> > data are located on the system? |
55 |
> > |
56 |
> > Thank you very much in advance for any help! |
57 |
> > |
58 |
> |
59 |
> I'm not really sure how to fix the corrupt fs, but don't forget to backup |
60 |
> the whole disk using dd |
61 |
> |
62 |
> Rgds, |
63 |
> -- |
64 |
|
65 |
Currently doing exactly this... |
66 |
|
67 |
mcc |