Date: Tue, 23 Jun 1998 01:10:34 -0400 (EDT) From: spork <spork@super-g.com> To: hardware@FreeBSD.ORG Subject: CMD CRD-5440 Message-ID: <Pine.BSF.3.96.980623010151.25148A-100000@super-g.inch.com>
next in thread | raw e-mail | index | archive | help
Hi, 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. I'm kind of leaning towards the CMD, as I'm not quite sure the DPT will be trouble-free yet. Today our DPT test box just started beeping on a reboot for no apparent reason. I didn't get a chance to boot DOS to see what was up, and I started wondering how long it would beep like that at a colo with no one to hear it... 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? Is $1800-ish (U.S. $'s) a good price? Has anyone run into problems with the CMD? Is the firmware generally stable? How do the DPT and CMD compare for speed? We're primarily looking for RAID 1, and a few machines will use RAID 5. Any additional comments/horror-stories welcome... Thanks, Charles Charles Sprickman spork@super-g.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?Pine.BSF.3.96.980623010151.25148A-100000>