From: Conrad Steenberg <conrad@hep.caltech.edu>
To: linux-mtd@lists.infradead.org
Subject: Re: MTD/DOC2000 question
Date: 24 Jul 2002 15:25:10 -0700 [thread overview]
Message-ID: <1027549510.3366.9.camel@heppc22.cithep.caltech.edu> (raw)
In-Reply-To: <1027488370.4105.7.camel@Tafelberg>
Hi
OK, let me reply to myself, since others have asked this question on
various lists, but the answer never seems to get posted :-)
To get the DOC to work if you get the below messages while creating a
filesystem, do the following:
1. nftl_format /dev/nftla
2. Reboot the device so that the bad "blocks" marked in the above
process are detected.
3. fdisk /dev/nftla and create the partitions you want
4. Reboot again so that the partitions can be properly detected (in the
old days exiting fdisk used to warn that this needs to be done)
5. Create the filesystem using mkfs.jffs2, mke2fs etc.
Cheers!
Conrad
On Tue, 2002-07-23 at 22:26, Conrad Steenberg wrote:
> Hi
>
> I'm trying to create a filesystem on a 72M DOC2000 (Netier XL1000), and
> get up to creating a partition (/dev/nftla1). This is with Bering-rc3.
>
> When I try mke2fs /dev/nftla1, the following gets reported:
>
> NFTL_writeblock(): Cannot find block to write to
> end_request; I/O error, dev 5d:01 (unknown) sector XXXXX
> Argh! No free blocks found LastFreeEUN = 4603, FirstEUN = 3
> No Virtual Unit Chains available for folding. Failing request
>
> The device was formatted with nftl_format first.
>
> Any ideas?
>
> Cheers!
>
> Conrad
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
--
*-----------------------------------------*
| Conrad Steenberg |
| Caltech, Mail Code 356-48 |
| Pasadena, CA, 91125 |
| e-mail: conrad@hep.caltech.edu |
| Tel: (626) 395-8758 |
*-----------------------------------------*
prev parent reply other threads:[~2002-07-24 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 5:26 MTD/DOC2000 question Conrad Steenberg
2002-07-24 22:25 ` Conrad Steenberg [this message]
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=1027549510.3366.9.camel@heppc22.cithep.caltech.edu \
--to=conrad@hep.caltech.edu \
--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