Ed,
Your work-around works on 7-stable as of this morning.
I have quite a few 2200S equipped systems that I am transitioning from 6.X
to 7-stable and aaccli is necessary to be able to insert/remove drives and
initialize them into storage arrays.
sysutils/arcconf says it needs
On Wed, Apr 02, 2008 at 10:16:17AM -0700, Chris Timmons wrote:
Ed,
Your work-around works on 7-stable as of this morning.
Excellent! I've actually committed a better fix to HEAD now (aac.c
revision 1.137). The diffs[1] should apply cleanly to RELENG_7 and
RELENG_6 I believe, and I plan to
The diff applied cleanly except for the __FBSDID().
With this new revision, I can still run batch scripts as shown below and
get the correct output from aaccli. Unfortunately, if you manually invoke
aaccli and type in open aac0, all terminal input is locked. The only
way to recover the
On Wed, Jan 02, 2008 at 03:54:50AM -0500, Mike Andrews wrote:
On RELENG_7 dated 2007-12-15 (BETA4), aaccli fails with the following
error; arcconf continues to work fine:
Command Error: The miniport device driver is too old to work with the
current AFAAPI.DLL.
I suspect Adaptec has
Vivek Khera wrote:
On Jan 2, 2008, at 12:45 PM, Ed Maste wrote:
I'm not aware of any reason to avoid Adaptec RAID cards specifically on
amd64 now; there were a number of problems in the past but they should
be addressed now.
My main concern is that there is no *reliable* way to monitor the
On Jan 3, 2008, at 2:07 PM, Mike Andrews wrote:
arcconf seems to be reliable (and a native amd64 binary), except for
the aforementioned hanging-on-exit issue with -RC1. On -BETA4 it's
fine. Google for check_icp if you need a Nagios plugin written
around arcconf (it needs only minor edits
I'm seeing some regressions in the various management tools for Adaptec
AAC cards on FreeBSD 7.0-RC1 amd64.
I'm trying to use both the 32-bit FreeBSD aaccli binary from the
sysutils/aaccli port, and also the 64-bit FreeBSD arcconf from the
sysutils/arcconf port (v5.20.17414). The card is an
On Jan 2, 2008, at 3:54 AM, Mike Andrews wrote:
Command Error: The miniport device driver is too old to work with
the current AFAAPI.DLL.
In my experience, this was caused by the firmware rev of the adaptec
card. Basically, the combination of FreeBSD, amd64, and Adaptec RAID
cards is
On Wed, Jan 02, 2008 at 10:19:15AM -0500, Vivek Khera wrote:
On Jan 2, 2008, at 3:54 AM, Mike Andrews wrote:
Command Error: The miniport device driver is too old to work with
the current AFAAPI.DLL.
In my experience, this was caused by the firmware rev of the adaptec
card.
On Wed, 2 Jan 2008, Ed Maste wrote:
On Wed, Jan 02, 2008 at 10:19:15AM -0500, Vivek Khera wrote:
On Jan 2, 2008, at 3:54 AM, Mike Andrews wrote:
Command Error: The miniport device driver is too old to work with
the current AFAAPI.DLL.
In my experience, this was caused by the firmware rev
Ed Maste wrote:
On Wed, Jan 02, 2008 at 10:19:15AM -0500, Vivek Khera wrote:
On Jan 2, 2008, at 3:54 AM, Mike Andrews wrote:
Command Error: The miniport device driver is too old to work with
the current AFAAPI.DLL.
In my experience, this was caused by the firmware rev of the adaptec
On Jan 2, 2008, at 12:45 PM, Ed Maste wrote:
I'm not aware of any reason to avoid Adaptec RAID cards specifically
on
amd64 now; there were a number of problems in the past but they should
be addressed now.
My main concern is that there is no *reliable* way to monitor the
status of an
On Jan 2, 2008, at 1:06 PM, Mike Andrews wrote:
In my experience, this was caused by the firmware rev of the adaptec
card. Basically, the combination of FreeBSD, amd64, and Adaptec
RAID
cards is a bad thing for production systems, and IMO should be
avoided.
Well, yeah, the error message
13 matches
Mail list logo
