areca controller problem

Casper Jensen mail at lurking.dk
Thu Jul 29 18:28:04 UTC 2010


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



More information about the freebsd-fs mailing list