kernel messages from INFTL

Andre andre at rocklandocean.com
Wed Jun 22 18:59:36 EDT 2005


> INFTL: inftlcore.c $Revision: 1.18 $, inftlmount.c $Revision: 1.16 $
> INFTL: corrupt block 10588 in chain 10588, chain length 0, erase mark
> 0x0? INFTL: formatting chain at block 10588
> INFTL: formatting block 10588
> INFTL: error while formatting block 10588
> INFTL: corrupt block 15274 in chain 15274, chain length 0, erase mark
> 0x0? INFTL: formatting chain at block 15274
> INFTL: formatting block 15274
> INFTL: error while formatting block 15274
> INFTL: corrupt block 21286 in chain 21286, chain length 0, erase mark
> 0x0? INFTL: formatting chain at block 21286
> INFTL: formatting block 21286
> INFTL: error while formatting block 21286
> INFTL: corrupt block 24574 in chain 24574, chain length 0, erase mark
> 0xffff?
> INFTL: formatting chain at block 24574
> INFTL: formatting block 24574
> INFTL: corrupt block 24575 in chain 24575, chain length 0, erase mark
> 0xffff?
> INFTL: formatting chain at block 24575
> INFTL: formatting block 24575
>  inftla: inftla1

Turns out that I can't boot my system anymore with the diskonchip memory
range enabled in the BIOS. Somehow mtd did something to the boot sector on
the doc2000. Upon inspecting the diskonchip2000 with m-sys dos utilities it
turns out that the bad block table info cannot be found anymore, and all
this time I assumed that the inftl mount operation would be non-destructive.
Can one of you guru's please advise how to proceed from here? Is my doc now
hosed?

Andre







More information about the linux-mtd mailing list