From owner-freebsd-scsi@freebsd.org Tue Feb 16 05:39:01 2016 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 772A8AA9249 for ; Tue, 16 Feb 2016 05:39:01 +0000 (UTC) (envelope-from kashyap.desai@broadcom.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 0D1761FF4 for ; Tue, 16 Feb 2016 05:39:01 +0000 (UTC) (envelope-from kashyap.desai@broadcom.com) Received: by mail-lf0-x235.google.com with SMTP id m1so101909544lfg.0 for ; Mon, 15 Feb 2016 21:39:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:content-type; bh=iAJawgYiieoFdQcH/VO6qvLuEmpo+2cYfhtwttxS5e8=; b=RAl83NzqMLv+zCrIQexxS450erFlVJjc8/84t+2XX5/oo44H5zBS6Y6G/TbnyvwuhH 52CrmoIxyz/HoBJn0pU1d/NRIuIWXBfMvtyscUTKSE8UYaOwTZIfAPxa0RFdAlHchw0k z+cSVtEB0QoQNpkskTeqMDk9eBwGBEBTmA+PA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:content-type; bh=iAJawgYiieoFdQcH/VO6qvLuEmpo+2cYfhtwttxS5e8=; b=HEvllp5sTSVsA1dq8fdRhrs97Oec5cGpBZUBb9Ydfc8DToJk91WUqtdXtYgFy33D9K Xm2s47nPSoBtwRJFoRrSw7hLZYmhMIREyzj8ArnrR2hcdTSj/PbKH5rCb2Jp6vKYsVF3 YeqwnarUwr4uGqmbskcdIIkVlLS2sOOj1eaIV+QqZhqhbBZg5lEwymAgPWGogkSXqWH0 93ME/X8W3VMloAyl0POce02rmalFNfDRWJ5PblUaGsL3MMoO1+tK5BNvaxpRRT3MxrtU T5SyE9R2gkUs1z3AJd8aRwMqZTEqSWEX2kd94ceBg9KGJjDvFsPMwOgh9Rob1mGmF86x bmug== X-Gm-Message-State: AG10YOSUHhEpcv0VHUnMiMiksZ/lbCiEig6hwAbunZjoB2uw0yTnWaxRWZcWcGb/YzghAKQu0Nk56USlBMHFxKZU X-Received: by 10.25.31.193 with SMTP id f184mr8775837lff.5.1455601138393; Mon, 15 Feb 2016 21:38:58 -0800 (PST) From: Kashyap Desai References: <6a648d421b6d611b4f6f411b66303017@openmailbox.org> <55de137d1ed81930cfdbee579d881d62@openmailbox.org> In-Reply-To: <55de137d1ed81930cfdbee579d881d62@openmailbox.org> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKkl8+O2HXYvg9L5h3WxDO8ryLRKQD7/aYNnX/od8A= Date: Tue, 16 Feb 2016 11:08:57 +0530 Message-ID: <76cfa84fa2600ca7022cfd9635d06245@mail.gmail.com> Subject: RE: MRSAS driver/LSI MegaRaid 92XX-93XX admin question: When one of the Raid's physical drives break, how is it reported in the logs? To: Tinker , freebsd-scsi@freebsd.org 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: Tue, 16 Feb 2016 05:39:01 -0000 Keeping only freebsd-scsi mailing list > -----Original Message----- > From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd- > scsi@freebsd.org] On Behalf Of Tinker > Sent: Sunday, February 14, 2016 8:44 PM > To: freebsd-stable@freebsd.org; freebsd-scsi@freebsd.org; freebsd- > fs@freebsd.org > Subject: Re: MRSAS driver/LSI MegaRaid 92XX-93XX admin question: When > one of the Raid's physical drives break, how is it reported in the logs? > > (Will send any followup from now only to freebsd-scsi@ .) > > > > Did some additional research and found that the disk failure indeed is > reported in MRSAS' "event log". > > So my final question then is, how do you extract it into userland (in the > absence of an "mfiutil" as the MFI driver has)? Are you using driver from Avago external portal or inbox freebsd kernel ? MRSAS driver has associated application to figure out such event in user space. Can you please post your query to Avago/Boradcom support team. > > > > Details below. Thanks. > > On 2016-02-14 19:59, Tinker wrote: > [...] > > > http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/3rd- > party/lsi/mrsas/userguide/LSI_MR_SAS_SW_UG.pdf > > on page 305, that is section "A.2 Event Messages" - I don't know for > > what LGI chip this document is, but, it does not list particular event > > message very clearly for when an individual underlying disk would have > > broken, I don't even see any event for when a hot spare would be taken > > in use! > > > Wait - this page: > > https://www.schirmacher.de/display/Linux/Replace+failed+disk+in+MegaR > AID+array > > (and also > http://serverfault.com/questions/485147/drive-is-failing-but-lsi-megaraid- > controller-does-not-detect-it > ) > > gives an example of how the host system learns about broken disks: > > > Code: 0x00000051 .. Event Description: State change on VD 00/1 from > OPTIMAL(3) to DEGRADED(2) > > > Code: 0x00000072 .. Event Description: State change on PD 05(e0xfc/s0) > from ONLINE(18) to FAILED(11) > > (unclean disk broken seems to be shown as:) > > Code: 0x00000071 .. Event Description: Unexpected sense: PD 05(e0xfc/s0) > Path 4433221103000000, CDB: 2e 00 3a 38 1b c7 00 00 01 00, Sense: > b/00/00 > > > And this version of the LSI documentation > > http://hwraid.le-vert.net/raw- > attachment/wiki/LSIMegaRAIDSAS/megacli_user_guide.pdf > > gives a clearer definition of the physical and virtual drive states in > "1.4.16 Physical Drive States" > and "1.4.17 Virtual Disk States" on pages 1-11 to 1-12. > > So as we see, a physical drive breaking would > > * "FAILED" the physical drive > > * "DEGRADED" the Virtual Drive (that is the logical exported drive) > (from "OPTIMAL") > > > So then, it was indeed the card's "event log" that contains this info. > > > > Last question then would only be then, *where* FreeBSD's MRSAS driver > sends its event log? > > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org"