[comp.unix.sysv386] problems installing esix 5.3.2-D with fd and wrens

det@cimcor.mn.org (Derek Terveer) (09/07/90)

I am experiencing trouble installing esix 5.3.2-D on a 386-25 system
with a wren IV and a wren III using a future domain TMC-885 controller.
Both of these drives are recognised by the scsi bios on the controller
(the labels come up at boot time) and i can use these drives under dos,
and they can be low level formatted and a surface analysis run upon
them (with no errors, by the way), but i can't get esix to install!

If the wren IV is drive 0 (with or without the wren III as drive 1) i
get as far as the fdisk command in /INSTALL on the boot floppy.  I get
the errors:

	fdisk: can't open /dev/rdsk/0s0

If the wren IV is drive 0 (without the wren III attached at all) I get
the errors:

	echa_mkedt: HA 1 has no TCs.
	WARNING: ECHD Driver: Can not locate a Unit 0 (primary) Hard Disk

If the wren III is drive 0 (with or without the wren IV as drive 1) i
get as far as the "disksetup -v" command (which does the surface
format) and it bombs with the message:

checking for bad sectors in Esix system partition

checking cylinder 3.  Too many bad tracks found (253) .....

numbad=31	nbadtrack=253


I have tried starting esix on different cylinder boundaries, using a
different percentage of unix, changing the geometry (i.e., instead of
148 cylinders, 64 heads, and 32 sectors/track), etc., to no avail.

I have the controller card set to the jumper settings recommended by
esix tech support.  The drives are properly cabled and terminated (as
far as i know) and have parity enabled, motor start on, and terminator
power is taken from the wrens (the last is apparently required by the
fd controller).

I don't believe that either the drives or the controller are bad in
this case.  The only two options that i see as realistic possibilities
are that i have either really screwed up something fundamental in the cabling/
installation (possible, but unlikely in this case since the drives seem
to run fine under dos and the wren iii was working fine with the public
domain st-01 scsi driver published on usenet earlier under 5.3.2-C) or
that their is a bug in the driver for the fd controller and/or fast
file system.

Is there anyone running esix 5.3.2-D in any kind of configuration
similar to mine?  I.e., future domain scsi controller and wren drives?
It would be hard to believe that the wrens would be incompatible since
they have such a good reputation....!

Please e-mail me at det@cimcor.mn.org since my machine is not up.

derek

-- 
temporarily:  			derek@cimcor.MN.ORG
as soon as i get my pc back:	det@hawkmoon.MN.ORG