🚀 go-pugleaf

It seemes that you have an impropper connected SCSI - bus.  I assume, you
have no / badly connected terminator resistors at the bus. Look if the
terminator resisters are plugged in the right way round, and if they have
Termpower connected to the 220 Ohm side. 

The sd driver uses the same chunk of data space for the Inquiry data and
for the request sense data. The inquiry command is used by the sd driver
at startup time to distinguish between the different brands of
controllers.

The Inquiry data contains information about the vendor of the controller.
The sense data contains information about the last faulty command.  It is
fetched by the sd driver after every failed command.

In the exapmle below you can see, that the "sense data" contains the
string "EMULEX" at the correct vendor info position (see ANSI X3.131). 

sd0:  failed cmd =  8  20  0  0  1  0  
sd1 error:  sense key(0x0): no sense,  error code(0x45): unknown error
           sense = 0  0  0  1  1f  12  0  0  45  4d  55  4c  45  58 

I assume that for some reason, the driver could obtain the inquiry data at
boot time. But afterwards for some other reasons it could not pass any
further command to the MD21.

Check if the  SCSI/E board has the same faulty layout as the 3/60 :-(
(TERMPOWER connected to ground).  I did't have had the time to figure that
out and our cables have no connetion on the TERMPOWER pin for that reason.

Most SCSI problems are caused by improper connections/terminations.


        J. Schilling 
        H. Berthold AG 
        Teltowkanalstr. 1-4 
        D 1000 Berlin 46 
        +49 30  7795 - 400 

joerg@berthold.de 

... tub!berthold!joerg 
... unido!berthold!joerg 
... sunmuc!berthold!joerg 
... sun!sunmuc!berthold!joerg