Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!orc!inews!iwarp.intel.com!psueea!parsely!agora!billsey From: billsey@agora.uucp (Bill Seymour) Newsgroups: comp.sys.amiga Subject: Re: help my hard drive & diDiskSalv problems Keywords: dh1: not a dos drive disksalv headonfire Message-ID: <1990Sep11.163152.8078@agora.uucp> Date: 11 Sep 90 16:31:52 GMT References: <14249@cbmvax.commodore.com> <1990Sep8.192254.5960@agora.uucp> <1990Sep10.164805.23863@cbnews.att.com> Distribution: na Organization: Open Communication Forum Lines: 51 In article <1990Sep10.164805.23863@cbnews.att.com> itch@cbnews.att.com (richard.m.brack) writes: :In article <1990Sep8.192254.5960@agora.uucp>, billsey@agora.uucp (Bill Seymour) writes: :> 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? You're certainly running the risk of having the same problem if you only did a 'Zero' of that partition. I've found that the best (or at least easiest) way to check the partition after Zeroing is to go ahead and do a Format from AmigaDOS. This will read and write each block on the partition and pretty much assure you that you don't have a grown error waiting to bite you. If format hangs or aborts somewhere on the partition, it's an indication that you should go ahead and backup the whole drive then do a low level format with bad block mapping turned on. If your problem is termination/cabling related, the errors will, in most cases, be recoverable. Just click on 'Retry' when you see an error. The risk you run there is during a write, some corrupted data during a read usually doesn't hurt worse than a crash, corrupted data during a write will leave you with something on the drive that you don't want. :-{ :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 } :{ \/\/ /^\ } -- -Bill Seymour ...tektronix!reed!percival!agora!billsey ============================================================================= Bejed, Inc. NES, Inc. Northwest Amiga Group At Home Sometimes (503) 281-8153 (503) 246-9311 (503) 656-7393 BBS (503) 640-0842