Xref: utzoo unix-pc.general:3894 comp.sys.att:7804 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!ingr!b11!elliott From: elliott@b11.ingr.com (Jeff Elliott) Newsgroups: unix-pc.general,comp.sys.att Subject: problem with WD2010 on UNIXPC Keywords: WD2010 Miniscribe 3085 write errors Message-ID: <6216@b11.ingr.com> Date: 17 Oct 89 13:55:14 GMT Organization: Intergraph Corp. Huntsville, AL Lines: 36 Subject: problem with WD2010 and Miniscribe 3085 Newsgroups: unix-pc.general,comp.sys.att Summary: surface test errors galore! References: <22964@cup.portal.com> <2221@ethz.UUCP> <23093@cup.portal.com> In article <23093@cup.portal.com>, thad@cup.portal.com (Thad P Floryan) writes: > ...................................................... As I mentioned, I've > been "away" for awhile and upon return discovered email indicating that seven > (7) of the WD2010 chips are bad, and everyone has reported the exact same > symptoms. I'll be sending private email to those people and be working on > getting replacement chips; I'm curious as to the date code on the bad chips. I *finally* got around to installing my MS3085 and the WD2010 this weekend. The WD2010 seemed to work fine with the stock 20MB drive I was using, so I then put in the 3085. Formatting with the new s4diags was no problem (except for the missing loader on the diag floppy :-) but the surface test started reporting write data errors for 60-70% of all sectors. I stopped the test after about 10 cylinders, removed the sectors from the bad block table (by the way, is there a *easy* way to do this???), powered down and reseated the WD2010 and reconnected the 3085 to make sure I had everything right, and tried it again; same results. So I'm now using the 3085 with the WD1010 with no problems (bad block table now has only 12 entries after formatting with the WD1010 and the original diag floppy). So, is this a 1) 3085 problem (don't think so, because it works with the WD1010), 2) WD2010 problem (don't think so, because it works with the 20MB drive), or 3) a 3085/WD2010 interfacing problem (I think I remember Jan Bagend discussing this at one time...are these the symptoms you saw?). BTW, my system is a P3..P5 7300 with 1/2MB and an 1/2MB expansion memory board. Thanks in advance for any input, -- ------------------------------------------ Jeff Elliott b11!elvis!elliott@ingr.com uunet!ingr!b11!elvis!elliott