[comp.sys.next] Using a Fujitsu 2266S SCSI disk on a NeXT

abe@mace.cc.purdue.edu (Vic Abell) (12/07/90)

Here is a disktab for attaching a Fujitsu 2266S to a NeXT.

# Fujitsu M2266S 1.2GB drive with 512 byte sectors
FUJITSU M2266S-512|Fuji 1.2 GB w/512 byte sectors as 1 partition:\
	:ty=fixed_rw_scsi:nc#1658:nt#15:ns#42:ss#1024:rm#3600:\
	:fp#630:bp#0:ng#0:gs#0:ga#0:ao#0:\
	:os=sdmach:z0#32:z1#96:ro=a:\
	:pa#0:sa#1043910:ba#8192:fa#1024:ca#32:da#4096:ra#10:oa=time:\
		:ia:ta=4.3BSD:

/usr/etc/scsimodes reports the following characteristics.

SCSI information for /dev/rsd0a
Drive type: FUJITSU M2266S-512
512 bytes per sector
85 sectors per track
15 tracks per cylinder
1658 cylinder per volume (including spare cylinders)
3 spare sectors per cylinder
15 alternate tracks per volume
2107703 usable sectors on volume

Other characteristics:

	8.33 ms latency
	Positioning:	4 ms minimum
			14.5 ms average
			30 ms maximum

Performance appears to be the same as my previous disk, a MAXTOR 8380S
(330 MB) from NeXT.  The 2266S is louder than the 8380S, however.

To use this disk as a boot device, it must be SCSI target 0 (jumper CN9),
and you must remove the jumpers 1-2 and 15-16 at block CNH2, as described
in an article from comp.sys.next by Izumi Ohzawa.

I set the "front porch" value to one cylinder's worth of sectors, and
"back porch" to 0.  My uninformed choices were based on the settings for
devices already described in /etc/disktab.  If anyone from NeXT is
listening, I repeat the oft-asked, never-answered question,

	"What do ``front porch'' and ``back porch'' signify, please!!!"

Vic Abell <abe@mace.cc.purdue.edu>

