From owner-freebsd-fs@FreeBSD.ORG  Thu Jul 29 18:28:04 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 39073106564A
	for <freebsd-fs@freebsd.org>; Thu, 29 Jul 2010 18:28:04 +0000 (UTC)
	(envelope-from mail@lurking.dk)
Received: from pqueueb.post.tele.dk (pqueueb.post.tele.dk [193.162.153.10])
	by mx1.freebsd.org (Postfix) with ESMTP id F2F608FC13
	for <freebsd-fs@freebsd.org>; Thu, 29 Jul 2010 18:28:03 +0000 (UTC)
Received: from pfepb.post.tele.dk (pfepb.post.tele.dk [195.41.46.236])
	by pqueueb.post.tele.dk (Postfix) with ESMTP id A6FD982D4
	for <freebsd-fs@freebsd.org>; Thu, 29 Jul 2010 20:08:55 +0200 (CEST)
Received: from Terminal (x1-6-c0-3f-0e-de-af-e8.k712.webspeed.dk
	[83.94.233.23])
	by pfepb.post.tele.dk (Postfix) with ESMTP id 07F67F84019
	for <freebsd-fs@freebsd.org>; Thu, 29 Jul 2010 20:08:52 +0200 (CEST)
From: "Casper Jensen" <mail@lurking.dk>
To: <freebsd-fs@freebsd.org>
Date: Thu, 29 Jul 2010 20:08:56 +0200
Message-ID: <000001cb2f49$1ca8e560$55fab020$@lurking.dk>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AcsvR8+V+MWFsBRFRmqm+/fz80QhXA==
Content-Language: da
Subject: areca controller problem
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2010 18:28:04 -0000

Hello

I have a problem with my areca controller running on amd64 based 7.3-REL

On boot it puts out this:
arcmsr0: <Areca SAS 3G Host Adapter RAID Controller (RAID6 capable)
> mem 0xf1000000-0xf1001fff irq 16 at device 0.0 on pci1
ARECA RAID ADAPTER0: Driver Version 1.20.00.17 2010-07-15
ARECA RAID ADAPTER0: FIRMWARE VERSION V1.48 2010-07-08
arcmsr0: [ITHREAD]

which by it self is OK I guess.

Further down the dmesg, when it initializes harddrives, the problem starts:

(probe16:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step

There is NO "da0-da1" in /dev/da*, so I cant mount the raids..

BUT, if I go to the controller config and add a single disk as "passthrough
device" followed by "camcontrol rescan all" in my shell something weird
happens..

This is what dmesg outputs after creating a passthrough device on the
controller followed by camcontrol rescan all:
arcmsr:scsi id=16 lun=0 device lost
(probe16:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step
da1 at arcmsr0 bus 0 target 0 lun 0
da1: <WDC WD20EARS-00MVWB0 R001> Fixed Direct Access SCSI-5 device
da1: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit)
da1: Command Queueing Enabled
da1: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C)
da2 at arcmsr0 bus 0 target 0 lun 1
da2: <Areca archive2 R001> Fixed Direct Access SCSI-5 device
da2: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit)
da2: Command Queueing Enabled
da2: 19073482MB (39062492160 512 byte sectors: 255H 63S/T 2431527C)

So when doing that, the device is suddenly listed and available for mount
(works)...

Im totally lost, and hope its "solveable"

Regards
Casper