Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 Mar 2008 16:33:40 +0100
From:      "Cristiano Deana" <cristiano.deana@gmail.com>
To:        "John Baldwin" <jhb@freebsd.org>, Scott <scottl@freebsd.org>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: mpt driver: check raid status
Message-ID:  <d8a4930a0803060733ufe151d5h92d71a3fba597088@mail.gmail.com>
In-Reply-To: <200803060832.44862.jhb@freebsd.org>
References:  <d8a4930a0803050207j218ee20ai74a66082fc560ac9@mail.gmail.com> <20080305111237.W50685@maildrop.int.zabbadoz.net> <200803060832.44862.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

first of all thanks everybody.

this is the output about mpt0, can i help with some other info?

mpt0@pci0:14:8:0:       class=0x010000 card=0x1f081028 chip=0x00541000
rev=0x01 hdr=0x00
    vendor     = 'LSI Logic (Was: Symbios Logic, NCR)'
    device     = 'SAS 3000 series, 8-port with 1068 -StorPort'
    class      = mass storage
    subclass   = SCSI

On Thu, Mar 6, 2008 at 2:32 PM, John Baldwin <jhb@freebsd.org> wrote:
>
> 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
>



-- 
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d8a4930a0803060733ufe151d5h92d71a3fba597088>