From: Lars Michael <lh_post@yahoo.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: mount ubi volume fails: No such device
Date: Mon, 28 Feb 2011 00:49:06 -0800 (PST) [thread overview]
Message-ID: <312621.60695.qm@web30207.mail.mud.yahoo.com> (raw)
In-Reply-To: <1298630702.2798.45.camel@localhost>
--- On Fri, 25/2/11, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> From: Artem Bityutskiy <dedekind1@gmail.com>
> Subject: Re: mount ubi volume fails: No such device
> To: "Lars Michael" <lh_post@yahoo.com>
> Cc: linux-mtd@lists.infradead.org
> Date: Friday, 25 February, 2011, 11:45
> On Fri, 2011-02-18 at 02:57 -0800,
> Lars Michael wrote:
> > NAND read: device 0 offset 0x1, size 0xfffffff
> > Skipping bad block 0x00000000
> > Skipping bad block 0x00020000
> > Skipping bad block 0x00040000
> > <cut>
> > Skipping bad block 0x0ffa0000
> > Skipping bad block 0x0ffc0000
> > Skipping bad block 0x0ffe0000
> > NAND read from offset 10000000 failed -22
> > 0 bytes read: ERROR
> > -> nand
> >
> > I am really stuck here, and don't know how to proceed.
> Is it normal that
> > the flash can suddenly go totally bad?
>
> Most likely not. Probably this is due to a bug
> somewhere.
>
Let us assume this is a software problem and that the NAND device is
ok. Note: I did not cycle the power during a flash operation, and I
did not write (e.g. format or erase) the flash prior to it going bad.
Can the bbt somehow be corrupt, reporting all blocks bad even if they
are not?
Is the problem likely to be in the UBI layer or in the NAND driver
(I suspect the first) and how can I troubleshoot this?
Any help is appreciated,
- Lars
next prev parent reply other threads:[~2011-02-28 8:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 10:57 mount ubi volume fails: No such device Lars Michael
2011-02-25 10:45 ` Artem Bityutskiy
2011-02-28 8:49 ` Lars Michael [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-14 10:22 Lars Michael
[not found] <9186EF1D8AB86E40B9C8009D36864D0403CA4342@dhreinsvxb03.messaging.danaherad.com>
2011-02-11 14:21 ` Lars Michael
2011-02-11 14:35 ` Artem Bityutskiy
2011-02-11 14:57 ` Artem Bityutskiy
2011-02-09 12:34 Lars Michael
2011-02-11 14:32 ` Artem Bityutskiy
2011-02-09 8:32 Lars Michael
2011-02-11 14:28 ` Artem Bityutskiy
2011-02-14 8:49 ` Lars Michael
2011-02-14 11:01 ` Artem Bityutskiy
2011-02-14 12:47 ` Lars Michael
2011-02-07 15:05 Lars Michael
2011-02-07 15:27 ` Artem Bityutskiy
2011-01-31 10:35 Lars Michael
2011-02-06 14:19 ` Artem Bityutskiy
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=312621.60695.qm@web30207.mail.mud.yahoo.com \
--to=lh_post@yahoo.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).