From: "Ivan Li" <lijinlei1@163.com>
To: "Ivan Li" <lijinlei1@163.com>, <linux-mtd@lists.infradead.org>
Subject: Re: Error creating FAT32 over Nand flash
Date: Tue, 25 Aug 2009 22:21:41 +0800 [thread overview]
Message-ID: <D6830EA55F9F4A9FBCD742B09BE98D9F@ivan> (raw)
In-Reply-To: 6CF41D77BA9F4BC5856D0031BA902A85@ivan
Some progress for it: I found the sector number mentioned in error message resides in BAD block.
Is there any fix for that?
----- Original Message -----
From: "Ivan Li" <lijinlei1@163.com>
To: <linux-mtd@lists.infradead.org>
Sent: Tuesday, August 25, 2009 9:35 PM
Subject: Error creating FAT32 over Nand flash
> Hi guys,
>
> I have some problems with creating FAT32 fs over nand flash.
> I created FAT32 fs over nand flash with below command:
>> flash_eraseall /dev/mtdblock6
>> mkdosfs -v -F 32 /dev/mtdblock6
> mkdosfs 3.0.2 (28 Feb 2009)
> unable to get drive geometry, using default 255/63
> /dev/mtdblock6 has 255 heads and 63 sectors per track,
> logical sector size is 512,
> using 0xf8 media descriptor, with 638976 sectors;
> file system has 2 32-bit FATs and 8 sectors per cluster.
> FAT size is 623 sectors, and provides 79712 clusters.
>
> with USB mass storage gadget I exported this FAT partition to WinXP. When I tried to copy some files into it, I got errors both on WinXP and Linux console:
> In WinXP I got an error dialog, say "Can't copy ****, data error (CRC error).
> In serial console I got:
> end_request: I/O error, dev mtdblock6, sector 77584
> end_request: I/O error, dev mtdblock6, sector 77568
> Buffer I/O error on device mtdblock6, logical block 9696
> lost page write due to I/O error on mtdblock6
> end_request: I/O error, dev mtdblock6, sector 77576
> Buffer I/O error on device mtdblock6, logical block 9697
> lost page write due to I/O error on mtdblock6
>
> I don't know if FAT32 can't handle bad blocks correctly, or something else.
> Any ideas?
>
> The Nand Flash I am using is Samsung K9F4G08U0A, (512M = 4096 blocks, 1 block = 64 pages, 1 page = 2048 bytes, spare area = 64 bytes.)
>
> Kernel configuration:
> CONFIG_BLOCK, CONFIG_MTD, CONFIG_MTD_PARTITIONS, CONFIG_MTD_CHAR, CONFIG_MTD_BLKDEVS, CONFIG_MTD_BLOCK, CONFIG_MTD_NAND...
>
> Thanks in advance.
>
> Ivan
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2009-08-25 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 13:35 Error creating FAT32 over Nand flash Ivan Li
2009-08-25 14:21 ` Ivan Li [this message]
2009-08-25 14:34 ` Artem Bityutskiy
2009-08-25 14:42 ` Eirik Aanonsen
2009-08-25 14:56 ` Matthieu CASTET
2009-08-30 8:14 ` Ivan Li
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=D6830EA55F9F4A9FBCD742B09BE98D9F@ivan \
--to=lijinlei1@163.com \
--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