From owner-freebsd-fs@FreeBSD.ORG Mon Jun 19 16:29:55 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCF4316A474; Mon, 19 Jun 2006 16:29:55 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 009F243D72; Mon, 19 Jun 2006 16:29:25 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k5JGTHGU084489; Mon, 19 Jun 2006 10:29:23 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4496D0D8.8040705@samsco.org> Date: Mon, 19 Jun 2006 10:29:12 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ensel Sharon References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-fs@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Please help - adaptec 2820sa not allowing installation X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2006 16:29:56 -0000 Ensel Sharon wrote: > I did all my due diligence, I contacted freebsd-fs and _made sure_ that > even though the 2820sa is not listed by name in the HCL, that I could take > a 6.1-RELEASE cd and install freebsd on a 2820sa. > > I was _assured_ that these cards are supported in 6.1-RELEASE, that all is > well, and I could install and that was that. > No, you were not assured, at least not by when we discussed this last week. I told you that I personally did not guarantee that it worked, only that I had heard reports that it did. You have two variables here. One is that it's an array that is larger than what the aac driver has supported in the past. Second is that it's RAID-6. Both of these variables should be handled by the aac driver update that happened last year, but again, I couldn't validate it, so I can only go with the reports of others. As others suggested, you need to experiment with simplier configurations. This will help us identify the cause and hopefully implement a fix. No one is asking you to throw away money or resources. Since you've already done the simple test with a single drive, could you do the following two tests: 1. RAID-5, full size (whatever >2TB value you were talking about). 2. RAID-6, <2TB. From there, I'll figure out what needs to be done to get it fully working for you. Scott