From owner-freebsd-scsi@FreeBSD.ORG  Tue Feb  7 14:17:02 2006
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
X-Original-To: scsi@freebsd.org
Delivered-To: freebsd-scsi@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 68FBF16A420;
	Tue,  7 Feb 2006 14:17:02 +0000 (GMT)
	(envelope-from danny@cs.huji.ac.il)
Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D6A6A43D45;
	Tue,  7 Feb 2006 14:17:01 +0000 (GMT)
	(envelope-from danny@cs.huji.ac.il)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by cs1.cs.huji.ac.il with esmtp
	id 1F6TeO-000LQ6-SF; Tue, 07 Feb 2006 16:17:00 +0200
X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4
To: "Kenneth D. Merry" <ken@freebsd.org>
In-reply-to: Your message of Tue, 7 Feb 2006 07:07:18 -0700 .
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 07 Feb 2006 16:17:00 +0200
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1F6TeO-000LQ6-SF@cs1.cs.huji.ac.il>
Cc: scsi@freebsd.org
Subject: Re: iSCSI/scsi problem 
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2006 14:17:02 -0000

> On Tue, Feb 07, 2006 at 15:51:30 +0200, Danny Braniss wrote:
> > hi,
> > I'm writing a iSCSI driver, and having problem with an
> >      HP StorageWorks IP Storage Router 2122-2
> > 
> > the CAM is sending a few Inquiry LUN commands
> > and the first Test Unit Ready is nacked with:
> > 	Logical Unit Not Ready, Initializing Cmd. Required
> > 
> > this could be a Target problem, like some misconfiguration, but
> > I was wondering if there is some CAM magic that I missed?
> 
> That generally means that the target needs to be spun up.
> 
> CAM will respond by sending a START UNIT command.

im going through the sniffed packets, and can't see a START UNIT
i do see Read Capacity, Reads, Sync. Cache, but no START :-(

danny