Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-picayune.mit.edu!news
From: athame@athena.mit.edu (Dirk Karis)
Newsgroups: comp.sys.next
Subject: Bad Blocks on Optical
Message-ID: <1991Apr16.181002.13073@athena.mit.edu>
Date: 16 Apr 91 18:10:02 GMT
Sender: news@athena.mit.edu (News system)
Organization: Massachusetts Institute of Technology
Lines: 15

My optical drive (from the businessland firesale) succumbed to the spinup/
spindown syndrome due to dust yesterday.  A quick cleaning solved the
hardware problem, but the disk that was in the the drive got munged.
Running fsck as root cleaned up all of those except for about ten
unreadable blocks, which show up every time I repeat the fsck -- it is
apparently not remapping them.  Short of reinitalizing t(I don't have
a backup of this disk; it's where I keep all the stuff i download from
various archive sites, so it could be recreated but its nearly 200 megs), I
can't find any way to remap the bad sectors. The closest I can come is
the 'bad' command to 'disk' which allows you to view and edit the bad
block table but there's no documentation on what all the numbers in it
mean that I can find. Any help would be greatly appreciated.

Dirk Karis
athame@athena.mit.edu