On Fri, Jul 24, 2009 at 08:53:00AM +0300, Artem Bityutskiy wrote: > On 07/23/2009 09:59 PM, e...@gulp.u--3.com wrote: >> [ 191.690000] UBI error: ubi_io_write: error -5 while writing 512 bytes >> to PEB 4051:512, written 0 bytes >> [ 191.700000] UBI warning: ubi_eba_write_leb: failed to write VID >> header to LEB 2147479551:0, PEB 4051 >> [ 191.710000] UBI warning: ubi_ro_mode: switch to read-only mode >> [ 191.720000] UBI error: autoresize: cannot auto-resize volume 0 > > http://www.linux-mtd.infradead.org/faq/ubi.html#L_subpage_verify_fail
Ah, ok. I did google for that error message but searching for "ubi_io_write: error -5" doesn't yield anything useful for the first screenful of results.. So workaround would be to disable CONFIG_MTD_NAND_VERIFY_WRITE or to follow the "ignore sub pages" entry from the faq... Indeed the latter seems to work, if I give --vid-hdr-offset 2048 option to the ubinize, ubiformat & ubiattach commands. Thanks! Maybe it would be better to disable the verify & subpages combo until the bug is fixed? Especially since it crashes the kernel... Also, ubiformat mentioned 1400+ "bad" eraseblocks, what should I make of that? Is it really failed flash cells, just some blocks reserved for u-boot and stuff, or blocks traumatized from my earlier misadventures with ubiformat parameters? Erno -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
