From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 5 11:34:05 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18AA0106566C for ; Wed, 5 Mar 2008 11:34:05 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id C0D808FC26 for ; Wed, 5 Mar 2008 11:34:04 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 8D45E41C7AC; Wed, 5 Mar 2008 12:15:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id 8lLepmWIUy2a; Wed, 5 Mar 2008 12:15:06 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 3D33F41C7A9; Wed, 5 Mar 2008 12:15:06 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 3E17E44487F; Wed, 5 Mar 2008 11:13:06 +0000 (UTC) Date: Wed, 5 Mar 2008 11:13:06 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Cristiano Deana In-Reply-To: Message-ID: <20080305111237.W50685@maildrop.int.zabbadoz.net> References: X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: mpt driver: check raid status X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Mar 2008 11:34:05 -0000 On Wed, 5 Mar 2008, Cristiano Deana wrote: > Hi, > > I'm using a 7-RELEASE on a Dell PowerEdge 1955, using a mpt driver to > manage a hardware raid1. > Is there any way to check the status of the raid? Not really. > Now it's running on a single disk (the second one failed and has been > removed), and the only thing i can see are: > mpt0: mpt_cam_event: 0x16 > mpt0: mpt_cam_event: 0x12 > mpt0: mpt_cam_event: 0x16 > mpt0: mpt_cam_event: 0x15 > mpt0: mpt_cam_event: 0x21 > mpt0: mpt_cam_event: 0x15 > mpt0: mpt_cam_event: 0x21 > mpt0: mpt_cam_event: 0x15 > mpt0: mpt_cam_event: 0x21 > > in messages. > > Thanks in advance mpt0: mpt_cam_event: 0x16 MPI_EVENT_SAS_DISCOVERY most likely started mpt0: mpt_cam_event: 0x12 MPI_EVENT_SAS_PHY_LINK_STATUS mpt0: mpt_cam_event: 0x16 MPI_EVENT_SAS_DISCOVERY most likely done mpt0: mpt_cam_event: 0x15 MPI_EVENT_IR2 that could be LD/PD/... state changed mpt0: mpt_cam_event: 0x21 MPI_EVENT_LOG_ENTRY_ADDED mpt0: mpt_cam_event: 0x15 MPI_EVENT_IR2 mpt0: mpt_cam_event: 0x21 MPI_EVENT_LOG_ENTRY_ADDED mpt0: mpt_cam_event: 0x15 MPI_EVENT_IR2 mpt0: mpt_cam_event: 0x21 MPI_EVENT_LOG_ENTRY_ADDED Giving more details would depend on a subtype which is dependend on the event. What we's really need is someone with the specs to write the code and add the printfs, etc. /bz -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time.