From: James Bottomley <James.Bottomley@SteelEye.com>
To: Gabriel Gomiz <gomita@cooperativaobrera.com.ar>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Symbios-NCR 6285-3621 + Adaptec 2944W multilun problem
Date: Fri, 12 May 2006 12:22:52 -0500 [thread overview]
Message-ID: <1147454573.3769.32.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <4464C384.2050605@cooperativaobrera.com.ar>
On Fri, 2006-05-12 at 14:19 -0300, Gabriel Gomiz wrote:
> You were right. The server was attached to controller "B" of the array.
> I attached it to controller "A" and it is working ok with 2.6.16.13
> vanilla kernel!!!
>
> But with 2.6.9-34EL Red Hat Enterprise Stock kernel I'm still having
> errors and dmesg output is a lot more verbose. I'm attaching both dmesg
> outputs just in case it helps.
> Do I need to report this to Red Hat?
> Is it a bug? or a kernel configuration error?
You didn't attach the dmesg ... but I'm afraid RHEL3 is probably too old
for me to be of much help anyway, so Red Hat is your best bet.
> BTW: Do anybody in this list knows how to manage this model of array
> from Linux? Any software available? Boot disk? Symplicity Software? Any
> hint you can provide will be greatly appreciated.
> Array model is Symbios/NCR 6285-3621.
No. The Java based symplicity will run on Linux, but it can only manage
network connected arrays. The 6285 is vintage 1996 or so and is too old
for that. You can really only manage it on Operating Systems which have
the symplicity support built in.
James
prev parent reply other threads:[~2006-05-12 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 13:29 Symbios-NCR 6285-3621 + Adaptec 2944W multilun problem Gabriel Gomiz
2006-05-12 14:09 ` James Bottomley
2006-05-12 14:34 ` Gabriel Gomiz
2006-05-12 15:09 ` James Bottomley
2006-05-12 15:56 ` Mike Anderson
2006-05-12 17:19 ` Gabriel Gomiz
2006-05-12 17:22 ` James Bottomley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1147454573.3769.32.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=gomita@cooperativaobrera.com.ar \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox