> harddrive while running FreeBSD. The controler reacts on this with a wild
> beeping and beeping does not stop until the array has been rebuild or
> checked on consistency. But there was no message of any kind of error or
> drive failure or that the controler moans due some drive failures. Is this
> normal or is there a special way to check this?
The driver doesn't (at this point in time) have any way of reporting
array status changes. I have the information necessary to deal with this
to hand, but have not had time to implement it. 8(
AMI also have a FreeBSD port of their MegaManager software, but I'm not
sure what their plans might be with regards to releasing it.
> Another question regards to the way the controler acts with its
> harddrives. How can I figure out in which way the controler accesses its
> drives? Means: how to check whether Ultra2/160m, FAST, Wide/Ultra Wide or
> simply Ultra 16 Bit is used as protocol? The reason why I want to know
> this is explained in part two ...
The driver ought to be able to work this out as well. See above inre
time.
I don't have any answers about the remainder, I'm sorry. I'm moving
right now and all my controllers are boxed, but it really does sound like
you have major termination issues. 8(
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
