From: Trevor Woolven <trevw@zentropix.com>
To: MTD <mtd@infradead.org>
Subject: Reviving DOCs
Date: Mon, 13 Mar 2000 16:31:13 +0000 [thread overview]
Message-ID: <38CD17D1.8E4447E6@zentropix.com> (raw)
Firstly, thanks to everyone for their help and advice.
Secondly, I appear to have found another way...
nftl_format /dev/mtd0
fdisk /dev/nftla (sometimes a reboot is needed first)
mke2fs /dev/nftla1 (I only create one partition on the DOC at present)
Now, so far this method appears to have revived three DOC2000 devices.
I've got a few more to try yet and so the chicken count hasn't started
but so far so good.
I haven't used docpmap to revive a DOC:
docpmap /br /f:<filename> to get an image of a 'virgin' DOC
docpmap /bw /f:<filename> to write virgin image onto 'broken' DOC
...because I haven't got any 'virgin' devices left (oops!) and I needed
to rebuild a kernel with MSDOS fs support (somewhere to store the image
files) and I couldn't be bothered.
DW's idea of using nanddump needs (I believe) a utility to write the
image back onto the DOC. I've hacked nanddump into nandput but have yet
to try it out. Is it worth it?????
Cheers
Trev. (Much happier now)
--
Trevor Woolven - Director of Customer Applications Engineering
Zentropix Inc - a Lineo company
Tel: +44 (0)1273 234 647 Fax: +44 (0)1273 704 482
Visit http://www.zentropix.com/ for Real Time Linux Tools
Visit http://www.realtimelinux.org/ for Real Time Linux Information
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-03-13 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 16:31 Trevor Woolven [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-13 16:49 Reviving DOCs Oron Ogdan
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=38CD17D1.8E4447E6@zentropix.com \
--to=trevw@zentropix.com \
--cc=mtd@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