From owner-freebsd-scsi@freebsd.org Wed Sep 9 05:42:54 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7FEF9CD598 for ; Wed, 9 Sep 2015 05:42:54 +0000 (UTC) (envelope-from ethernext@gmail.com) Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A1931EB2; Wed, 9 Sep 2015 05:42:54 +0000 (UTC) (envelope-from ethernext@gmail.com) Received: by ioii196 with SMTP id i196so983814ioi.2; Tue, 08 Sep 2015 22:42:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cmhl8M66R46XglF8FAPwfrtjGz6AoBcOxqwCn9vXia4=; b=sPh+K0DaAv5x76yLZovqM8cGqAnVoY2WGhZfk2yDopcJ/KPlgmpWNQgjH0tUg/dRSo lHzZhq6x9PFv5YRysLcdsNdT2JZieMRyHr1MR9o8IS/LB7KzhtUlg3QKQSv7xocoVtNU 3/0ofqqnVdBJiiC018nGnk//CnrAzT2tT70eNYGrVrGU8WeOF9iI7HxU1v4WgXN0J5qC OcORcDHTcFEoopLV0cch92OwsdLpxv6cWzwgpAIH9Fw90FgAd8aiIrLzlKropMGMgkJP uVmjvuICpVtTL9L+HlW5KaQJtNFbphzaGvzXUYocP0Q/Lru6y96S7AZyljZL1HD/YyCk zsgg== MIME-Version: 1.0 X-Received: by 10.107.3.94 with SMTP id 91mr44962829iod.178.1441777373962; Tue, 08 Sep 2015 22:42:53 -0700 (PDT) Received: by 10.107.140.12 with HTTP; Tue, 8 Sep 2015 22:42:53 -0700 (PDT) In-Reply-To: <20150909033510.GA34413@FreeBSD.org> References: <20150909033510.GA34413@FreeBSD.org> Date: Wed, 9 Sep 2015 01:42:53 -0400 Message-ID: Subject: Re: ses/pass devices (enclosure/processor devices) not all showing up? From: "Bill (EtherneXt)" To: John De Boskey Cc: FreeBSD-SCSI Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2015 05:42:54 -0000 Hi John, On Tue, Sep 8, 2015 at 11:35 PM, John De Boskey wrote: > Hi Folks - > > I have a shelf with 84 sata drives. All drives show up > correctly and are accessible. The shelf appears to have > multiple processor devices and one enclosure device internally. > For instance: > > # camcontrol devlist | grep XYRATEX > at scbus7 target 159 lun 0 (pass18) > at scbus7 target 188 lun 0 (pass47) > at scbus7 target 217 lun 0 (pass76) > at scbus7 target 232 lun 0 (pass91) > > # camcontrol devlist | grep ses > at scbus7 target 144 lun 0 (ses0,pass3) > > # camcontrol smprg pass18 | grep 'Number of Phys:' > Number of Phys: 25 > # camcontrol smprg pass47 | grep 'Number of Phys:' > Number of Phys: 37 > # camcontrol smprg pass76 | grep 'Number of Phys:' > Number of Phys: 37 > # camcontrol smprg pass91 | grep 'Number of Phys:' > Number of Phys: 25 > # camcontrol smprg ses0 | grep 'Number of Phys:' > Number of Phys: 37 > ...... you definitely want to install and use the sg3_utils package to manage the enclosure. the sg_ses utility in sg3_utils will provide most all the info you will ever need. you can use sg_ses to manage drive/slot LED's, fans, power supplies and more. sg3_utils installs a lot of useful tools so take a look at them all. there are also some basic ses tools in /usr/share/examples/ses. sdparm is also a handy tool for managing drives. for the 4 pass devices, I am not sure. there is a scsi processor device driver named pt but I have no idea if it is related. do a man pt for more info. you may also want to build the kernel with the sg device which is another pass-thru device for compatibility with the scsi generic linux driver. with sg_ses, take a look at the line for subenclosures: #>sg_ses ses1 -p 1 SUN CSM200_E 98C4 Configuration diagnostic page: number of secondary subenclosures: 0 ^^^^^^^^^^^^^^^^^^^^^^^^ if you see 4 subenclosures, those scsi processor devices may be used for internal enclosure management and communication with the ses0 device, but thats only a guess on my part. you can also try using sg_ses on the pass devices to see if they report enclosure services. also see the sg3_utils website, lots of detail on using the utilities. Best, -- Bill