Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcnc!ecsvax!unbent
From: unbent@ecsvax.UUCP (Jay F. Rosenberg)
Newsgroups: comp.sys.ibm.pc,comp.sys.misc
Subject: Need info about ST-238 disk, 2070 controller problem
Message-ID: <3155@ecsvax.UUCP>
Date: Fri, 15-May-87 08:59:14 EDT
Article-I.D.: ecsvax.3155
Posted: Fri May 15 08:59:14 1987
Date-Received: Sat, 16-May-87 21:57:09 EDT
Distribution: na
Organization: UNC Chapel Hill
Lines: 28
Keywords: Seagate ST-238 hard disk Adaptek 2070 controller problem
Xref: mnetor comp.sys.ibm.pc:4047 comp.sys.misc:588


	I keep running across references to a mysterious problem involving
Seagate ST-238 hard disks coupled with Adaptek 2070 RLL controllers.  A May
11th Infoworld story spoke of a "25 percent failure rate" and disks
"becoming unusable months after being set up to work with RLL controller
cards".  Since that's precisely the combination I installed in my new clone
last December, this is getting rather disturbing.
	Does anyone out there know what is going on here?  How worried
should I be?  What are the early symptoms?  Is it better to leave the disk
running 24 hours a day (which is what I've been doing for the past 6 months)
or to shut it down each night (which sometimes produced symptoms of
reluctance from the disk upon cold reboot from zero revs, namely "General
Error Reading Disk C; Abort, Retry, Ignore?"  Retry seemed to work, by the
way.)?  How many months do I need to wait before I can be confident that my
configuration is healthy?
	Any information appreciated.  Email and I shall summarize if
appropriate.  (But don't bother to remind me to keep current backups.  I DO, 
and I intend to go on doing so.)  Thanks in advance.


JAY ROSENBERG     Dept. of Philosophy     UNC     Chapel Hill, NC   27514
...{decvax,akgua}!mcnc!ecsvax!unbent         ...tucc!tuccvm!ecsvax!unbent  
   unbent@ecsvax.UUCP      unbent@ecsvax.BITNET      unbent@unc.BITNET      
-- 

JAY ROSENBERG     Dept. of Philosophy     UNC     Chapel Hill, NC   27514
...{decvax,akgua}!mcnc!ecsvax!unbent         ...tucc!tuccvm!ecsvax!unbent  
   unbent@ecsvax.UUCP      unbent@ecsvax.BITNET      unbent@unc.BITNET