From owner-freebsd-current  Mon Aug  4 16:03:23 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA04089
          for current-outgoing; Mon, 4 Aug 1997 16:03:23 -0700 (PDT)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA04057;
          Mon, 4 Aug 1997 16:03:16 -0700 (PDT)
Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA01634
  (5.67b/IDA-1.5); Tue, 5 Aug 1997 01:03:13 +0200
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id BAA01234; Tue, 5 Aug 1997 01:03:12 +0200 (CEST)
X-Face: "<d]#=8pzx);RzeqSKI86OVa7=!0/(uRa.+B.9Z9\eNUn@UG?!`y7yt2dFNn%k4'.}](uE%
 yCO)$e&Y1%3EO~ifu6Q-#YUM&JZ't,}JkPnAz,8Dj33u%@GBi%[Y#LHz$]h7a<p4)-jKI7~sKjlP-^
 EvA[G;]v&0]W!EL%shs,{7x0|oqN4YVIs5,NI#,V{9"WF):5&RkOhyj*#-IAG}Tnu;YCF,d
Message-Id: <19970805010311.12729@mi.uni-koeln.de>
Date: Tue, 5 Aug 1997 01:03:11 +0200
From: Stefan Esser <se@FreeBSD.ORG>
To: Chris Timmons <skynyrd@opus.cts.cwu.edu>
Cc: current@FreeBSD.ORG, Stefan Esser <se@FreeBSD.ORG>
Subject: Re: NCR behavior wrt spun-down disks at boot
References: <19970417114955.56763@x14.mi.uni-koeln.de> <Pine.BSF.3.95.970803213137.12149A-100000@opus.cts.cwu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.74
In-Reply-To: <Pine.BSF.3.95.970803213137.12149A-100000@opus.cts.cwu.edu>; from Chris Timmons on Sun, Aug 03, 1997 at 09:46:53PM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Aug 3, Chris Timmons <skynyrd@opus.cts.cwu.edu> wrote:
> 
> Hi Stefan,
> 
> I have a couple of DEC RZ26L drives on an SC200 controller (data only, not
> the boot device nor swap.)  Presently I think they are jumpered to wait
> for a start unit command before they spin up (I'll fix that the next time
> I get into the box.)
> 
> With -current of July 22, 1997, the boot probe works fine, and when fsck
> touches them I get a couple of complaints but thereafter everything is ok:
> 
> ncr1: <ncr 53c810a scsi> rev 0x11 int a irq 11 on pci0.12.0
> ncr1: waiting for scsi devices to settle
> scbus1 at ncr1 bus 0
> sd1 at scbus1 target 1 lun 0
> sd1: <DEC RZ26L    (C) DEC 440C> type 0 fixed SCSI 2
> sd1: Direct-Access 
> sd1: 10.0 MB/s (100 ns, offset 8)
> 1001MB (2050860 512 byte sectors)
> sd2 at scbus1 target 2 lun 0
> sd2: <DEC RZ26L    (C) DEC 440C> type 0 fixed SCSI 2
> sd2: Direct-Access 
> sd2: 10.0 MB/s (100 ns, offset 8)
> 1001MB (2050860 512 byte sectors)
> 
> 
> (complaints until the drives come up... work fine thereafter)

Hmmm, doesn't your SCSI BIO Sstart those drives ???
Mine does ...

> sd1: error code 1, retries:2
> sd1: error code 1, retries:1
> sd1: error code 1, FAILURE
> sd2: error code 1, retries:2
> sd2: error code 1, retries:1
> sd2: error code 1, FAILURE
> 
> With -current from today, things don't go as well.  I don't have the
> machine on a serial console, so I will paraphrase what happens. 
> 
> The boot probe does not succede and the system hangs.  As in the log from
> above, we get to:
> 
> 	scbus1 at ncr1 bus 0
> 
> but then before we see sd1 (partially incomplete hand transcribed):
> 
> 	scbus target 1 lun 0: command failed (9ff) @ fa043600
> 	
> 	ncr1 Aborting Job...
> 	ncr1:1: Error (10:0:) (8-0-0) (0/3) @ script 424
> 
> 
> and the reset switch is my only friend :(

Hmmm ...

> I think it is an acceptable solution for me to jumper the drives so that
> they spin up on power, but I thought that this change in behavior was
> noteworthy enough to call to your attention.

Did you verify, that there is no problem, if your drives
spin up as soon as power is applied ?

Sorry, if it takes a few days until I'm able to send a 
reply, I'm currently overloaded with work :(

Regards, STefan