Date: Thu, 17 May 2001 12:02:21 -0500 (CDT) From: Chris Dillon <cdillon@wolves.k12.mo.us> To: Clemens Hermann <haribeau@gmx.de> Cc: <freebsd-scsi@FreeBSD.ORG>, <msmith@wolves.k12.mo.us> Subject: Re: mly problem (AR 170) Message-ID: <Pine.BSF.4.32.0105171149260.5420-100000@mail.wolves.k12.mo.us> In-Reply-To: <20010517114314.A1714@ramses.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 17 May 2001, Clemens Hermann wrote: I've copied Mike Smith on this, the author of the driver, since he will hopefully know more information about the error messages you're getting. > Am 16.05.2001 um 15:46:50 schrieb Chris Dillon: > > Hi Chris, > > > > There does no such disk exist, according to the controller-setup > > > this is the processor. Are these messages a problem? > > > > Shouldn't be. > > could you give me a hint what this messages mean? I can't even remember what you said they were, now. Would have been good to keep them in the reply. :-) > > No userland tools exist yet to manage the controller and its devices, > > that I know of. With a managed hot-plug enclosure, I'm not sure that > > you would even need any. I do know that the driver (via the kernel) > > will emit a warning when a RAID array goes critical. You can test it > > yourself by simply removing a drive from your redundant array, > > yes it works but I get the following lies in syslog: > > mly0: physical device 0:0 selection timeout > mly0: logical device 0(da0) critical > mly0: unknown event code-61 > mly0: unknown event code-162 > > any ideas what the last two lines mean? No idea. If you re-insert the drive, does it begin a rebuild? If it doesn't, make sure you actually have automatic rebuild enabled in the controller config, and that it is set up properly for your managed enclosure. Mike will hopefully know wether those "unknown events" are potentially serious or just informational flak. > Furthermore: Will I get the messages only in syslog or will they > appear in the FreeBSD daily report mails? If not, is there a way > to get them there? Anything printed by the kernel to the console will also show up in /var/log/messages and possibly even /var/log/console.log, depending on how you have syslogd set up. They will be sent to you in the daily security output showing the daily dmesg difference, assuming that the dmesg buffer isn't so overrun with other messages that they get lost. The best way to get that information in the mail is to write your own script that runs along with the daily periodic stuff and searches for output from the mly driver. Better yet, have it check the logs every hour or so and mail you or page you if it finds something. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.32.0105171149260.5420-100000>