donn@utah-cs.UUCP (Donn Seeley) (12/03/86)
The University has six of these and we're interested in knowing if other sites have experienced problems with these disks. Notice that I'm interested in the M2361, not the normal Eagle or M2351; we have many of the latter and they've been rock-solid. We're particularly interested in knowing about any ECOs that might have improved the behavior of Super-Eagle drives. I'll summarize to the net if I get anything (and include our own experiences). Thanks, Donn Seeley University of Utah CS Dept donn@utah-cs.arpa 40 46' 6"N 111 50' 34"W (801) 581-5668 decvax!utah-cs!donn
cetron@utah-cs.UUCP (Edward J Cetron) (12/03/86)
Distribution:uu hmm, i seem to remember some of the unix gurus over in cs complaining about the ones here......I think the computer center (the REAL cs dept) had one come in doa....gosh what was that guru's name, peter sealey or something... -ed
lacasse@randvax.UUCP (Mark LaCasse) (12/06/86)
I brought up one Fujitsu M2361 "Super Eagle" here about 3 months ago.
It was on an Emulex SC7003 controller to a Vax 11/780.
The scuttlebut was that the reason our drive failed was that it
had an HDA revison number of <= D3. D4 and above is supposed to be OK.
[I could be wrong and it you could need D5 to be OK. I can't remember
if D4 is OK or not.]
The failure mode for D3 and earlier is that immediately to after six
months of perfect operation, it is prone to the seal around the main
bearing for the platters giving way. This causes bearing oil to get
in the HDA and on the platters. :-(
Our salesman said we were clear and this wasn't our problem, because
the drive said D5 on the back. (By "said" I mean the first numbers not
crossed out.) Turned out this was the rev. number of the power supply.
You have to look inside the drive to find the HDA rev. number. I think
ours was D2. Anyway, it failed.
Since Fujitsu fixed ours on warranty (HDA swap) it has been find. Too
had the HDA fix took them two months at their plant!
If it makes you feel any better, we have about 12 Eagle Is (M2351) hear,
some for as long as 4 or so years, and I don't think any have ever died.
Mark LaCasse qantel!hplabs!sdcrdcf!randvax!lacasse
c/o The Rand Corporation cbosgd!ihnp4!sdcrdcf!randvax!lacasse
1700 Main Street lacasse@Rand-Unix
Santa Monica, CA 90406
213/393-0411 ext. 7420sherouse@godot.UUCP (George W. Sherouse) (12/07/86)
We have been running two SI9761 drives with their wonderful cache controller for about a year. We love them to pieces and have experienced only one major problem. About the time the warranty ran out, one of the drives started popping up with spontaneous bad blocks all over. I believe this was in the spring :-) It took SI a while to sort out the cause of the problem - the drive, the cache controller, and the CMI interface were all covering for one another. Eventually, the process of elimination brought us to the point of replacing the HDA. It turned out that this same thing was going on at several other sites at more or less the same time - and all with HDAs from the same batch. We have had no problems since the HDA was replaced. BTW, we have borrowed a performance monitor for the cache controller this week and were pleased to find that our average hit rate is around 55% and our average request service time is running around 15 ms. You should see what happens during the boot fsck runs!!! - George