From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 05:36:17 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0079D106566B for ; Fri, 29 Apr 2011 05:36:17 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7711F8FC14 for ; Fri, 29 Apr 2011 05:36:16 +0000 (UTC) Received: by bwz12 with SMTP id 12so4087383bwz.13 for ; Thu, 28 Apr 2011 22:36:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=hgLs9DYglMteHdBfhPsC3IMrQw9VDu7FyYY1QJgfRG8=; b=kxpcLwtlQnr2ukDr1+T8EVT0MhomvdA1bgNGMPJZzWQAdEvvGX32OG0PphBwCjekuX iWnNAMJ/Q1eV3BaW5DAT8oRD3686rh4BQvWud5cJpBOk7HHtka4Q/f85bzODXd9EBhCE aSsWbf38pdZFcdM2nBUXauE2FLKorfv9JXHOE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=EnAHq/oy26TyWpgmT/TRPlIVFERZWFQkyRENq6QhhjjGCqkXTsW8Vhv4/crP0893hQ 4RyOC9NUfSFJBPvGB1XECcLBk2usFw6Gg4UmqwQhE7rWKfBONzMMu0n42ifmpOnOaugz qFn/Ynsa4N5dm9YXNkZgH5M3A2QQhIXkiQIeQ= Received: by 10.204.29.18 with SMTP id o18mr2183536bkc.12.1304055375311; Thu, 28 Apr 2011 22:36:15 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id y22sm1396285bku.8.2011.04.28.22.36.13 (version=SSLv3 cipher=OTHER); Thu, 28 Apr 2011 22:36:14 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DBA4E40.4000404@FreeBSD.org> Date: Fri, 29 Apr 2011 08:36:00 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Rumen Telbizov References: <20110427125736.GA1977@icarus.home.lan> <4DB8381B.4030408@FreeBSD.org> <20110428032347.GA15220@icarus.home.lan> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Denny Schierz , FreeBSD Stable , Jeremy Chadwick Subject: Re: MPS driver: force bus rescan after remove SAS cable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 05:36:17 -0000 Rumen Telbizov wrote: > > Also identify function doesn't work from the OS (no problem > > via the card BIOS). Don't remember having any luck with sg3_util > > package either but worth trying again. > > I don't use SAS myself, but wouldn't the command be "inquiry" and not > "identify"? "identify" is for ATA (specifically SATA via CAM), while > "inquiry" is for SCSI. Where SAS fits into this is unknown to me. > > > Well I have SATA disks visible as /dev/da* . From camcontrol(8): > > inquiry Send a SCSI inquiry command (0x12) to a device. By > default, > camcontrol will print out the standard inquiry data, device > serial number, and transfer rate information. The user can > specify that only certain types of inquiry data be printed: > > Example: > > # camcontrol inquiry /dev/da47 > pass48: Fixed Direct Access SCSI-5 device > pass48: Serial Number WD-WMAUR0408496 > pass48: 300.000MB/s transfers, Command Queueing Enabled > > It's a SATA disk in this case attached to SAS/SATA backplane and SAS2008 > HBA chip (9211-8i) > What I need is a way to light on the fault led on the disk that I want > to identify (point to) > This is usually what I need when I send a DC technician to replace a > disk. For which I though I should > be using: > > identify Send a ATA identify command (0xec) to a device. > > From my experience SAS or SATA disks - I always get those as /dev/da* > disks. It's a combo controller and backplane. > So which is the correct way of identifying a disk? `camcontrol identify` means sending ATA IDENTIFY DEVICE command to the ATA device. That command is roughly the analogue of the SCSI INQUIRY command. It has nothing to do with LEDs. LEDs most likely controlled via ses device or some alike management thing. The fact that you see ATA device as daX is just means that your SAS controller does protocol translation on-the-fly. It allows you to communicate with disk using SCSI commands _instead_ of ATA. -- Alexander Motin