From owner-freebsd-questions Sun Dec 17 4:44:21 2000 From owner-freebsd-questions@FreeBSD.ORG Sun Dec 17 04:44:16 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id 5E3A437B400 for ; Sun, 17 Dec 2000 04:44:15 -0800 (PST) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.11.1/8.11.1/Kp) with ESMTP id eBHCi1u37831; Sun, 17 Dec 2000 12:44:01 GMT Message-ID: <3A3CB4EE.49296E30@tdx.co.uk> Date: Sun, 17 Dec 2000 12:43:26 +0000 From: Karl Pielorz Organization: The Digital eXchange X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Noor Dawod , freebsd-questions@FreeBSD.ORG Subject: Re: Adaptec SCSI RAID 2100S problems. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Noor Dawod wrote: > Now, the problems start... One out of 3-4 reboots, the 2100S card > manages to identify all disks, reads the configured settings, and boots > the system (into FreeBSD which I managed to install on a previous reboot > under the configured Array). The other attempts do not succeed, and on > the Disk Cage I see 3 red lights out of 4, indicating that the 2100S > failed to identify disks in those bays. In addition, I hear a > high-volume alarm coming out of the 2100S card indicating a problem. Hi, This doesn't really have a lot to do with FreeBSD?! - Sounds like a hardware problem... You said the card was running SMOR, which means it sounds like it's a re-badged DPT RAID controller (Adaptec bought DPT). I've had similar problems with these before... Make sure the card is running the latest firmware, and if that still doesn't fix the problem - double check cabling, termination etc. - You can also try setting the "Delay" option in SMOR to a higher value, this worked for one of our set-ups... Alternatively, as you pointed out - it could be the different firmware on one of the drives, but at least you've got something to try now :) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message