From owner-freebsd-i386@FreeBSD.ORG Wed Sep 6 16:06:53 2006 Return-Path: X-Original-To: freebsd-i386@FreeBSD.org Delivered-To: freebsd-i386@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 384BA16A4DD; Wed, 6 Sep 2006 16:06:53 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from mail.sailorfej.net (mail.sailorfej.net [66.93.72.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 665D243D6B; Wed, 6 Sep 2006 16:06:47 +0000 (GMT) (envelope-from jeff@sailorfej.net) Received: from [192.168.150.100] (c-24-20-239-104.hsd1.or.comcast.net [24.20.239.104]) (authenticated bits=0) by mail.sailorfej.net (8.13.4/8.13.4) with ESMTP id k86FttZk005229 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Sep 2006 08:55:56 -0700 (PDT) (envelope-from jeff@sailorfej.net) Message-ID: <44FEF17F.2050909@sailorfej.net> Date: Wed, 06 Sep 2006 09:04:15 -0700 From: Jeffrey Williams User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: bug-followup@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.6 required=6.0 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.sailorfej.net Cc: freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org, dmartin@euitt.upm.es Subject: Re: i386/100160: [mfid] Perc5i: additional symptomatic info on virtual disk detection issue X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Sep 2006 16:06:53 -0000 I don't know if anyone specifically is working on this, but just tried to install FreeBSD 6.1 from CD on a Dell 2950 with the PERC 5/i SAS controller. This server was originally configured with two hardware RAID virual disks, the first was RAID 1 with two 36GB drives, and the second was RAID 5 with three 72 GB drives. Just like the original PR, the first was detected and identified in the the installer volume setup as both mfid0 and mfid1. In order to try and work around the problem and just get the machine up and running, I tried deleting the RAID 1 virtual disk with the intention of installing everything to the RAID 5 virtual disk, however, with the first virtual disk removed, no drives where detected at all. Next I will be trying removing the physical drives original used in the RAID 1 virtual disk, and re-initializing the RAID 5 array. I will provide an update if successful. In the meantime if anybody else is aware of another work around of fix for this, I appreciate hearing about it. If a patch comes out soon, I will be happy to provide testing, but I have a small window as this server was being implemented as an emergency replacement for another server. Thanks, Jeffrey Williams