Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!ernie.viewlogic.com!greg
From: greg@suntan.viewlogic.com (Gregory Larkin)
Newsgroups: comp.os.minix
Subject: Question about readall(1)
Message-ID: <1991Mar14.220659.6704@viewlogic.com>
Date: 14 Mar 91 22:06:59 GMT
Sender: news@viewlogic.com (News Administrator)
Organization: Viewlogic Systems, Inc., Marlboro, MA
Lines: 40
Originator: greg@mobius


Hi all, 

I am using readall(1) in 1.5 to check my disk for bad
blocks.  When I used to do this with the V1.3 readall,
it used to stop for a bit when it hit a bad block and
print a message like:

Unrecoverable disk error on device 3/6, block 12000

I would then record all of these block numbers and 
feed them into badblocks(1).  No problem.

Now, it seems that the V1.5 readall just hangs on the
bad block and doesn't print any error.  Sometimes it
will stop for a few minutes, other times longer. It
doesn't print any diagnostic message, so I can't tell
what block it couldn't seek to.  That message comes
from the FS, anyway, so I'm not sure what the problem
is.

How can I rectify this situation permanently?  Should
the disk be low-level formatted and update the bad
track table?  This is getting to be more of a headache
and I'm worried that I'm going to trash the filesystem
again (for the 4th time!!)  

That would be a bad thing!
(BTW, the disk is type 3, 32 meg, 6 heads, 17 secs/trk,
it is installed as the 2nd physical drive in the system;
it is all partitioned as /dev/hd6)

Thanks for any help with this,


-- 
Greg Larkin (ASIC Engineer)|"This is a fragile ball we are living on; 
Viewlogic Systems, Inc.    |it's a miracle and we are destroying it.."
293 Boston Post Road West  |Peter Garrett, Midnight Oil               
Marlboro, MA 01752  (greg@Viewlogic.COM)