(And here is Izumi Ohzawa's invaluable article.)

Article 7153 of comp.sys.next:
From: izumi@mindseye.berkeley.edu (Izumi Ohzawa)
Newsgroups: comp.sys.next
Subject: FUJITSU M2263S SCSI Disk for NeXT -- Answers
Date: 18 Jul 90 08:04:12 GMT
Organization: University of California, Berkeley

The 660MB Fujitsu SCSI drive now boots fine, thanks to a help from
Helene Young-Myers and Eugene D. Myers.  The problem
I described in an earlier posting was due to incorrect
jumper settings on the drive.

The drive has about the same capacity as Maxtor XT-8760S, and
can be had for a little more than $2000.  The drive is, however,
substantially louder during seeks than Maxtor (see below).

In any case, since some of you sent me mail asking for the summary
report, here it is:

----------------------------------------------------------------------
*** Installing FUJITSU M2263S SCSI disk (660MB) as NeXT boot disk ****

[1] Jumper settings on the drive

  (a) SCSI target# can be set by jumber block "CN9" located right
	next to the SCSI bus connector of the drive.  Three jumpers
	closest to the SCSI connector encode the target number in
	binary.

	View from the back of the drive, with the drive UP-SIDE DOWN.

     |-----------|  |----------------------------|       .......
     | power con.|  |   50 pin SCSI connector    |   CN9 .......
     |-----------|  |----------------------------|       \-/
		                                          ID

	For SCSI target# 0, remove the three left-most jumpers on CN9.
	For SCSI target# 1, keep the left-most one, and remove the
		second and third jumper from left.

  (b) Remove two jumpers at both ends of the jumper block "CNH2".

	Locate the jumper block "CNH2" betweeen two surface-mount VSLI's
	whose labels are obscured by capacitors ( 1cm square blocks
	colored blue on my drive, with two leads).
	There are 8 jumpers in this block.

           On Jumper Block "CNH2" remove:
                        [1-2]      INQUIRY DATA
                        [15-16]    Synchronous Mode Transfer

	If you can't figure out the numbers on the block,
	[1-2] is at one end and indicated by a little triangle mark, and
	[15-16] is at the other end (8-th position from the triangle).

	[  This information was kindly provided by Helene Young-Myers,
	helene@secd.cs.umd.edu, and her husband Eugene D. Myers.
	Thank you! ]


[2] Remove the 40MB swap disk and install M2263S.
	Connect the power cable to the drive, and SCSI flat cable.

[3] Boot from OD, and login as root.
	Use command "scsimodes" as below to get basic formatting
	information, e.g., bytes per sector, etc.
	If "scsimodes" does not work, the most likely cause is
	improper cable connections.

localhost# scsimodes /dev/rsd0a
SCSI information for /dev/rsd0a
Drive type: FUJITSU M2263S-512
512 bytes per sector
53 sectors per track
15 tracks per cylinder
1658 cylinder per volume (including spare cylinders)
3 spare sectors per cylinder
15 alternate tracks per volume
1312343 usable sectors on volume


[4] Add the following entry to the end of "/etc/disktab".

	If the parameters shown by "scsimodes" are different
	from those above, you cannot use the entry below.
	If you want the modified disktab to appear also in
	the SCSI disk's /etc/disktab after BuildDisk, copy
	/etc/disktab to /usr/template/client/etc/disktab, too.
	( BuildDisk will copy /usr/template/client/etc/* onto a
	newly built disk as /private/etc/* )

	Be sure to make backup copies of the unmodified disktab
	in each directory.  Write permission may have to be set
	to edit these files.

----- cut here and append to /etc/disktab -----------------------------------
# FUJITSU M2263S-512 with 3 spare sectors/cylinder and 512 byte sectors
# localhost# scsimodes /dev/rsd0a
# SCSI information for /dev/rsd0a
# Drive type: FUJITSU M2263S-512
# 512 bytes per sector
# 53 sectors per track
# 15 tracks per cylinder
# 1658 cylinder per volume (including spare cylinders)
# 3 spare sectors per cylinder
# 15 alternate tracks per volume
# 1312343 usable sectors on volume
#
M2263S-512|FUJITSU M2263S-512|Fujitsu 760MB w/512 byte sectors as 1 partition:\
	:ty=fixed_rw_scsi:nc#1658:nt#15:ns#26:ss#1024:rm#3600:\
	:fp#160:bp#0:ng#0:gs#0:ga#0:ao#0:\
	:os=sdmach:z0#32:z1#96:ro=a:\
	:pa#0:sa#646230:ba#8192:fa#1024:ca#32:da#4096:ra#10:oa=time:\
		:ia:ta=4.3BSD:
#
# Fujitsu M2263-512, divided into two partitions, sd0a and sd0b.
# This entry has not been tested. It may not work.
# (To use this entry, uncomment lines below, and comment out lines above)
#
# M2263S-512|FUJITSU M2263S-512|Fujitsu 760MB w/512 byte sectors, 2 partitions:\
#	:ty=fixed_rw_scsi:nc#1658:nt#15:ns#26:ss#1024:rm#3600:\
#	:fp#160:bp#0:ng#0:gs#0:ga#0:ao#0:\
#	:os=sdmach:z0#32:z1#96:ro=a:\
#	:pa#0:sa#426230:ba#8192:fa#1024:ca#32:da#4096:ra#10:oa=time:\
#		:ia:ta=4.3BSD:
#	:pb#426230:sb#220000:bb#8192:fb#1024:cb#32:db#4096:rb#10:ob=time:\
#		:ib:tb=4.3BSD:
#
------ cut here --- end of disktab for M2263S --------------------------------


[5] Check if the modified /etc/disktab is valid by;

localhost# disk /dev/rsd0a
disk name: FUJITSU M2263S-512
disk type: fixed_rw_scsi
Disk utility
disk> quit		(quit this program)
localhost#

	If the "disk" command does not recognize the drive, you have
	made a mistake in adding the disktab entry in step [4].
	Check /etc/disktab again.
	

[6] Launch "BuildDisk" and run it.


[7] If you are using the first disktab entry (the whole disk
	as one large partition), you must edit "/etc/fstab" on the
	SCSI disk before you attempt to boot from it.
	If you are using the second entry (for two partions), skip
	this step.

	mount /dev/sd0a /mnt
	chmod 644 /mnt/etc/fstab

	... Edit /mnt/etc/fstab, and comment out or remove the line:
	    /dev/sd0b /clients 4.3 rw,noquota 0 2	

	umount /dev/sd0a


[8] Shutdown and boot from the SCSI disk.

	If the ROM monitor complains:

	SCSI unexpeced msg:1
	sc: Unexpected msg
	.... repeated many times...

	Then, you must have not set the jumpers correctly in step [1](b).

===========================================================================
Additional information of interest

[9] Transfer Rate

localhost# disk /dev/rsd0a
disk name: FUJITSU M2263S-512
disk type: fixed_rw_scsi
Disk utility

disk> read
starting block? 0
# sectors per transfer? 16
number of transfers? 1000
sector increment? 16
16384000 bytes in 21243 ms = 771374 bytes/s
disk> read
starting block? 0
# sectors per transfer? 16
number of transfers? 1000
sector increment? 16
16384000 bytes in 21242 ms = 771374 bytes/s


For comparison, according to Ronald Antony & Axel Merk (the authors of
"TheFormatter" for Wren drives), CDC Wren VI (CDC 94191-15) gives

520000 - 560000 bytes/sec for 512 bytes/sector drive without cache, and
900000 - 980000 bytes/sec with on-drive cache.


[10] Seek Noise

The drive is quite noisy during seek.  My subjective impression
is that the drive is as noisy as the current opical drive, although
the nature of the noises is quite different.  You will
certainly hear seek noise every time a Browser opens a directory or
when someone does an rlogin, etc.  By comparison, Maxtor XT-8760S,
the NeXT's official 660MB drive, is dead quiet.
Perhaps, the drive may not be suitable if you need a quiet environment.
But the 5-year manufacturer warranty is, for me, quite soothing :-)

I don't know how Fujitsu compares with CDC Wren drives with respect to
seek noise.

[11] As always, use the information above at your own risk.  I am
	not responsible for any damage to the SCSI drive or to the
	NeXT cube itself (voiding the warranty) caused directly 
	or indirectly by the use of the information provided above.