MRSAS driver/LSI MegaRaid 92XX-93XX admin question: When one of the Raid's physical drives break, how is it reported in the logs?

Tinker tinkr at
Sun Feb 14 15:13:48 UTC 2016

(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)?

Details below. Thanks.

On 2016-02-14 19:59, Tinker wrote:
> 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:

(and also 

gives an example of how the host system learns about broken disks:

Code: 0x00000051 .. Event Description: State change on VD 00/1 from 

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: 

And this version of the LSI documentation

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?

More information about the freebsd-stable mailing list