home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!uunet.ca!geac!r-node!marc
- From: marc@r-node.pci.on.ca (Marc G Fournier)
- Subject: Re: HD: write_intr errors during SLS install
- References: <C0BEIs.8Bt@unix.portal.com> <1993Jan7.175800.1813@sun1.ruf.uni-freiburg.de> <G2K0KHT@minnie.zdv.uni-mainz.de>
- Organization: R-node Public Access Unix - 1 416 249 5366
- Date: Tue, 12 Jan 1993 07:49:28 GMT
- Message-ID: <1993Jan12.074928.17167@r-node.pci.on.ca>
- Lines: 24
-
- In article <G2K0KHT@minnie.zdv.uni-mainz.de> ckurs-2@orville.uni-mainz.de (Dominik Kubla) writes:
- >I experienced the same and called for suggestions to summarize them for the faq,
- >but for no nothing arrived in my post box :-(
- >
- >But i solved the problem for my RLL drive:
- >1. I called the routines for low level formatting (in my case the controller
- >bios :-) but i think something like the Ontrack disk manager might do it as well)
- >2. then i entered the bad block list provided by the manufacturer.
- >3. i reformatted the drive and the controller managed to skip the bad spots ...
- >
- >There was also an earlier posting (in November i think), which provided an awk
- >script to convert the bad block list to the format needed by mk(e)fs, but i was
- >not able to retrieve that article ...
- >
-
- I think (am almost positive) this is in the FAQ. If you add the
- -c qualifier to both mk(e)fs, it will test for and mark badblocks.
-
- marc
- --
- Marc G. Fournier | R-node Public Access Unix running Linux 0.99p1
- Etobicoke, Ontario | 416-249-5366 24hrs 7 days/week network email
- voice: 249-4230 | shell accounts available 2500+ newsgroups FREE
- marc@r-node.pci.on.ca | Telebit WorldBlazer/SupraModem2400/Cardinal 2400
-