[CLUG] Adaptec 2000s

[adam]

Ronan Kirby wrote:
> Are you absolutely sure that it's:
> 
> 	(1) a 2000s series controller (Ultra 160)?
>
I'm pretty sure, although I have to admit I can't remember why! It's in
an old (not that old, but not new either) Encom box.

> 	(2) SCSI?
> 
The disks are SCSI? Jesus, now I have to check!

>>>> Did you need to install a particular driver or was it recognised?
> 
> What kind of problems are you seeing, or what errors are you seeing 
> (assuming your question was not a preemptive one). Is it even trying to 
> load a module for it. I don't see anything in the module tables that I can 
> identify on glance as being an Adaptec 2000s. What does dmesg have to say 
> about it?
> 
I just get a "no disk" error in the install. They're showing up (well,
one is showing up, RAID 1) in the Adaptec wotsit though.

> Can you show us the output of:
> 
> 	cat /proc/scsi/scsi
> 
I doubt it.

> If this is a new deployment, it's quite likely going to be cheaper for you 
> in the long run to put in a cheap and cheerful new controller when priced 
> against your time, not to mention the performance and reliability gains.
> 
I'll try loading the other two Adaptec drivers from the CD first, but
yes, I'm guessing that might be the route I have to take.

Still can't get the other machine working. RAM was part of the problem,
in that placement was an issue (despite what the board manual said), but
I still have an amber light on it.

> PS: Right, I guess Adam got that old kit he was looking for then ;-)
>
Kind of. I already had five, but none of them are working. I reckon two
of them are EOL, and I'm not sure the other three can be saved.

Another four came from a completely different source, but one is close
to death, another is the size of house, and I think I'm only be able to
make one good one out of these two.

So I'm still looking. :)

adam