Greetings,
I'm not fully clued in on the on chip data format of the nftl, but I wonder if
running something like badblocks -w /dev/nftla1 >badlist then mke2fs -l badlist
might make things OK on a damaged chip (as long as the LinuxBIOS and kernel area
happens to be error free)?
For the LinuxBIOS and kernel areas, a simple minded approach like checksum each
block, and on failure, skip it might allow a successful boot as long as no new
blocks go bad after loading the image.
G'day,
sjames
Quoting Ronald G Minnich <[EMAIL PROTECTED]>:
> On Fri, 24 Aug 2001, Nikolai Vladychevski wrote:
>
> > "DO NOT EVER USE THE nftl_format UTILITY WITHOUT FIRST SEEKING ADVICE
> > ON THE MAILING LIST. It will erase all blocks on the device,
> > potentially losing the factory-programmed information about bad
> > blocks. (Someone really ought to fix it one of these days - ed)"
>
> yow! we've never seen this problem.
>
> Steve James probably can say more than I can. But in a year of doing
> this
> I haven't lost a single chip.
>
>
> uh oh.
>
> ron
>
-------------------------steven james, director of research, linux labs
LinuxBIOS Cluster Solutions 230 peachtree st nw ste 701
High-Speed Colocation, Hosting, atlanta.ga.us 30303
Web Design, Linux Hardware, http://www.linuxlabs.com
Development & Support Since 1995 404.577.7747 fax 404.577.7743
-----------------------------------------------------------------------
