From owner-freebsd-scsi Fri Dec 14 10:24:41 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from anubis.nosc.mil (anubis.nosc.mil [198.253.16.34]) by hub.freebsd.org (Postfix) with ESMTP id 4B92437B405 for ; Fri, 14 Dec 2001 10:24:35 -0800 (PST) Received: from huckabeec (sc032ws139.chs.spawar.navy.mil [198.253.32.139]) by anubis.nosc.mil (8.9.3/8.9.3) with SMTP id NAA26594; Fri, 14 Dec 2001 13:21:02 -0500 (EST) Message-ID: <008e01c184cc$8dffc930$90b411ac@huckabeec> From: "Craig Huckabee" To: "Tom Samplonius" Cc: References: Subject: Re: mly driver question ? Date: Fri, 14 Dec 2001 13:24:22 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > No, I'd use a plain SCSI card to test that. It could be your disk(s) > conflict with the SCSI id of the SAF-TE device, or there is a termination > problem (bus is terminated before SAF-TE device). So try it without disks > connected as well. I was trying just that when your e-mail arrived. I used the onboard Adaptec controllers, and they didn't see it. I used another add-on controller, it didn't see it. So, I called IN-WIN to confirm there wasn't some deep voodoo that had to be done to the backplane. They said no, and that it should show up in the SCSI scans so my case must be defective. I just finished tearing the server down and making arrangements to have it sent back for replacement under RMA. > > It has always been my impression that the Mylex card hides SAF-TE > devices from the host, in order that there be no conflicts over control of > the SAF-TE device. Usually if you have a SAF-TE on a Mylex (mly) card, > you will get a few "Device gone" messages with the ID of the SAF-TE > device(s). Well, that was the confusing part of this - I saw messages telling me that a device had been removed, but never any signs that I had reinserted a drive back into the array. And thus the rebuilds never got started. Anyway, I appreciate all the help - hopefully when the replacement arrives it will "just work". Thanks, Craig / Craig Huckabee | e-mail: huck@spawar.navy.mil / / Code 71B-CH | phone: (843) 218 4446 / / SPAWAR Systems Center | close proximity: "Hey You!" / / Charleston, SC | ICBM: 32.78N, 79.93W / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message