Original posting:
>We've got a 2392 we are trying to put on a 753 controller with little luck.
>Configuration is a 3/280 running 4.0.3. There are 2 Fuji 2382's on the
>same controller that are and have been running fine.
>The controller, the cable, and the 2392 have all been replaced.
>I still can't read the label or format it or anything.
>
>I double checked the switch settings and the setup with the
>vendor (R-Squared), our service company, and Xyologics.
>I've tried the net specified format.dat, I've tried smaller
>format.dats. I pulled every other board (aside from memory and the 451
>the system boots from) out of the backplane (double checking jumpers
>along the way) with no change.
>
>Can someone contact me who has one of these actually up and running?
>
The long and the short of it is if you have to install one of these
you have to make sure you are running one of the following prom versions
on your controller. Our service company called Xylogics before I sent
out the help mail, but the people at Xylogics didn't have any
suggestions. It wasn't until one of the responses gave me a specific
person within Xylogics to call that we got the right proms.
WHO TO CALL:
>Steve Kelley of Xylogics [(617) 272-8140 Extension 373] informed me
>that Xylogics 753-103 controllers required version 2.23 of firmware and
> 753-107 controllers required version 2.3 of firmware inorder
>to work properly with the new drives (Large CDC & Fuji 2392's).
Unfortunatly it didn't help. Our service company said it should work,
Xylogics said it should work, the vendor who sold us the disk said it
should work (R-Squared).....but it didn't. The vendor is now supposed
to be swapping out the 2392 for two 2382's....even though they now say
they misplaced the paperwork (heavy sigh).
Responses verbatim follow:
Ken Smith forwarded me the folowing from comp.sys.sun. The very
interesting part of this was that his mail arrived before my posting to
sun-managers did.
>We are running two of these drives on Xylogics 753 controllers. We had a
>few problems associated with being "on the leading edge" and all :-).
>
>If your controller is a pre-May 1990 unit, you probably need new
>microcode. The old microcode did not understand the way that Fujitsu did
>extended cylinder addressing. This same problem has been discussed here
>on the CDC 9772/9773 disk drives (858Meg and 1.3Gig drives in the 14" form
>factor). The new firmware works fine for both drive types. I have run
>the following controllers, and all seem happy with new firmware:
>
>753-103 (firmware # 180-002-186 Rev 2.23)
>753-107 (firmware # 180-002-271 Rev 2.3)
>7053 (firmware # 180-002-271 Rev 2.3)
>
>We use our 2392 drives as server, and client root/swap filesystems, as
>well as user filesystems. They seem to be very nice drives. There are
>three problems (?) I am aware of though.
>
>1) My hands are bigger than the designers. This became painfully obvious
> the first time I tried to plug in the SMD interface cables. I prefer the
> way the 2382 was laid out (you could at least get to the cables... 2392
> drive is a bit of a pain). At least they have "A" cable "in" and "Out"
> connectors, instead of the one connector like the 2382 that requires funky
> cables.
>
>2) No IPI interface is currently available :-(. I hope someone at Fujitsu
> is reading this, and takes care of this problem!
>
>3) The drives do not work on a Gould NP1 system, as the drive does the
> extended addressing a little awkwardly. Actually, we are running one
> drive on a Gould, but we only use the first 1023 cylinders. If we go
> beyond this limit, the drive does a RTZ for every seek to a cyl>1023. We
> have been told by people at Fujitsu that they are working on a new version
> of the logic board for the drive that would fix this, and negate the need
> for the special Xylogics firmware.
>
>Example format.dat entries:
>
>disk_type = "Fujitsu-M2392 Swallow" \
> : ctlr = XD7053 \
> : ncyl = 1914 : acyl = 2 : pcyl = 1916 : nhead = 21 : nsect = 81 \
> : rpm = 3600 : bpt = 50400 : bps = 610
>
>partition = "Fujitsu-M2392 Swallow" \
> : disk = "Fujitsu-M2392 Swallow" : ctlr = XD7053 \
> : a = 0, 20412 : b = 13, 74844 : c = 0, 3255714 : g = 57, 3158757
>
>To use the settings above, set the SW1 for 608 bytes/sector (Switches
>2,5,6) closed. The drive automagically adds two to the value set by the
>switches to give you the 610 bytes/sector. And yes, I know the number of
>sectors is actually 83+runt in our setup. Slip sectoring, and paranoia
>(read past experience) were included in the values we used....
>
>Other drives? Rumour has it that Seagate (was Imprimis, was CDC) is
>readying a 2.5Gig drive with SMD-E and IPI interfaces. I have not seen
>one yet, but an associate has. I am anxiously awaiting its release...
>
>Curt Freeland
>Manager, Systems Engineering
>Purdue University
>Engineering COmputer Network
>(curt@mischief.ecn.purdue.edu)
>(317) 494-3715
and From: sarah.lerc.nasa.gov!ron@uunet (Ron Gaug)
>Recently I swapped a Fuji M2382K drive for a M2392K drive on a Sun4/260
>running SunOS 4.1.
>Steve Kelley of Xylogics [(617) 272-8140 Extension 373] informed me
>that Xylogics 753-103 controllers required version 2.23 of firmware and
> 753-107 controllers required version 2.3 of firmware inorder
>to work properly with the new drives (Large CDC & Fuji 2392's).
>I obtained the firmware upgrade through my xylogics distributor.
>Here's the switch settings that I used on my 2392K.
>
>SW1
>1,3,4,6,8 OFF 600 bytes/ sector
>2,5,7,9,10 ON
>SW2
>2 ON, Rest OFF Channel B disabled
>SW3
>5,7 ON, Rest OFF
>SW4
>2,7,8 OFF
>1,3,4,5,6 ON
>
>Here's the format.dat entry I used:
>
>disk_type = "Fujitsu-M2392K" \
> : ctlr = XD7053 \
> : ncyl = 1914 : acyl = 2 : pcyl = 1916 : nhead = 21 : nsect = 83 \
> : rpm = 3600 : bpt = 50400 : bps = 600
and further From: sdsu.sdsu.edu!newloral!sysadmin!jes@rutgers (John E. Schimmel)
>You are probably running down rev on you 753. It must have firmware level
>2.23 or 2.3 to handle the 2392s. We just got ours up a couple weeks ago, and
>had a lot of the same problems. Swapping out our firmware solved it.
>
>I've two M2392 on a Ciprico Rimfire in a Solbourne Series5 machine, so
>this is a different situation than yours, but perhaps the following
>information will help you get things going or give some hints at least.
>
>So here we go...
>
>From the manuals (Fuji and Ciprico) and the driver and formatting
>utility sources (YES, you get sources from Ciprico) I came up with the
>following setup:
>
>disk_type = "Fujitsu-M2392K" \
> : ctlr = XD7053 \
> : ncyl = 1914 : acyl = 2 : pcyl = 1916 : nhead = 21 : nsect = 84 \
> : rpm = 3600 : bpt = 50400 : bps = 592
>
>(transformed from Rimfire syntax to /etc/format.dat syntax)
>
>Micro switches on the Main PCA are set as follows:
>
>SW2: all keys off (factory setting)
>
>SW3: keys 8,7,6 off; key 5 (tag 4/5 enabled) ON; keys 4 to 1 off (Unit 0)
>
>SW1: keys 10,9,8,5,2 on (590 phys. sector length, 2 magically added by
> drive logic); others (7,6,4,3,1) off
>
>SW4: nothing changed, using factory setting as outlined in the manual,
> same holds for SW1 on Interface PCA.
>
>One of the two drives formats nicely, passed verification and runs
>fine now for 3 days. The other one seem's to have to much bad spots
>for the above setup: format reports: "no alternates left" and the
>verify-pass fails on every first sector on a new track.
>
>Using:
>disk_type = "Fujitsu-M2392K" \
> : ctlr = XD7053 \
> : ncyl = 1912 : acyl = 4 : pcyl = 1916 : nhead = 21 : nsect = 81 \
> : rpm = 3600 : bpt = 50400 : bps = 592
>ie. 4 alternate cylinders and 4 sec/track for slipping, the beast
>formats, but verifying yields the same failure as above.
>My conclusion is now that the drive is bad and I will check with our
>distributor tomorrow.
Thanks to
Ron Gaug
John E. Schimmel
Ken Smith
Curt Freeland
Kurt Schreiner
and the rest of the list for putting up with my part of the bandwidth.
Murf
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:05:58 CDT