Dear List, > I am unable to boot ubifs with the new kernel. I've tried nand-scrub, > and reformatting mtd6 from within a 2.6.37 environment. I get this > error when running ubiformat: > > ubiformat: error!: failed to erase eraseblock 913 > error 5 (Input/output error) > ubiformat: mark it as bad? Continue (yes/no) y > ubiformat: marking block 913 bad > libmtd: error!: MEMSETBADBLOCK ioctl failed for eraseblock 913 (mtd6) > error 22 (Invalid argument) > > I am able to boot jffs2, but I see errors in the console about > unrecoverable errors. Has badblock handling changed in 2.6.37?
I have the same issue on my FR also. The interesting thing I see is, that running nandtest with option to mark the badblocks, the defect eraseblocks are recognised (like 913 in that case) but when i run nandwrite or ubiformat it fails exactly on this block. The same happens also if I do nand-scrub and nand createbbt. Does 2.6.37 use FreeRunnes Bad Block Table? Is there maybe a kernel switch to disable this feature? Regards, Sebastian _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
