All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Noll <maan@systemlinux.org>
To: Maarten <maarten@ultratux.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid6 array crashed-- 4-disk failure...(?)
Date: Tue, 16 Sep 2008 10:25:10 +0200	[thread overview]
Message-ID: <20080916082509.GA17300@skl-net.de> (raw)
In-Reply-To: <48CE9811.60307@ultratux.net>

[-- Attachment #1: Type: text/plain, Size: 2789 bytes --]

On 19:14, Maarten wrote:
> >Are you also using an Intel-based SATA chip (please send the output
> >of lspci -v)?  Also, which kernel version are you using?
> 
> No, my chipset is a VIA one. Because the VIA SATA chips/drivers are 
> terrible, I use only SATA PCI cards with Sil chipsets.  Believe it or 
> not I have good/excellent experiences with these. The driver is quite 
> stable, better than everything else I tried.
> 
> apoc log # lspci
> 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] 
> Host Bridge (rev 80)
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
> 00:07.0 RAID bus controller: Silicon Image, Inc. SiI 3114 
> [SATALink/SATARaid] Serial ATA Controller (rev 02)
> 00:08.0 RAID bus controller: Silicon Image, Inc. SiI 3114 
> [SATALink/SATARaid] Serial ATA Controller (rev 02)
> 00:09.0 RAID bus controller: Silicon Image, Inc. SiI 3114 
> [SATALink/SATARaid] Serial ATA Controller (rev 02)
> 00:0a.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial 
> ATA Controller (rev 02)
> 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 
> Gigabit Ethernet (rev 10)
> 00:0f.0 IDE interface: VIA Technologies, Inc. 
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
> 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge 
> [KT600/K8T800/K8T890 South]
> 01:00.0 VGA compatible controller: ATI Technologies Inc Rage XL AGP 2X 
> (rev 65)
> 
> Linux apoc 2.6.23-gentoo-r3 #2 Fri Apr 25 11:09:37 CEST 2008 i686 AMD 
> Sempron(tm) 2200+ AuthenticAMD GNU/Linux

My machine is running vanilla 2.6.25.4, i.e. we're using different
SATA drivers and different kernels.

While looking at the logs I found a plenty of those:

	set_rtc_mmss: can't update from 150 to 43

And indeed this machine started to have serious problems with its
clock since last weekend. I found it off by 12 hours yesterday and it
is still runing much too fast so that ntp is not working any more. I'm
currently setting the time with a script in 10min intervals...

Were you also seeing such messages during/after the hard disk failures?

> I'm considering a 8/12/16 port Areca controller but a few practicalities 
> hold me back: the price, and the fact I would need a PCI-X slot unless I 
> want to kill performance by a factor of 10. Also, the fact that I then 
> cannot use software raid anymore tends to scare me a little: You never 
> know how firmware reacts in the more 'interesting' circumstances, and 
> you lose control over it...

You could use jbod mode (or create single-disk "raid arrays") with
Areca or 3ware controllers and use software raid on top of that.

Andre
-- 
The only person who always got his work done by Friday was Robinson Crusoe

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-09-16  8:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15  9:04 Raid6 array crashed-- 4-disk failure...(?) Maarten
2008-09-15 10:16 ` Neil Brown
2008-09-15 16:32   ` Maarten
2008-09-15 20:57     ` Maarten
2008-09-16 13:12       ` Andre Noll
2008-09-15 11:03 ` Peter Grandi
2008-09-15 16:57   ` Maarten
2008-09-16 19:06     ` Bill Davidsen
2008-09-15 12:59 ` Andre Noll
2008-09-15 17:14   ` Maarten
2008-09-16  8:25     ` Andre Noll [this message]
2008-09-16 17:50       ` Maarten
2008-09-16 18:12         ` Maarten
2008-09-17  8:25         ` Andre Noll
2008-09-19 14:55         ` John Stoffel

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=20080916082509.GA17300@skl-net.de \
    --to=maan@systemlinux.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=maarten@ultratux.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.