From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 6 13:33:59 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 CF8561065678 for ; Thu, 6 Mar 2008 13:33:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id BC5C78FC19 for ; Thu, 6 Mar 2008 13:33:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 17DDC1A4D87; Thu, 6 Mar 2008 05:33:34 -0800 (PST) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 6 Mar 2008 08:32:44 -0500 User-Agent: KMail/1.9.7 References: <20080305111237.W50685@maildrop.int.zabbadoz.net> In-Reply-To: <20080305111237.W50685@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803060832.44862.jhb@freebsd.org> Cc: "Bjoern A. Zeeb" , Cristiano Deana 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: Thu, 06 Mar 2008 13:33:59 -0000 On Wednesday 05 March 2008 06:13:06 am Bjoern A. Zeeb wrote: > 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. It's there in mpt_raid.c, but on some mpt chips the mpt_raid stuff probes too early and so it doesn't see any RAID volumes. Bug scottl@ to fix mpt(4). We have a machine at work that has a newer mpt(4) part with the same feature. -- John Baldwin