From: Richard Weinberger <richard@sigma-star.at>
To: Timo Ketola <timo@exertus.fi>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI assert failed in ubi_wl_init
Date: Tue, 13 Feb 2018 13:42:43 +0100 [thread overview]
Message-ID: <63275670.WCUj5TjS3v@blindfold> (raw)
In-Reply-To: <b5eb17b7-14f1-7ec4-a590-d486dd0b89b6@exertus.fi>
Timo,
Am Dienstag, 13. Februar 2018, 12:58:50 CET schrieb Timo Ketola:
> On 13.02.2018 00:49, Richard Weinberger wrote:
> > I meant the image _after_ UBI failed to place the fastmap. :)
>
> Argh, sorry, shame on me.
>
> https://drive.google.com/open?id=1t-auduKG2bwzpzZf09rV4O9F7GUN2viJ
This image contains no fastmap at all.
> https://drive.google.com/open?id=1ahKl8pf3svKQSvz6VQ-7xUQsyfkVuO7k
>
> The first one is taken after the first boot and the second after the
> second boot.
This one a good fastmap (full scan comes to the same result).
The UBIFS seems good but contains no files/dirs.
So, this is not what you have described in your problem report.
Can you please double check?
Thanks,
//richard
--
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y
next prev parent reply other threads:[~2018-02-13 12:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 6:44 UBI assert failed in ubi_wl_init Timo Ketola
2018-02-04 13:44 ` Richard Weinberger
2018-02-05 6:39 ` Timo Ketola
2018-02-12 22:49 ` Richard Weinberger
2018-02-13 11:58 ` Timo Ketola
2018-02-13 12:42 ` Richard Weinberger [this message]
2018-02-13 14:00 ` Timo Ketola
2018-02-18 20:31 ` Richard Weinberger
2018-03-16 13:34 ` Timo Ketola
2018-03-19 7:13 ` Timo Ketola
2018-03-20 22:02 ` Richard Weinberger
2018-03-22 13:57 ` Timo Ketola
2018-03-22 15:05 ` Richard Weinberger
2018-03-22 15:40 ` Timo Ketola
2018-03-22 15:48 ` Richard Weinberger
2018-03-23 9:26 ` Timo Ketola
2018-03-23 9:35 ` Richard Weinberger
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=63275670.WCUj5TjS3v@blindfold \
--to=richard@sigma-star.at \
--cc=linux-mtd@lists.infradead.org \
--cc=timo@exertus.fi \
/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