From: Artem Bityutskiy <dedekind@infradead.org>
To: Oren <oren_s3@VERIFONE.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiattach problem
Date: Tue, 07 Jul 2009 18:45:42 +0300 [thread overview]
Message-ID: <1246981542.20721.327.camel@localhost.localdomain> (raw)
In-Reply-To: <1246981097.2208.19.camel@tlvorens3lnx>
On Tue, 2009-07-07 at 18:38 +0300, Oren wrote:
> cp /mnt/pc/Linux_2_6_27_old/mtd-utils/ubi_format.sh .
> ~ # chmod 777 ubi_format.sh
> ~ # ./ubi_format.sh
> cat /proc/mtd
> dev: size erasesize name
> mtd0: 01000000 00020000 "NAND-block1"
> mtd1: 01e00000 00020000 "jffs2"
> mtd2: 05200000 00020000 "NAND-block2"
> ubinfo
> UBI version: 1
> Count of UBI devices: 0
> UBI control device major/minor: 10:63
> ubiformat /dev/mtd0 -s 2048 -f ubi_ncomp.img
> ubiformat: mtd0 (nand), size 16777216 by[42949488.970000] Uncorrectable
> ECC error!!!! :f0000fff
> tes (16.0 MiB), 128 eraseblocks [42949488.980000] Uncorrectable ECC
> error!!!! :f0000fff
> of 131072 bytes (128.0 KiB), min[42949488.990000] Uncorrectable ECC
> error!!!! :f0000fff
> . I/O size 2048 bytes
> libscan: [42949489.000000] Uncorrectable ECC error!!!! :f0000fff
> start scanning eraseblocks 0-128[42949489.010000] Uncorrectable ECC
> error!!!! :f0000fff
>
> libscan: scanning eraseblock 0[42949489.010000] Uncorrectable ECC
> error!!!! :f0000fff
> : empty
> libscan: scanning eraseblock 1: empty
> libscan: scanning eraseblock 2: empty
> libscan: scanning eraseblock 3: empty
> libscan: scanning eraseblock 4: empty
> libscan: scanning eraseblock 5: empty
> libscan: scanning eraseblock 6: empty
> libscan: scanning eraseblock 7: empty
> libscan: scanning eraseblock 8: empty
> libscan: scanning eraseblock 9: empty
> libscan: scanning eraseblock 10: empty
> libscan: scanning eraseblock 11: empty
> libscan: scanning eraseblock 12: empty
> libscan:[42949489.060000] Uncorrectable ECC error!!!! :f0000fff
> scanning eraseblock 13: empty
> [42949489.070000] Uncorrectable ECC error!!!! :f0000fff
> libscan: scanning eraseblock 14:[42949489.080000] Uncorrectable ECC
> error!!!! :f0000fff
> empty
> libscan: scanning eraseb[42949489.090000] Uncorrectable ECC
> error!!!! :f0000fff
> lock 15: empty
> libscan: scannin[42949489.090000] Uncorrectable ECC
> error!!!! :f0000fff
> g eraseblock 16: empty
> libscan:[42949489.100000] Uncorrectable ECC error!!!! :f0000fff
> scanning eraseblock 17: empty
> libscan: scanning eraseblock 18: empty
> libscan: scanning eraseblock 19: empty
> libscan: scanning eraseblock 20: empty
> libscan: scanning eraseblock 21: empty
...
> [42949490.870000] UBI: logical eraseblock size: 126976 bytes
> [42949490.880000] UBI: smallest flash I/O unit: 2048
> [42949490.880000] UBI: VID header offset: 2048 (aligned 2048)
> [42949490.890000] UBI: data offset: 4096
> [42949490.900000] UBI DBG (pid 90): ubi_scan: process PEB 0
> [42949490.910000] UBI DBG (pid 90): process_eb: scan PEB 0
> [42949490.910000] UBI DBG (pid 90): ubi_io_read: fixable bit-flip
> detected at PEB 0
> [42949490.920000] UBI warning: ubi_io_read_ec_hdr: bad magic number at
> PEB 0: 15400000 instead of 55424923
> [42949490.930000] Erase counter header dump:
> [42949490.930000] magic 0x15400000
> [42949490.940000] version 0
> [42949490.940000] ec 0
> [42949490.940000] vid_hdr_offset 0
> [42949490.950000] data_offset 0
> [42949490.950000] hdr_crc 0x000000
> [42949490.950000] erase counter header hexdump:
> [42949490.960000] 00000000: 15 40 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 .@..............................
> [42949490.970000] 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 ................................
OK, I admit UBI should print a better error message when it finds
nothing but rubbish on flash. I'll try to implement this.
But you probably now noticed that UBI could not find a valid nodes, so
something is wrong with your flash. You should check your driver.
:-)
I suggest you nandtests:
http://git.infradead.org/users/ahunter/nand-tests.git
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-07-07 15:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <baa101c9fe67$d7b31f0a$b65b1ec0@verifone.com>
2009-07-07 6:25 ` ubiattach problem Artem Bityutskiy
2009-07-07 10:32 ` Oren
2009-07-07 10:42 ` Artem Bityutskiy
2009-07-07 12:08 ` Oren
2009-07-07 12:51 ` Artem Bityutskiy
2009-07-07 13:21 ` Oren
2009-07-07 13:28 ` Artem Bityutskiy
2009-07-07 14:08 ` Oren
2009-07-07 14:19 ` Artem Bityutskiy
2009-07-07 14:38 ` Artem Bityutskiy
2009-07-07 14:49 ` Oren
2009-07-07 14:53 ` Artem Bityutskiy
2009-07-07 15:30 ` Oren
2009-07-07 15:38 ` Oren
2009-07-07 15:45 ` Artem Bityutskiy [this message]
2009-07-12 7:19 ` Oren Sokolowsky
2009-07-12 14:06 ` Artem Bityutskiy
2009-07-27 12:54 ` Oren
2009-08-09 4:36 ` Artem Bityutskiy
2009-07-06 13:50 Oren
2009-07-06 14:05 ` Artem Bityutskiy
2011-09-09 9:53 ` marco
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=1246981542.20721.327.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=oren_s3@VERIFONE.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