NFTL not recognizing disk on chip in some cases

Henrik Nordstrom hno at
Wed Jan 29 12:05:31 EST 2003

ons 2003-01-29 klockan 17.42 skrev Raphael Hertzog:

> Unless the bad things are irreversible this should not be the case.
> AFAIR I always took care to remove the module before formating.
> And it doesn't explain why I have the problem when I copy a set of files
> and why I doesn't have it with another set of files. Even stranger when
> I first copy the good set of files, then umount, remount, remove the
> good set of files and copy the problematic set of files then it's ok.
> But if I copy the problematic set of files directly during the first
> mount after the partitioning/formating then I have the problem exposed
> in my previous mail.

Well.. who knows what happens if the NFTL table gets corrupted somehow
due to conflict between the NFTL driver and nftl_format. I would not at
all be supriced if in such case it behaves quite different depending on
which fileset you copy first/how as this has impact on in which order
the blocks is beeing used by the filesystem.

But if you are sure the NFTL driver was removed from the system when you
ran nftl_format then it must be something else..

As of yet I have only formatted our DOC chips using the DFORMAT tool.
Feels like a safer approach. And with the current GRUB patch you should
be able to install GRUB direcly using DFORMAT 5.X as a binary partition

Note: For various reaosns (mainly lack of time and lab equipment to try
out a new scheme) we are still using the msys drivers and a normal grub
loading from the doc via the msys BIOS. Hope to switch to native
Linux/GRUB drivers shortly.

Henrik Nordstrom <hno at>
MARA Systems AB

More information about the linux-mtd mailing list