[comp.sys.dec] DS3100 problems - some odd ones

hurf@batcomputer.tn.cornell.edu (Hurf Sheldon) (03/23/90)

	
	Well, we have a cornucopia of DS3100 problems ...
	All on different systems and all somewhat puzzling.

	1) System running 3.1/2.1 , 12mb rz55:
	   We added a WrenVI and an Exabyte to the scsi
	   bus. Everything is terminated correctly(we think).
	   The only thing I don't like is that the scsi cable 
	   we were given is the ushielded variety like an
	   in-cabinet cable. The rz55 was rz1, the boot device,
	   so we made the new disk rz0 and the tape is at SCSI 5.

	   Problem: 
		Powering up with any of the drives powered up
	   gets a display screen filled with little sprinkles of 
	   white and the system hangs. Turning off all the drives
	   allows the screen to blank white and then go to console.
	   Turning the drives on after the white blanking works
	   and everthing works ok from then on...


	 2) System running 3.101,/2.2 12mb, rz23 internal
	    This system had a maxtor 8760 added to it before
	    doing the upgrade. The root partition is on the 
 	    8760. The 8760 is rz0, the rz23 is rz3.
	    Problem:
	    It will not boot correctly with the 3.1 
	    kernal, complaining that it can't find the rz23
            or just hanging.
 	    We were able to come up single user on the
	    rz23 with the 8760 disconnected. The 3.0 kernal
	    boots and runs fine from the 8760.

	  3)3.1 Systems with newish Exabytes,
	    2 very differnt systems as far a disks, memory, etc
	    2 separate instances so far.
	    Problem:
	    Even with the dip swith #3 set to even byte disconnect
	    the drive hangs on reads and writes. Futhermore,
	    thruput from the drive is abysmal, on the order of
	    23k/sec. THe drives do a lot of searching, clicking
	    as well. Systems with Exabytes purchased in the fall do not
	    have this problem.

	  4)3.0/3.1 systems
	    Serial lines turned on, DEC supplied cable used to
	    connect to terminals and macs running terminal
	    emulation.
	    Problem:
            When the terminal is turned off the getty process for that
	    line runs amok, hogging the cpu.   
	    Killing off that particular pid does not stop the problem.


Any and all insights, suggestions appreciated.

hurf


-- 
     Hurf Sheldon			 Network: hurf@ionvax.tn.cornell.edu
     Lab of Plasma Studies		  Bitnet: hurf@CRNLION
     369 Upson Hall, Cornell University, Ithaca, N.Y. 14853  ph:607 255 7267
     "And the walls came tumbling down"