Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!att!cbnews!itch
From: itch@cbnews.att.com (richard.m.brack)
Newsgroups: comp.sys.amiga
Subject: Re: help my hard drive & diDiskSalv problems
Keywords: dh1: not a dos drive disksalv headonfire
Message-ID: <1990Sep10.164805.23863@cbnews.att.com>
Date: 10 Sep 90 16:48:05 GMT
References: <1990Aug30.191714.10892@cbnews.att.com> <14249@cbmvax.commodore.com> <1990Sep8.192254.5960@agora.uucp>
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 44

In article <1990Sep8.192254.5960@agora.uucp>, billsey@agora.uucp (Bill Seymour) writes:
> In article <14249@cbmvax.commodore.com> daveh@cbmvax (Dave Haynie) writes:
> >In article <1990Aug30.191714.10892@cbnews.att.com> itch@cbnews.att.com (richard.m.brack) writes:
> >
> >>DiskSalv 1.42 problems:
> >>   So I used DiskSalv 1.42 to recover my files from dh1: to floppies.
> >>   It took me about 5 trys to get disksalv to work.  
> >>   It would start counting blocks, and then just hang.  
> 
> 	This isn't a problem with Disksalv, it's a problem with his HD
> combination...

Thanks for your help, guys.  In the mean time I have gotten my drive up
and running.  As I stated I did finally get DiskSalv to work.  I then
zeroed my dh1: partition and copied the disksalv'ed stuff back on.
It has been up for about a week with no problems.

> 	Doing a 'zero' of the offending partition would certainly
> work if his problem were only and AmigaDOS bad block. 'Zero' from
> within SupraFormat is the same as 'Format drive foo: name FooBar Quick'
> from CLI. The problem is that as soon as he tried writing again
> to that bad block, he'd start hanging the system just as he was
> during the block mapping that DiskSalv does.
> 	One other thing I just thought of that could be his problem...
> If he's got termination problems on his SCSI bus, he could be getting
> lots of soft errors which could show as that same type of grown error.
> In that case, zeroing and restoring would work, as long as he fixed
> the cabling/termination problem first.

Are you trying to tell me that my is just sitting around waiting to
crash again?  This is really the only trouble I have had with my drive,
and as I said above, it has been up for a week or so with no problems.
Do you suggest I do more than what I have done?  


Thanks again for listing to my problems.....

RichBrack

-- 
{ the itchman cometh   /-/         _          i don't want to be your angel }
{ itch@cbnews.att.com /-/        _|_|_          i want to be your witch!    }
{ att!cbnews!itch \-\/-/         ( * )tch                 -yello            }
{                  \/\/           /^\                                       }