Areca weirdness
Andre Oppermann
andre at freebsd.org
Tue Dec 11 13:39:13 PST 2007
Scott Long wrote:
> For the Areca driver, it's harmless. I still haven't narrowed
> down the actual problem, unfortunately.
I see the same on a new box with FreeBSD 7.0BETA4 AMD64. Unfortunately
it just stops and hangs here:
arcmsr0: <Areca SATA Host Adapter RAID Controller (RAID6 capable)> mem
0xfdbff000-0xfdbfffff,0xfd400000-0xfd7fffff irq 16 at device 14.0 on pci10
ARECA RAID ADAPTER0: Driver Version 1.20.00.14 2007-2-05
ARECA RAID ADAPTER0: FIRMWARE VERSION V1.43 2007-4-17
arcmsr0: [ITHRRAD]
...
Waiting 5 seconds for SCSI devices to settle
(probe23:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step
[hangs...]
The controller is an ARC-1220 PCI-Express with 8 SATA ports. The
firmware is the newest according to their website. Connected are
4 Seagate 750GB SATA drives (the ES 24x7 variant). With 6.3RC1
AMD64 it works just fine.
--
Andre
> Scott
>
> Philip Murray wrote:
>
>> Hi,
>>
>> After the recent commit of the new Areca (arcmsr) driver, I get this
>> output during boot:
>>
>> arcmsr0: <Areca SATA Host Adapter RAID Controller (RAID6 capable)
>> > mem 0xfc7ff000-0xfc7fffff,0xfc000000-0xfc3fffff irq 31 at device
>> 14.0 on pci2
>> ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07
>> ARECA RAID ADAPTER0: FIRMWARE VERSION V1.43 2007-4-17
>> arcmsr0: [ITHREAD]
>>
>> .... snip ....
>>
>> Waiting 5 seconds for SCSI devices to settle
>> (probe16:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step
>> ^^^ This line here ^^^
>>
>> da0 at arcmsr0 bus 0 target 0 lun 0
>> da0: <Areca ARC-1120-VOL#00 R001> Fixed Direct Access SCSI-5 device
>> da0: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit)
>> da0: 76293MB (156248064 512 byte sectors: 255H 63S/T 9725C)
>> da1 at arcmsr0 bus 0 target 0 lun 1
>> da1: <Areca ARC-1120-VOL#01 R001> Fixed Direct Access SCSI-5 device
>> da1: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit)
>> da1: 2784727MB (5703121920 512 byte sectors: 255H 63S/T 355002C)
>>
>>
>> Not sure if it's anything to worry about (as I have no idea what it
>> means), but doesn't seem to affect functionality at all
>>
>> Cheers
>>
>> Phil
>> _______________________________________________
>> freebsd-current at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to
>> "freebsd-current-unsubscribe at freebsd.org"
>
>
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>
>
More information about the freebsd-current
mailing list