home *** CD-ROM | disk | FTP | other *** search
- Organization: Sophomore, Electrical and Computer Engineering, Carnegie Mellon, Pittsburgh, PA
- Path: sparky!uunet!math.fu-berlin.de!ira.uka.de!scsing.switch.ch!univ-lyon1.fr!ghost.dsi.unimi.it!rpi!usc!howland.reston.ans.net!spool.mu.edu!agate!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!cis.ohio-state.edu!news.sei.cmu.edu!bb3.andrew.cmu.edu!crabapple.srv.cs.cmu.edu!andrew.cmu.edu!pw1r+
- Newsgroups: comp.unix.bsd
- Message-ID: <UfNsocy00WBNMAXZhX@andrew.cmu.edu>
- Date: Thu, 28 Jan 1993 02:37:12 -0500
- From: Peter William Wieland <pw1r+@andrew.cmu.edu>
- Subject: [386BSD] Using bad144?
- Lines: 28
-
-
- I'm trying to mark off all of the bad blocks on my MFM drive. The
- installation notes claim that BSD will give me some form of error
- message whenever it trys to write to a bad block, but I haven't seen any
- messages, and I'm almost certain the installation has used the bad areas.
-
- So my question is:
-
- Knowing the bad tracks on my drive (cylinder & head), how do I compute
- the block number(s) that are bad.
-
- For example, if I wanted to mark track 101:4 (cylinder:head) as bad,
- what are the block numbers that I want to feed to bad144.
-
- Or is there a simpler way that I missed. I looked through the FAQ, man
- pages for bad144, fsck, badsect, and checked the installation notes. Is
- there a program which will check my drive for bad blocks and report
- block numbers back to me?
-
- Any help would be appreciated.
- -peter wieland
-
- ****************************************************************************
- None of the ideas expressed above are acutally mine. They are told to
- me by Luthor and Ferdinand, the five inch tall space aliens who live
- under my desk. In return for these ideas, I have given them persmision
- to eat any dust bunnies they may find under there.
- Peter Wieland pw1r+@andrew.cmu.edu dmonger+@cmu.edu
-