kern/76792: vinum not working with aac disk devices

[Gil Kloepfer]

>Number:         76792
>Category:       kern
>Synopsis:       vinum not working with aac disk devices
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 28 15:50:14 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Gil Kloepfer
>Release:        FreeBSD 4.11-RELEASE i386
>Organization:
UT Applied Research Laboratories
>Environment:
System: FreeBSD  4.11-RELEASE FreeBSD 4.11-RELEASE #0: Fri Jan 21 17:21:22 GMT 2005 root at perseus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

	4.11-RELEASE vanilla install, right out of the box
	Dell PowerEdge 2650 with PERC 3/Di (Adaptec) controller
	Two RAID containers, both with a pair of 60G disks in RAID1 config

	4.10-RELEASE also fails in the same manner.

>Description:

	After relabeling the disk and setting the appropriate
	FreeBSD partitions to vinum, creating vinum drive fails
	with messages:

            1: drive disk0 device /dev/aacd0s1f
         ** 1 Can't initialize drive disk0: Operation not supported by device
            2: drive disk1 device /dev/aacd1s1f
         ** 2 Can't initialize drive disk1: Operation not supported by device

	I have actually tried this multiple times in multiple RAID
	configurations with the same results (incidentally with a RAID5
        container, I coudln't even install FreeBSD).

>How-To-Repeat:

	1. Create RAID1 container with Dell PERC 3/Di controller.
	2. Partition the disk as:  500M root, 1G swap, 1G /usr   (one slice)
	3. Install FreeBSD
	4. Relabel the disk with the remaining disk space allocated to
	   partition "f" (root will be a, swap b, usr e), type vinum
	5. Create file (vinum.conf, for example) with:

              drive disk0 device /dev/aacd0s1f

        6. Execute:   vinum create -f vinum.conf

	I have also tried this with FreeBSD 4.10 as well, and it failed
	in the same manner (I am currently running 4.10-RELEASE on another
	system with a standalone SATA drive with vinum without any
	problems).

>Fix:
	Have not found a workaround or fix at this time aside from
	not using vinum.
>Release-Note:
>Audit-Trail:
>Unformatted: