From: Lars Michael <lh_post@yahoo.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: mount ubi volume fails: No such device
Date: Fri, 18 Feb 2011 02:57:38 -0800 (PST) [thread overview]
Message-ID: <664335.29092.qm@web30201.mail.mud.yahoo.com> (raw)
--- On Mon, 14/2/11, Lars Michael <lh_post@yahoo.com> wrote:
> Unfortunately, booting Linux the NAND flash is now detected
> bad, so I do not have an mtd1! what is the best way to try
> to recover? I do not understand how the flash can suddenly
> become bad!
>
> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron
> NAND 256MiB 3,3V 16-bit)
> Bad block table not found for chip 0
> Bad block table not found for chip 0
> Scanning device for bad blocks
> Bad eraseblock 0 at 0x000000000000
> Bad eraseblock 1 at 0x000000020000
> Bad eraseblock 2 at 0x000000040000
> Bad eraseblock 3 at 0x000000060000
> Bad eraseblock 4 at 0x000000080000
> Bad eraseblock 5 at 0x0000000a0000
> Bad eraseblock 6 at 0x0000000c0000
> <cut>
> Bad eraseblock 2046 at 0x00000ffc0000
> Bad eraseblock 2047 at 0x00000ffe0000
> No space left to write bad block table
> fsl_nfc: NAND Flash not found !
> m25p80 spi1.1: at26df081a (1024 Kbytes)
> Creating 1 MTD partitions on "Atmel at26df081a SPI Flash
> chip":
> 0x000000000000-0x000000100000 : "at26df081a"
> DSPI: Coldfire master initialized
> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
>
I try to diagnose the flash from U-Boot. When I e.g. try to read from the
flash I get:
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? At one moment in Linux the device
just had a few bad blocks and after a reboot, all went bad. I am really
worried about this issue!
Do I need to replace the device?
Any comments on this is appreciated.
Thanks and regards,
- Lars
next reply other threads:[~2011-02-18 10:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 10:57 Lars Michael [this message]
2011-02-25 10:45 ` mount ubi volume fails: No such device Artem Bityutskiy
2011-02-28 8:49 ` Lars Michael
-- 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=664335.29092.qm@web30201.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).