ubifs: bad node type (255 but expected 6)

Thomas De Schampheleire patrickdepinguin at gmail.com
Wed Aug 28 09:37:51 EDT 2013


On Wed, Aug 28, 2013 at 2:31 PM, Thomas De Schampheleire
<patrickdepinguin at gmail.com> wrote:
> On Wed, Aug 28, 2013 at 12:36 PM, Mats Kärrman <Mats.Karrman at tritech.se> wrote:
>> Hi Thomas,
>>
>> On Wednesday, August 28, 2013 12:13 PM Thomas De Schampheleire [patrickdepinguin at gmail.com] wrote:
>>> Is this a known problem, fixed in a later release?
>>> Could it be just a bad NAND flash?
>>> Could it be a problem with the underlying MTD driver (or my modification to it)?
>>
>> I would put my money on the MTD driver.
>> Have you tried running the mtd tests (http://www.linux-mtd.infradead.org/doc/general.html#L_mtd_tests)?
>
> Thanks for the tip.
> The readtest went fine, but I'm now getting errors on the pagetest:
>
> [  736.746005] mtd_pagetest: error: verify failed at 0x9ea000
> [  736.814904] mtd_pagetest: error: verify failed at 0x9ea800
> [  736.883804] mtd_pagetest: error: verify failed at 0x9eb000
> [  736.952735] mtd_pagetest: error: verify failed at 0x9eb800
> [...]
>
> I will revert my changes and retest.

Even without my changes, the pagetest fails. Can I safely assume that
pagetest should always work, and that it failing really means a buggy
mtd driver, or can there be other causes?
The current driver is coming from the SoC vendor (Freescale), and in
this 2.6.36.4 kernel release it was not yet accepted upstream (so I'm
still using a patch against vanilla)

Thanks,
Thomas

>
> Best regards,
> Thomas



More information about the linux-mtd mailing list