From: "Matt Garratt" <m.garratt@adfa.edu.au>
To: <linux-mtd@lists.infradead.org>
Subject: Bad black table not found
Date: Mon, 7 Mar 2005 23:07:27 +1100 [thread overview]
Message-ID: <HMEGLJJFEGIOMNFLAPOFEEAMCEAA.m.garratt@adfa.edu.au> (raw)
When my computer boots, I get the following messages that concern me
regarding the DOC2000. Are these something I should worry about and if so,
is there anything that can be done to fix?
Bad Block Table not found for chip 0
Bad Block Table not found for chip 0
INFTL: corrupt block 4087 in chain 4087, chain length 0, erase mark 0x0?
INFTL: formating chain at block 4087
INFTL: formatting block 4087
nand_erase: Failed erase, page 0x0001fee0
INFTL: error while formatting block 4087
INFTL: cannot calculate a geometry to match size of 0x6d5c0
INFTL: using C:999 H:16 S:28 (==0x6d440 sects)
It appears that the BBT is missing or something, which is odd since I have
reconstructed using the M-Systems utilities
(dformat /win:d000 /USELOG:BBT.txt)
Any advice would be much appreciated.
I am using a 2.6.9 kernel patched from cvs.
Matt
next reply other threads:[~2005-03-07 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 12:07 Matt Garratt [this message]
2005-03-14 21:11 ` Bad black table not found Dan Brown
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=HMEGLJJFEGIOMNFLAPOFEEAMCEAA.m.garratt@adfa.edu.au \
--to=m.garratt@adfa.edu.au \
--cc=linux-mtd@lists.infradead.org \
/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