public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Andrew Tierney <cybergibbons@cybergibbons.com>,
	Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	David Gstir <david@sigma-star.at>
Subject: Re: UBIFS recovery/forensics tools
Date: Sun, 27 Sep 2015 10:47:53 +0200	[thread overview]
Message-ID: <5607AD39.60305@nod.at> (raw)
In-Reply-To: <CAK__sc7xduxq62DVw6fQeNZtXeYbzDmmjw3ms2b8ZgF96j6bhQ@mail.gmail.com>

Am 27.09.2015 um 10:37 schrieb Andrew Tierney:
> I suspect a fsck utility will work quite well for a number of these.
> 
> I guess the real issue is that as soon as any piece of data deviates
> from the norm, current tools fall over rather than attempting to
> recover. ubi_reader has verbose output that allows some degree of
> tweaking, but it can still be awkward.
> 
> The current issue I am working on is that I have one image with two
> volumes contained within. The first volume can be recovered fine, but
> the second starts walking the index, reads a common header, an ino,
> and then stops. I can observe significant data in the remainder of the
> file. There is no other location on the system for a root directory,
> so I suspect that the index is being misread. I don't yet know enough
> about UBIFS to describe the issue better.

Can you share the image?

I hope I have something sane to release soon.
...being still busy with rebasing my preliminary tool to Yang's tree
and found some issues.

Thanks,
//richard

  reply	other threads:[~2015-09-27  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25  9:29 UBIFS recovery/forensics tools Andrew Tierney
2015-09-25 10:26 ` Richard Weinberger
2015-09-27  2:27   ` Dongsheng Yang
2015-09-27  8:37     ` Andrew Tierney
2015-09-27  8:47       ` Richard Weinberger [this message]
2015-09-27  9:50         ` Andrew Tierney

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=5607AD39.60305@nod.at \
    --to=richard@nod.at \
    --cc=cybergibbons@cybergibbons.com \
    --cc=david@sigma-star.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=yangds.fnst@cn.fujitsu.com \
    /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