From nobody@FreeBSD.org  Wed Jul 12 10:33:22 2006
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9DFC616A4DA
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 12 Jul 2006 10:33:22 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8D00543D67
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 12 Jul 2006 10:33:11 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k6CAXA8T084924
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 12 Jul 2006 10:33:10 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id k6CAXAWD084923;
	Wed, 12 Jul 2006 10:33:10 GMT
	(envelope-from nobody)
Message-Id: <200607121033.k6CAXAWD084923@www.freebsd.org>
Date: Wed, 12 Jul 2006 10:33:10 GMT
From: Daniel Martin-Fabiani <dmartin@euitt.upm.es>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Perc5i: FreeBSD doesn't recognize more than one virtual disk created at the controller BIOS
X-Send-Pr-Version: www-2.3

>Number:         100160
>Category:       i386
>Synopsis:       [mfid] Perc5i: FreeBSD doesn't recognize more than one virtual disk created at the controller BIOS
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    linimon
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul 12 10:40:09 GMT 2006
>Closed-Date:    Tue Jul 17 08:51:01 GMT 2007
>Last-Modified:  Tue Jul 17 08:51:01 GMT 2007
>Originator:     Daniel Martin-Fabiani
>Release:        6.1
>Organization:
Universidad Politecnica de Madrid
>Environment:
>Description:
If you create two RAID0 with different disks at the controller BIOS, FreeBSD
detects two disks (mfid0 and mfid1), but both point to the same virtual disk,
and the second device is unreachable.

This happens at sysinstall time and later when the whole OS is installed.
>How-To-Repeat:
Create two logical devices at Perc5i BIOS RAID controller.
>Fix:

>Release-Note:
>Audit-Trail:

From: Jeffrey Williams <jeff@sailorfej.net>
To: bug-followup@FreeBSD.org
Cc: freebsd-i386@FreeBSD.org, freebsd-stable@FreeBSD.org, dmartin@euitt.upm.es
Subject: Re: i386/100160: [mfid] Perc5i: additional symptomatic info on virtual
 disk detection issue
Date: Wed, 06 Sep 2006 09:04:15 -0700

 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

From: "Bucky Jordan" <bjordan@lumeta.com>
To: "Jeffrey Williams" <jeff@sailorfej.net>,
	<bug-followup@FreeBSD.org>
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
Date: Wed, 6 Sep 2006 12:39:35 -0400

 >In the meantime if anybody else is aware of another work around of fix=20
 >for this, I appreciate hearing about it. =20
 
 I've got almost the same setup- 6.1 amd64 RELEASE, a 2950 with 6 drives
 attached to the Perc5/I SAS Raid controller. Right now I've got the
 whole thing configured as a RAID5x6 disks and it seems to be working
 fine.=20
 
 I was able to also create smaller RAID sets (for example, a 4 disk
 RAID10) without an issue, and I did not have to remove extra drives.
 
 Someone (on -hardware I think) mentioned that the problem recognizing
 multiple virtual volumes is addressed in 6-stable, but I have not had
 the chance to try it out. I will post the results if/when I do.
 
 - Bucky

From: Paul Saab <ps@freebsd.org>
To: Bucky Jordan <bjordan@lumeta.com>
Cc: Jeffrey Williams <jeff@sailorfej.net>,  bug-followup@FreeBSD.org, 
 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
Date: Wed, 06 Sep 2006 09:46:59 -0700

 revision 1.11
 date: 2006/06/20 22:41:44;  author: ps;  state: Exp;  lines: +77 -202
 Instead of using scsi probes to do device discovery, use the firmware
 commands to grab the device listing.  This resolves issues using
 multiple volumes, where each volume was actually internally pointing
 to target 0.
 
 
 Bucky Jordan wrote:
 >> In the meantime if anybody else is aware of another work around of fix 
 >> for this, I appreciate hearing about it.  
 >>     
 >
 > I've got almost the same setup- 6.1 amd64 RELEASE, a 2950 with 6 drives
 > attached to the Perc5/I SAS Raid controller. Right now I've got the
 > whole thing configured as a RAID5x6 disks and it seems to be working
 > fine. 
 >
 > I was able to also create smaller RAID sets (for example, a 4 disk
 > RAID10) without an issue, and I did not have to remove extra drives.
 >
 > Someone (on -hardware I think) mentioned that the problem recognizing
 > multiple virtual volumes is addressed in 6-stable, but I have not had
 > the chance to try it out. I will post the results if/when I do.
 >
 > - Bucky
 > _______________________________________________
 > freebsd-stable@freebsd.org mailing list
 > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
 >
 >   

From: Doug Ambrisko <ambrisko@ambrisko.com>
To: Jeffrey Williams <jeff@sailorfej.net>
Cc: bug-followup@freebsd.org, 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
Date: Thu, 7 Sep 2006 10:50:19 -0700 (PDT)

 Jeffrey Williams writes:
 | 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.
 
 Upgrade the mfi driver to -stable.
 
 Doug A.
State-Changed-From-To: open->feedback 
State-Changed-By: linimon 
State-Changed-When: Mon Jul 9 15:58:52 UTC 2007 
State-Changed-Why:  
To submitter: it sounds like this issue was fixed in time for 6.2.  Are 
you still seeing the problem? 


Responsible-Changed-From-To: freebsd-i386->linimon 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Mon Jul 9 15:58:52 UTC 2007 
Responsible-Changed-Why:  

http://www.freebsd.org/cgi/query-pr.cgi?pr=100160 
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Tue Jul 17 08:50:49 UTC 2007 
State-Changed-Why:  
Apparently this was fixed for 6.2. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=100160 
>Unformatted:
