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] Need help: Filesystem (ext4) corrupted!
Date: Mon, 2 Sep 2013 18:41:34 +0200	[thread overview]
Message-ID: <20130902164134.GB3446@solfire> (raw)
In-Reply-To: <CAA2qdGV1DWwU_XcbEzgUQ7CRft2EdKtR8_iva_2pqqTkuUVn-w@mail.gmail.com>

Pandu Poluan <pandu@poluan.info> [13-09-02 18:40]:
> On Sep 2, 2013 11:16 PM, <meino.cramer@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



  reply	other threads:[~2013-09-02 16:41 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 [this message]
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
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=20130902164134.GB3446@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