Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!rex!ukma!tut.cis.ohio-state.edu!ucbvax!DOCKMASTER.NCSC.MIL!TMPLee
From: TMPLee@DOCKMASTER.NCSC.MIL
Newsgroups: comp.sys.apple
Subject: What to do about a bad block
Message-ID: <890413062835.131220@DOCKMASTER.ARPA>
Date: 13 Apr 89 06:28:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 25

I recently got a ProDos "DISK I/O" error when downloading a file with
kermit.  The file looks like it got saved OK.  (I can read it all and it
all seems to be there.)  Just to be safe I decided to run the Finder's
"verify volume" on my harddrive.  It told me that only one block,
#16384, was bad.  (The drive is a 40Meg Everex set up as a 32Meg volume
under P16 but I'm now running GS/OS -- I haven't had the courage to dump
the whole thing and reformat/partition it to use all 40M) Soooooo, four
questions --

a) is there any easy way of finding out what file and/or directory 16384
is in, or if it might in fact be unused?  (note that 16384 = 2**14,
which seems an interesting coincidence.)

b) if it is unused, or even if not, how does one go about marking it as
a bad block?

c) what is the best set of hard drive utilities for dealing with such a
problem?  My guess is the ones that come with ProSel but I'll ask again;
now that ProSel-16 is out and is reported to have selective
backup/restore I guess its time to get it.

d) does ProDos do a read-after-write to verify that what it writes
actually gets written correctly?

TMPLee@Dockmaster.ncsc.mil