From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 16 23:29:15 2005 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 DE07F16A4CE for ; Wed, 16 Mar 2005 23:29:14 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E576543D53 for ; Wed, 16 Mar 2005 23:29:13 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2GNT2sI028129; Wed, 16 Mar 2005 16:29:02 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4238C0B5.3020509@samsco.org> Date: Wed, 16 Mar 2005 16:26:45 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dannyman@toldme.com, freebsd-scsi@freebsd.org References: <20050316224002.GK44253@ratchet.nebcorp.com> In-Reply-To: <20050316224002.GK44253@ratchet.nebcorp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Subject: Re: LSILogic MegaRAID and "camcontrol: cam_lookup_pass:CAMGETPASSTHRU ioctl failed" 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: Wed, 16 Mar 2005 23:29:15 -0000 Danny Howard wrote: > Hello, > > I have a variety of systems that I inherited, with a variety of hardware > RAIDs. Most systems are 4.8-4.10. I want to be able to monitor the > various RAIDs reliably so that I can fix failures faster, but it is a > bear. > > META QUESTION: Can anyone wiser in the ways of SCSI offer a clue? Is > there a "best practices" approach to monitoring hardware > RAIDs on FreeBSD? Or suggestions and advice on > formulating such an approach? There is no universal way to manage RAID devices, especially between different vendors. This is something that the big OEMs have been wishing for for years (I know since I was involved in one of those failed wishes), but has never happened. Most vendors consider their management interface to be highly proprietary or non-portable, so getting source code or specs is practically impossible unless you have the money to make it worth their while. The only think that is close to a universal management tool is the atacontrol in FreeBSD that can configure and monitor several brands of software RAID. This offers no benefit to your MegaRAID hardware, however. > > On a Very Important Machine (VIM) I have: > amrd0: on amr0 > amrd0: 140012MB (286744576 sectors) RAID 5 (optimal) > SMP: AP CPU #3 Launched! > pass0 at amr0 bus 0 target 6 lun 0 > pass0: Fixed Processor SCSI-2 device > Mounting root from ufs:/dev/amrd0s1a > > So, I cast about on the net and found amrcontrol at > http://people.freebsd.org/~emoore/MegaRAID_SCSI/ but it can not see my > controller when I run it. The VIM is quite new, and amrcontrol is two > years old, so, this doesn't seem unreasonable. THe package that you are refering to was a highly experimental and unsupported porting effort that only had a limited lifetime. I'm not surprised that is doesn't work. However, LSI is starting to provide more official FreeBSD support, and it's quite possible that more appropriate software might be available from their website now. I haven't checked recently, though, and if it's not there then I can't answer any questions of when it might be there in the future. Sorry! > > I'd be happy just to probe the dmesg part that says: > amrd0: on amr0 > amrd0: 140012MB (286744576 sectors) RAID 5 (optimal) > > I take "optimal" to mean "okay" and if it ever said something else, I > know I have some emergency maintenance to do, and can fail the VIM. > > So, I tried camcontrol. I am a little wary of issuing SCSI commands to > exotic devices because maybe sometimes those devices get an exotic SCSI > command and freak out? Well, anyways, I try: The amrd0 devices are NOT scsi devices. They are low-level block devices that present themselves as disks to the system. The only thing in your system that camcontrol will be able to talk to is the SES backplane that was probed (the pass0 device that you mentioned earlier). Scott