Date: Sun, 17 Jun 2001 17:36:33 -0700 From: Mike Smith <msmith@freebsd.org> To: Clemens Hermann <haribeau@gmx.de> Cc: scsi@freebsd.org Subject: Re: 'mly' driver update/bugfix snapshot available Message-ID: <200106180036.f5I0aXp03022@mass.dis.org> In-Reply-To: Your message of "Mon, 18 Jun 2001 01:59:52 %2B0200." <20010618015951.A405@homer.local>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi, > > > http://people.freebsd.org/~msmith/RAID/mylex/mly-20010617.tar.gz > > > > If you do try it out, please let me know how you go. > > sure :). I installed the new driver as described in the README and > disabled the old one. The boot went through perfect (no error messages > concerning the enclosure any more). That's a good start. > Then I removed one drive and the spare was rebuilt. Later I re-inserted > the first drive and removed the spare. The rebuild also went through. You say that it "went through", but it sounds like there were problems before it completed. What really happened? > I got many messages during the rebuilt, sorry for not being able to > reproduce them exactly but they did not appear in syslog. There were > several concerning IO-Problems and things like that, I could no longer > access the machine. I really need these messages to be able to help, here. 8( > there seems to be big trouble when accessing the array after the > rebuild. > Finally I rebooted the machine and the syncing before the halt failed. > While rebooting the mylex-bios did not report any problems, the two > system drives and the spare disk were all online. Freebsd made an fsck (yes, > I booted a different kernel) but did not report problems. I would have liked to know what happened if you rebooted with the modified driver at this point. > It might be possible that the error-messages were the result from the > driver trying to write to syslog - I have no Idea why else all the > messages that appered on the screen were not in syslog. Unlikely; the driver just uses the normal kernel printf mechanisms. If /var was on the array, it's possible that writes were failing and thus nothing ended up in the log. A transcript from a serial console would be helpful here. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E 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?200106180036.f5I0aXp03022>