Date: Mon, 22 Jun 1998 22:05:19 -0700 From: Mike Smith <mike@smith.net.au> To: spork <spork@super-g.com> Cc: hardware@FreeBSD.org Subject: Re: CMD CRD-5440 Message-ID: <199806230505.WAA00729@antipodes.cdrom.com> In-Reply-To: Your message of "Tue, 23 Jun 1998 01:10:34 EDT." <Pine.BSF.3.96.980623010151.25148A-100000@super-g.inch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > We've been having a hard time deciding which RAID solution to go with, and > are currently torn between the DPT controller and a CMD CRD-5440. ... > So my questions are: > > The CMD provides a serial interface for setup/troubleshooting. I assume > we could write some simple script to "look" at it every now and again and > verify that there are no failed drives. Has anyone else done this? How > do most people detect a failure when the machine is at a remote location? You would probably want to use something like expect (ports/lang/expect and the book 'Exploring Expect') to talk to it. If you polish it a bit, it might even make for a port of its own. 8) > Has anyone run into problems with the CMD? Is the firmware generally > stable? There have been lots of happy testimonials about them, and they're marketted sufficiently successfully that I suspect they're pretty solid. Actually, I was looking at one of their units at Usenix; they pack 7 PCI slots, the CPU and memory into a 5.25" FH drive form factor - yeow! -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806230505.WAA00729>