From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 13 01:03:03 2010 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA55C106566B for ; Wed, 13 Oct 2010 01:03:03 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id A889B8FC0A for ; Wed, 13 Oct 2010 01:03:03 +0000 (UTC) Received: from [127.0.0.1] (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.4/8.14.4) with ESMTP id o9D12xL6073483; Tue, 12 Oct 2010 19:02:59 -0600 (MDT) (envelope-from scottl@samsco.org) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Scott Long In-Reply-To: <911A3B60-559B-471E-90B2-3D7754AC8D17@your.org> Date: Tue, 12 Oct 2010 19:02:59 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <9B56BE59-38FD-46EF-89C3-0A5035BE324C@samsco.org> References: <911A3B60-559B-471E-90B2-3D7754AC8D17@your.org> To: Kevin Day X-Mailer: Apple Mail (2.1081) X-Spam-Status: No, score=-50.0 required=3.8 tests=ALL_TRUSTED, T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: mfi "unexpected sense" when using mfip/smartctl X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Oct 2010 01:03:04 -0000 On Oct 12, 2010, at 3:15 PM, Kevin Day wrote: >=20 > Hey, SCSI people! >=20 > I'm trying to use smartctl (from smartmontools) with an mfi card. I = can kldload mfip, and use smartctl to access SMART data on the member = drives fine. The problem is that each time I do so, I get: >=20 > mfi0: 13501 (340232122s/0x0002/info) - Unexpected sense: PD = 05(e0x04/s0) Path 50030480006deec4, CDB: 85 06 2c 00 da 00 00 00 00 00 = 4f 00 c2 00 b0 00, Sense: c/6d/00 >=20 > I'm assuming this shows up because the RAID controller isn't expecting = the reply to the command that smartctl is sending behind it's back. >=20 > If so, this is pretty harmless, but it looks very very similar to what = happens when there's a serious problem with a drive. Is there a way this = could be muted, or is this indicating that something is actually not = working right?=20 >=20 You're exactly right about the controller firmware seeing a side effect = of running smartctl. You can cross-ref the sense codes at = http://www.t10.org/lists/asc-num.txt if you're interested. The reported = code of "c/6d/00" doesn't make any sense to me, but I guess it's ok. As = long as it's not kicking the array into failover mode, it's harmless. I = think that there is an official way of doing SMART in-band with the = controller that avoids this confusion, I'll look into it. It likely = means that smartctl will need learn how to talk to the /dev/mfi0 = interface, or mfiutil will need to learn about SMART commands. Neither = option is terribly easy. Scott