Date: Wed, 18 Jun 2008 17:20:40 +0300 From: Stefan Lambrev <stefan.lambrev@moneybookers.com> To: freebsd-stable@freebsd.org Subject: Re: Management interface for cards powered by the "mfi" driver? Message-ID: <485919B8.20705@moneybookers.com> In-Reply-To: <20080618140236.GA23551@FS.denninger.net> References: <20080508050550.GA76170@FS.denninger.net> <E1Ju2Rt-000MNF-1k@dilbert.ticketswitch.com> <20080617012053.GA82316@FS.denninger.net> <20080618041530.GA81315@FS.denninger.net> <20080618050530.GA75831@citylink.fud.org.nz> <20080618053605.GA27112@FS.denninger.net> <4858E3A4.2000208@moneybookers.com> <20080618140236.GA23551@FS.denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Karl, Karl Denninger wrote: > On Wed, Jun 18, 2008 at 01:29:56PM +0300, Stefan Lambrev wrote: > >> Karl Denninger wrote: >> >>> On Tue, Jun 17, 2008 at 10:05:31PM -0700, Andrew Thompson wrote: >>> >>> >>>> On Tue, Jun 17, 2008 at 11:15:30PM -0500, Karl Denninger wrote: >>>> >>>>>> Intel SRCSAS18E card in it, and well, the only way I can describe it is >>>>>> "oh >>>>>> my GOD!" >>>>>> >>>>>> >>>>> Ok, another followup! >>>>> >>>>> Is there a mangement interface program for the "mfi" driver somewhere? I >>>>> rooted around in "ports" but didn't find one, nor on the base system. >>>>> >>>>> The Linux ones want to talk to the "amr" driver which is the older LSI >>>>> Logic >>>>> MegaRAID boards, not the newer ones that the mfi driver talks to. >>>>> >>>>> No management tool = el-sucko, because you can't rebuild a failed disk or >>>>> even shut the alarm on the board off! >>>>> >>>>> >>>> Its sysutils/linux-megacli. >>>> >>>> >>> Nope. It builds and installs but doesn't work (already tried this one.) >>> >>> Attempting to ask it for the number of boards returns "0". >>> >>> This may have something to do with changes made to the device structure(s) >>> in FreeBSD-7 (I don't have a 6 machine to test on any more) but it >>> definitely does not function. >>> >>> >> It works fine for me on very recent 7-STABLE. >> >> megacli -CfgDsply -a0 >> >> ============================================================================== >> Adapter: 0 >> Product Name: PERC 5/i Integrated >> Memory: 256MB >> BBU: Present >> Serial No: 12345 >> ============================================================================== >> -cut- >> >> megacli -AdpAllInfo -aALL also works without a problem. >> >> 7.0-STABLE-200805 FreeBSD 7.0-STABLE-200805 #0: Sun May 11 11:55:15 UTC >> 2008 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >> >> Did you follow all steps from ports/sysutils/linux-megacli/pkg-message ? >> Though I think there is a small bug in the port (maintainer CCed) >> It wants compat.linux.osrelease=2.6.12, but I think it should be >> compat.linux.osrelease=2.6.16 ? >> Just for reference I installed it with OVERRIDE_LINUX_BASE_PORT=f8 >> I think you are confusing mega-cli with megamgr (which is the one that >> work with amr driver) >> > > dbms# megacli -CfgDsply -a0 > > Failed to get ControllerId List. > Failed to get CpController object. > dbms# > Sorry if you already answer this and I missed it, but do you have mfi_linux, linprocfs, linsysfs loaded as modules (or build in kernel)? Also do you have mounted: linprocfs on /usr/compat/linux/proc (linprocfs, local) linsysfs on /usr/compat/linux/sys (linsysfs, local) If this is done I'm really out of ideas. > But the card is definitely there; this is what it last logged when I manually > yanked one of the mirrored drives, then shut down and told it to rebuild > from the GUI before boot and let it go on its way: > > mfi0: 501 - PD 10(e252/s1) progress 99% seconds 7017s: Rebuild progress on > PD 0a(e0xfc/s1) is 98.94%(7017s) > mfi0: 502 - PD 10(e252/s1) progress 100% seconds 7158s: Rebuild progress on > PD 0a(e0xfc/s1) is 99.94%(7158s) > mfi0: 503 - PD 10(e252/s1) event: Rebuild complete on PD 0a(e0xfc/s1) > mfi0: 504 - VD 00/0 state prior 2 new 3: State change on VD 00/0 from > DEGRADED(2) to OPTIMAL(3) > mfi0: 505 - VD 00/0 event: VD 00/0 is now OPTIMAL > mfi0: 506 - PD 10(e252/s1) state prior 20 new 24: State change on PD > 0a(e0xfc/s1) from REBUILD(14) to ONLINE(18) > > Oook! > > So we have a card that the driver is perfectly happy with, but the > management interface can't find. > > Note that this is the Intel board; I grabbed the Intel version of the > software for Linux (which appears to be essentially the same code but under > Intel's name), set the branding so the Linux emulator would play nice, and > got the same thing: > > dbms# ./CmdTool2 -Cfgdsply -a0 > > Failed to get ControllerId List. > Failed to get CpController object. > dbms# > > Hmmmm... this is on a new machine that I loaded 7-RELEASE on and then > grabbed the CVS tree and pulled a -rRELENG_7 on and rebuilt. > > Let me dig around a bit..... I wonder if I got a "funny" in here... > looking at kernel versions, it appears I might. > > If so, that's going to be an interesting problem (as in "how did that happen?") > to figure out. > > uname -v is returning: > FreeBSD 7.0-CURRENT-200608 #0: Mon Jun 16 20:54:25 UTC 2008 karl@dbms.denninger.net:/usr/obj/usr/src/sys/GENERIC > > How'd that happen with the tag "RELENG_7" in the tag? (and yes, it IS > in there in the CVS directory in the "Tag" file....) > > -- Karl Denninger > karl@denninger.net > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Best Wishes, Stefan Lambrev ICQ# 24134177
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?485919B8.20705>