public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "mel" <mel@mmtab.se>
To: linux-scsi@vger.kernel.org
Subject: Promise UltraTrak RM15000 + Adaptec 39160
Date: Fri, 8 Aug 2003 12:36:21 +0200	[thread overview]
Message-ID: <20030808103621.M63039@mmtab.se> (raw)

The story so far:

I've been running an out of the box RH 7.3 with 2.4.18-3 kernel together with 
the 39160 card and a UltraTrak RM8000 for over 12 months. The only change 
made to the kernel was that I compiled the aic7xxx driver into the kernel. 
The server is running nfs and samba only. The RM8000 is equipped with eight 
80GB IBM drives and exports about 0.5TB.

The mobo is a Kinetiz 7E-A with a 1GHz AMD and 512MB of RAM.

When we run out of disk i invested in a RM15000 and 15 120GB IBM-drives. I 
figured it was time to upgrade kernel and drivers and therefore I got the 
2.4.21 kernel together with the latest driver ( aic79xx-linux-2.4-20030603-
tar.gz )  from Justin Gibbs site http://people.freebsd.org/~gibbs/linux/

After installation I tried to partition and makefs the new drive. I got a lot 
of parity errors and "trying to queue an ABORT message" from the card. I did 
some 'Googling' but could not find the answer.

As the server is in production I assembled a lab machine and hooked the 
RM15000 to that machine. I did a RH7.3 install and had it to autodetect my 
gear ( aic7xxx as a module ). As a surprise everything worked without a 
glitch with this setup. I tried to use the 2.4.21 kernel with the new driver 
( as a module ) on this machine but with this it malfunctioned in the same 
way as before.

Is there anyone that have a clue to this behaviour?

Shouldn't the never version be better ;)

/Mel

--

This sentence is false.

             reply	other threads:[~2003-08-08 10:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08 10:36 mel [this message]
2003-08-08 16:48 ` Promise UltraTrak RM15000 + Adaptec 39160 Justin T. Gibbs

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=20030808103621.M63039@mmtab.se \
    --to=mel@mmtab.se \
    --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