public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Henrik Nordstrom <hno@marasystems.com>
To: Raphael Hertzog <eng@eipm.ch>
Cc: linux-mtd@lists.infradead.org
Subject: Re: NFTL not recognizing disk on chip in some cases
Date: 29 Jan 2003 15:48:29 +0100	[thread overview]
Message-ID: <1043851709.11449.118.camel@henrik.marasystems.com> (raw)
In-Reply-To: <1043844420.555.111.camel@localhost>

>From what I recall you must not have the NFTL driver loaded while
running nftl_format.. if the NTFL driver is loaded then I think bad
things may happen such as those you describe.

Regards
Henrik


ons 2003-01-29 klockan 13.47 skrev Raphael Hertzog:
> Hi,
> 
> I followed the instructions given here :
> http://lists.infradead.org/pipermail/linux-mtd/2002-October/006166.html
> 
> I used the second set of instructions (the one for 2.4.18) since I'm
> running an unmodified 2.4.19 kernel.
> 
> After having successfully created the filesystem on the disk on chip (I
> can mount it and work with it), I reboot and then the chip is no more
> recognized. The error happens in the NFTL module, it displays :
> 
> NFTL Driver: nftlcore.c $Revision: 1.85$ nftlmount.c $Revision: 1.25$
> NFTL Media Headers at 0x18000 and 0x6cc000 disagree
> Could not find valid boot record
> Could not mount NFTL device
> 
> Now if I relaunch nftl_format a second time it may find "bad blocks"
> which didn't exist the first time. After that the chip is usually again
> recognized ... I can reproduce that with different disk on chip (this
> does probably mean that it's not the disk on chip that is on fault).
> 
> After more tries, it appears that the disk on chip is recognized after
> partitioning and formating ... but the problems appears once I copy a
> specific set of files on the disk on chip (it's not reproducible with
> any set of files) and umount the DOC (and try to reload the nftl
> module).
> 
> Any idea of what can go wrong ?
> 
> Regards,
-- 
Henrik Nordstrom <hno@marasystems.com>
MARA Systems AB

  reply	other threads:[~2003-01-29 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 12:47 NFTL not recognizing disk on chip in some cases Raphael Hertzog
2003-01-29 14:48 ` Henrik Nordstrom [this message]
2003-01-29 16:42   ` Raphael Hertzog
2003-01-29 17:05     ` Henrik Nordstrom
2003-01-29 18:30     ` Mark Meade
2003-01-29 22:41     ` David Woodhouse
2003-01-30  8:05       ` Raphael Hertzog
2003-01-30  8:19         ` David Woodhouse
2003-01-30 10:56           ` Raphael Hertzog
2003-01-30 10:14         ` Raphael Hertzog

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=1043851709.11449.118.camel@henrik.marasystems.com \
    --to=hno@marasystems.com \
    --cc=eng@eipm.ch \
    --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