From owner-freebsd-scsi@FreeBSD.ORG Fri May 14 07:00:41 2004 Return-Path: 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 D0E6F16A4D0; Fri, 14 May 2004 07:00:41 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2389E43D41; Fri, 14 May 2004 07:00:40 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Fri, 14 May 2004 10:00:38 -0400 Message-ID: From: Don Bowman To: 'Scott Long' , Don Bowman , Zac Thompson Date: Fri, 14 May 2004 10:00:37 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: "'scsi@freebsd.org'" Subject: RE: smartmontools with aac X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2004 14:00:42 -0000 From: Scott Long [mailto:scottl@freebsd.org] > Don Bowman wrote: > > is there a way to use smartmontools with > > aac? > > > > e.g. smartctl wants to see 'ad0' or 'da0' > > as the disk to connect to. For aac, it is > > aacd0. Specifying: > > > > smartctl -i -d scsi -a aacd0 > > gives > > Smartctl open device: aacd0 failed: Inappropriate ioctl for device > > > > I'm not really sure what ioctl are being used, > > i guess i should look in the smartmontool source. > > > > --don > > AAC containers do not export SMART events. You can monitor individual > disks by enabling the aacp driver and watching the /dev/passN devices, > or you can script the aaccli to report events for you. So i was tracking down why i can't do a 'camcontrol inq' on aac. When i do: camcontrol inq 0:2 -v I get: pass1: Fixed unknown SCSI-3 device CAM status is 0x12 [long pause, ~30s?] camcontrol: error getting transfer settings CAM status is 0x6 camcontrol cmd pass1 -v -c "12 01 00 00 01 00" -i 1 "b3 b5" 0 31 ---------- According to the docs, the second of these numbers should be 0, unless the LUN (pass1) is not present, in which case 31 is correct, but then the first number should be 3. Maybe this is what the RAID is botching, and what "camcontrol inquiry" can't handle to get the serial number. Byte | Bit | 7 6 5 | 4 3 2 1 0 0 | Peripheral Device Type | Peripheral Qualifier "Peripheral Qualifier is set to zero to indicate that the LUN specified in the IDENTIFY Message is currently supported. Peripheral Qualifier is set to 011b when the LUN specified in the IDENTIFY Message is not present. Peripheral Device Type is set to zero to indicate that the device is a Direct-Access. Peripheral Device Type is set to 1Fh when the LUN specified in the IDENTIFY Message is not present."