[comp.sys.amiga] DF1: mechanical problems

gbs@utgpu.UUCP (08/15/87)

My DF1: has been acting strangly lately, not only does it complain
about R/W errors far too frequently, but on occasion I stick a disk
in and it reports it as bad (unformatted) when its not (df0: read it).
There seems to be no good reason or consistancy to its behavior.
Sometimes ejecting and reinserting the disk is all thats needed to get
it read, sometimes it needs to be ignored for an hour.
Is it time to bring it in to a doctor or can I wap it on the side with
a rolled up newspaper ? Has this happened to anyone else, any ideas?

thanks,

-- 
Gideon Sheps
I am not a number ...                             ...I am a free variable !
                                                                  ///
UUCP: {allegra,ihnp4,decvax,pyramid}!utzoo!utgpu!gbs          \\\///
BITNET: gbs@utorgpu         gbs@gpu.utcs.toronto.edu           \\\/

blgardne@esunix.UUCP (Blaine Gardner) (08/17/87)

in article <1987Aug15.045420.1010@gpu.utcs.toronto.edu>, gbs@gpu.utcs.toronto.edu (Gideon Sheps) says:
> My DF1: has been acting strangly lately, not only does it complain
> about R/W errors far too frequently, but on occasion I stick a disk
> in and it reports it as bad (unformatted) when its not (df0: read it).
> There seems to be no good reason or consistancy to its behavior.
> Sometimes ejecting and reinserting the disk is all thats needed to get
> it read, sometimes it needs to be ignored for an hour.
> Is it time to bring it in to a doctor or can I wap it on the side with
> a rolled up newspaper ? Has this happened to anyone else, any ideas?


This is the same kind of problem I've been having. DF0: will not
recognize disks formatted in DF1:, and DF1: will not recognize disks
that have been formatted in DF0:. 
 
This problem showed up after I had taken my external drive over to a
friends house to do some mass copying. I handled the drive carefull of
course, but it must have got bumped just enough to do it in.

The really weird twist in my case is that disks that were formatted
before this problem occured can be read by both drives. Strange!
 
George Robbins suggested that it was indeed an alignment problem, but
that the alignment was still close enough that DF1: could pick up on
on the formatting on some disks.
 
The $64K question now is: Where can I get a 3.5" alignment disk at a
reasonable price? I can take care of the alignment myself, but I need
the alignment disk. Any help here would be greatly appreciated!
-- 
Blaine Gardner @ Evans & Sutherland    540 Arapeen Drive, SLC, Utah 84108
UUCP Address:   {ihnp4,ucbvax,decvax,allegra}!decwrl!esunix!blgardne
Alternates:     {ihnp4,seismo}!utah-cs!utah-gr!uplherc!esunix!blgardne
		seismo!usna!esunix!blgardne