From: Juergen Beisert <jbeisert@eurodsn.de>
To: <linux-mtd@lists.infradead.org>
Subject: Problems using JFFS2 on my Samsung NAND chip
Date: Tue, 23 Mar 2004 12:55:52 +0100 [thread overview]
Message-ID: <200403231255.52627.jbeisert@eurodsn.de> (raw)
Hello group.
I have trouble using a JFFS2 filesystem on my NAND chip.
I have tried:
emb> eraseall --jffs2 /dev/mtd/0
Last ouput of this command is:
Erasing 16 Kibyte @ ffc000 -- 99 % complete. Cleanmarker written at ffc000.
emb> mount -t jffs2 /dev/mtdblock/0 /mnt
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 0, bad_blocks 0, c->nr_blocks 1024
mount: Mounting /dev/mtdblock/0 on /mnt failed: Invalid argument
My NAND is a Samsung K9F2808U0B chip. I found a small discussion in february
2004 in this list about this chip ("JFFS2 NAND support - Mount failure on
"good" filesystem" by Joshua Wise).
So I have updated my mtd sources but I get the same results as before.
Any hints?
JB
next reply other threads:[~2004-03-23 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 11:55 Juergen Beisert [this message]
2004-03-23 12:09 ` Problems using JFFS2 on my Samsung NAND chip Juergen Beisert
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=200403231255.52627.jbeisert@eurodsn.de \
--to=jbeisert@eurodsn.de \
--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