Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Artur Jasowicz" <arturj@mousebusiness.com>
To: linux-raid@vger.kernel.org
Cc: Maurice Hilarius <maurice@harddata.com>
Subject: Re: Fw: DriveReady SeekComplete problems
Date: Thu, 9 May 2002 23:16:59 -0500	[thread overview]
Message-ID: <003401c1f7d9$97c7c460$050010ac@niunia.org> (raw)
In-Reply-To: 5.1.0.14.2.20020509152331.03accca0@mail.harddata.com

From: Maurice Hilarius
> With regards to your message at 03:13 PM 5/9/02, Artur Jasowicz. Where you
> stated:
> >I am building a file server with 5 drive software RAID5 array. I am using
> >three IWill SIDE-100 (Highpoint 370A) controllers as my IDE interfaces,
> >not using their RAID functionality. One Maxtor 160GB drive per channel,
> >two channels per controller. I plan on adding hot spare as the sixth
drive
> >in the future. There's one 160GB partition on each drive. Linux version
> >2.4.19-pre7smp-020502b (root@production) (gcc version 2.96 20000731 (Red
> >Hat Linux 7.1 2.96-98)) #6 SMP Thu May 2 12:15:34 CDT 2002
> >This is a dual Athlon 2000+ MP on Tyan Tiger S2466N-4 with 1GB RAM. OS
and
> >swap runs on separate drives and controllers. This array will be just for
> >data once it is configured.
> >
> >Below are the most relevant parts of my logs. I will post further details
> >if anyone is willing to help, just let me know what info you need. Any
> >suggestions greatly appreciated.
>
> Probably cable problem..
May be, although I've used original, 18in cables, changed the config to use
diferent controllers, the errors came from all drives, randomly. Isn't it
unlikely, that all cables are bad?

>
> Maybe cards not getting a clean IRQ status.
>
I'm not sure what you mean by that, here's my IRQs is that ok?
[root@production root]# cat /proc/interrupts
           CPU0       CPU1
  0:    1060111     900968    IO-APIC-edge  timer
  1:       2223       1623    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
  5:     475613     476603   IO-APIC-level  ide2, ide3, eth1
  8:          1          0    IO-APIC-edge  rtc
  9:     464960     465255   IO-APIC-level  ide4, ide5, eth2
 10:      12405      11231   IO-APIC-level  eth0
 11:      69567      67494   IO-APIC-level  ide6
 12:        159       1172    IO-APIC-edge  PS/2 Mouse
 14:      48388      44855    IO-APIC-edge  ide0
 15:      48907      47090    IO-APIC-edge  ide1
NMI:          0          0
LOC:    1961162    1961161
ERR:          0
MIS:          0



       reply	other threads:[~2002-05-10  4:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5.1.0.14.2.20020509152331.03accca0@mail.harddata.com>
2002-05-10  4:16 ` Artur Jasowicz [this message]
2002-05-10  6:36   ` Fw: DriveReady SeekComplete problems Diamon
2002-05-10 20:07     ` Artur Jasowicz
2002-05-11  6:10       ` Danilo Godec
2002-05-11  6:36         ` Alvin Oga
2002-05-09 21:13 Artur Jasowicz
2002-05-09 21:32 ` Karsten Becker
2002-05-10  3:37   ` Artur Jasowicz
2002-05-12  8:27 ` Mikael Abrahamsson
2002-05-13  4:41   ` Artur Jasowicz
2002-05-13  5:01     ` Mikael Abrahamsson
2002-05-13  6:22     ` Danilo Godec

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='003401c1f7d9$97c7c460$050010ac@niunia.org' \
    --to=arturj@mousebusiness.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=maurice@harddata.com \
    /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