Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Apr 2001 10:12:14 -0600
From:      "Kenneth D. Merry" <ken@kdm.org>
To:        Tomi Vainio - Sun Finland - <Tomi.Vainio@Sun.COM>
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: camcontrol stop / restart broken
Message-ID:  <20010430101214.A46826@panzer.kdm.org>
In-Reply-To: <15083.65379.523173.371122@ultrahot.Finland.Sun.COM>; from Tomi.Vainio@Sun.COM on Sun, Apr 29, 2001 at 02:47:47PM %2B0300
References:  <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 29, 2001 at 14:47:47 +0300, Tomi Vainio - Sun Finland - wrote:
> Kenneth D. Merry writes:
>  > 
>  > Can you do the following:
>  > 
>  > camcontrol stop da1
>  > camcontrol tur da1 -v
>  > [ then you can start it back up with camcontrol start ]
>  > 
>  > What I want to see here is the sense information coming back from the drive
>  > when it is spun down.
>  > 
>  > The new error recovery code should be doing the same thing as the old error
>  > recovery code -- sending a start unit.  For some reason it isn't doing the
>  > right thing, though.
>  > 
> cat:~(10)# camcontrol stop da1
> Unit stopped successfully
> cat:~(11)# camcontrol tur da1 -v
> Unit is not ready
> (pass1:ahc0:0:2:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
> (pass1:ahc0:0:2:0): CAM Status: SCSI Status Error
> (pass1:ahc0:0:2:0): SCSI Status: Check Condition
> (pass1:ahc0:0:2:0): NOT READY asc:4,2
> (pass1:ahc0:0:2:0): Logical unit not ready, initializing cmd. required field replaceable unit: 2

This should be fixed as of rev 1.22 of scsi_all.c.  There was an errant
search and replace that caused the 'start' bit in the start/stop unit to
always be set to 0 (stop).  So automatic spinups wouldn't work, and
'camcontrol start' wouldn't work.

> Also messages file is full of these:
> 
> Apr 29 00:55:42 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue
> Apr 29 00:55:43 cat last message repeated 26 times
> Apr 29 00:57:43 cat last message repeated 359 times
> Apr 29 01:07:43 cat last message repeated 1793 times
> Apr 29 01:17:43 cat last message repeated 1794 times
> Apr 29 01:27:43 cat last message repeated 1793 times
> Apr 29 01:34:13 cat last message repeated 1122 times
> Apr 29 01:34:13 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue
> Apr 29 01:34:13 cat last message repeated 43 times
> Apr 29 01:36:02 cat last message repeated 322 times

I'd still like to know when these messages are cropping up.

Ken
-- 
Kenneth Merry
ken@kdm.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010430101214.A46826>