Re: Corrupt data - RAID sata_sil 3114 chip

Started by Justin Piszcz on Jan 2, 2009 · 10 messages from 7 authors · Last reply Jan 3, 2009

open the first message on its own page

Message details and related content

On Fri, 2 Jan 2009, Bengt Samuelsson wrote:
Hi,

I need some support for this soft-raid system.

I am running it as RAID5 with 4 samsung spinpoint 500G SATA300 tot 1.3T byte

And it runs in http://sm7jqb.dnsalias.com
I use mdadm sytem in a Debian Linux
CPU 1.2Mhz 1G memory ( my older 433Mhz / 512M dont work at all )

I have 'some courrupt' data. And I don't understand whay and how to fix it.
Mybee slow it down more, but how slow it down?

Any with experents from this cheep way of RAID systems.

Ask for more information and I can get it, logs, setup files and what you want
to know.

-- 
Bengt Samuelsson
Nydalavägen 30 A
352 48 Växjö

+46(0)703686441

http://sm7jqb.se


-- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
If this is an mdadm-related raid (not dmraid) please show all relevant md info, mdadm -D /dev/md0, I have cc'd linux-raid on this thread for you.

You'll want to read md.txt in /usr/src/linux/Documentation and read on the check and repair commands.

In addition, have you run memtest86 on your system first to make sure its not memory related?

Justin.

Re: Corrupt data - RAID sata_sil 3114 chip (corrected email address)

Message details and related content

On Fri, 2 Jan 2009, Justin Piszcz wrote:

On Fri, 2 Jan 2009, Bengt Samuelsson wrote:
quoted
Hi,

I need some support for this soft-raid system.

I am running it as RAID5 with 4 samsung spinpoint 500G SATA300 tot 1.3T byte

And it runs in http://sm7jqb.dnsalias.com
I use mdadm sytem in a Debian Linux
CPU 1.2Mhz 1G memory ( my older 433Mhz / 512M dont work at all )

I have 'some courrupt' data. And I don't understand whay and how to fix it.
Mybee slow it down more, but how slow it down?

Any with experents from this cheep way of RAID systems.

Ask for more information and I can get it, logs, setup files and what you want
to know.

-- 
Bengt Samuelsson
Nydalavägen 30 A
352 48 Växjö

+46(0)703686441

http://sm7jqb.se


-- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
If this is an mdadm-related raid (not dmraid) please show all relevant md info, mdadm -D /dev/md0, I have cc'd linux-raid on this thread for you.

You'll want to read md.txt in /usr/src/linux/Documentation and read on the check and repair commands.

4 more quoted lines

Message details and related content
Hello Bengt,

sil3114 is known to cause data corruption with some disks. So far I only know
about Seagate, but maybe there issues with newer Samsungs as well?

http://lkml.indiana.edu/hypermail/linux/kernel/0710.2/2035.html

Unfortuntely this issue has been simply ignored by the SATA developers :(
So if you want to be on the safe side, go an get another controller. 

I hope I won't frighten you too much, but it also might be possible one of 
your disks has a problem,  I have also seen a few broken disks, which don't 
return what you write to it...


Cheers,
Bernd


On Fri, Jan 02, 2009 at 07:42:30AM -0500, Justin Piszcz wrote:

On Fri, 2 Jan 2009, Bengt Samuelsson wrote:
quoted
Hi,

I need some support for this soft-raid system.

I am running it as RAID5 with 4 samsung spinpoint 500G SATA300 tot 1.3T byte

And it runs in http://sm7jqb.dnsalias.com
I use mdadm sytem in a Debian Linux
CPU 1.2Mhz 1G memory ( my older 433Mhz / 512M dont work at all )

I have 'some courrupt' data. And I don't understand whay and how to fix it.
Mybee slow it down more, but how slow it down?

Any with experents from this cheep way of RAID systems.

Ask for more information and I can get it, logs, setup files and what 
you want
to know.

-- 
Bengt Samuelsson
Nydalavägen 30 A
352 48 Växjö

+46(0)703686441

http://sm7jqb.se


-- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a 
subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
If this is an mdadm-related raid (not dmraid) please show all relevant md 

9 more quoted lines

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Message details and related content
Hi,

I also had problems with the sata_sil driver with more than one
silicon image card in the same machine about a year or two back. Don't
remember the specifics, but basically the cards would occasionally
drop the SATA link. This was with Western Digital drives. With a
Samsung 750GB disk the disk and controller absolutely refused to talk
to each other.

I've since got rid of all but one silicon image card and haven't had
problems since and swapped out cables. Coincidence? No idea.

04:01.0 RAID bus controller: Silicon Image, Inc. SiI 3512
[SATALink/SATARaid] Serial ATA Controller (rev 01)
Currently running kernel 2.6.24-21

Not much fun when disks don't work properly, is it? :-(

T

2009/1/2 Bernd Schubert [off-list ref]:
Hello Bengt,

sil3114 is known to cause data corruption with some disks. So far I only know
about Seagate, but maybe there issues with newer Samsungs as well?

http://lkml.indiana.edu/hypermail/linux/kernel/0710.2/2035.html

Unfortuntely this issue has been simply ignored by the SATA developers :(
So if you want to be on the safe side, go an get another controller.

I hope I won't frighten you too much, but it also might be possible one of
your disks has a problem,  I have also seen a few broken disks, which don't
return what you write to it...


Cheers,
Bernd


On Fri, Jan 02, 2009 at 07:42:30AM -0500, Justin Piszcz wrote:
quoted

On Fri, 2 Jan 2009, Bengt Samuelsson wrote:
quoted
Hi,

I need some support for this soft-raid system.

I am running it as RAID5 with 4 samsung spinpoint 500G SATA300 tot 1.3T byte

And it runs in http://sm7jqb.dnsalias.com
I use mdadm sytem in a Debian Linux
CPU 1.2Mhz 1G memory ( my older 433Mhz / 512M dont work at all )

I have 'some courrupt' data. And I don't understand whay and how to fix it.
Mybee slow it down more, but how slow it down?

Any with experents from this cheep way of RAID systems.

35 more quoted lines

Message details and related content
On Fri, 2009-01-02 at 22:30 +0100, Bernd Schubert wrote:
Hello Bengt,

sil3114 is known to cause data corruption with some disks. So far I only know
about Seagate, but maybe there issues with newer Samsungs as well?

http://lkml.indiana.edu/hypermail/linux/kernel/0710.2/2035.html

Unfortuntely this issue has been simply ignored by the SATA developers :(
So if you want to be on the safe side, go an get another controller. 
Are you sure? is this not the "15" or "slow_down" thing mentioned here:
http://ata.wiki.kernel.org/index.php/Sata_sil ?
I hope I won't frighten you too much, but it also might be possible one of 
your disks has a problem,  I have also seen a few broken disks, which don't 
return what you write to it...


Cheers,
Bernd


On Fri, Jan 02, 2009 at 07:42:30AM -0500, Justin Piszcz wrote:
quoted

On Fri, 2 Jan 2009, Bengt Samuelsson wrote:
quoted
Hi,

I need some support for this soft-raid system.

I am running it as RAID5 with 4 samsung spinpoint 500G SATA300 tot 1.3T byte

And it runs in http://sm7jqb.dnsalias.com
I use mdadm sytem in a Debian Linux
CPU 1.2Mhz 1G memory ( my older 433Mhz / 512M dont work at all )

I have 'some courrupt' data. And I don't understand whay and how to fix it.
Mybee slow it down more, but how slow it down?

Any with experents from this cheep way of RAID systems.

Ask for more information and I can get it, logs, setup files and what 
you want
to know.

-- 
Bengt Samuelsson
Nydalavägen 30 A
352 48 Växjö

25 more quoted lines

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Message details and related content
On Saturday 03 January 2009 03:31:57 Redeeman wrote:
On Fri, 2009-01-02 at 22:30 +0100, Bernd Schubert wrote:
quoted
Hello Bengt,

sil3114 is known to cause data corruption with some disks. So far I only
know about Seagate, but maybe there issues with newer Samsungs as well?

http://lkml.indiana.edu/hypermail/linux/kernel/0710.2/2035.html

Unfortuntely this issue has been simply ignored by the SATA developers :(
So if you want to be on the safe side, go an get another controller.
Are you sure? is this not the "15" or "slow_down" thing mentioned here:
http://ata.wiki.kernel.org/index.php/Sata_sil ?
According to Jeff Garzik and Tejun Heo 3114 is not affected by the mod15 bug. 
The mod15 also help in our case, but probably we are just luckily.

https://kerneltrap.org/mailarchive/linux-kernel/2007/10/11/334985/thread


Cheers,
Bernd

-- 
Bernd Schubert
Q-Leap Networks GmbH
Message details and related content
On Fri, 2 Jan 2009 22:30:07 +0100
Bernd Schubert [off-list ref] wrote:
Hello Bengt,

sil3114 is known to cause data corruption with some disks. 
News to me. There are a few people with lots of SI and other devices
jammed into the same mainboard who had problems but that doesn't appear
to be an SI problem as far as I can tell.

There are some incompatibilities between certain silicon image chips and
Nvidia chipsets needing BIOS workarounds according to the errata docs.

Alan
Message details and related content
On Sat, Jan 03, 2009 at 01:39:36PM +0000, Alan Cox wrote:
On Fri, 2 Jan 2009 22:30:07 +0100
Bernd Schubert [off-list ref] wrote:
quoted
Hello Bengt,

sil3114 is known to cause data corruption with some disks. 
News to me. There are a few people with lots of SI and other devices
No no, you just forgot about it, since you even reviewed the patches ;)

http://lkml.org/lkml/2007/10/11/137
jammed into the same mainboard who had problems but that doesn't appear
to be an SI problem as far as I can tell.

There are some incompatibilities between certain silicon image chips and
Nvidia chipsets needing BIOS workarounds according to the errata docs.
Well, I already posted the the links to the discussion we had in the past.
The corruption issue is easily reproducible on Tyan S2882 with AMD-8111,
SiI 3114 and ST3250820AS disks. This is on a compute cluster, and we run into 
the problem, when a few ST3200822AS failed and got replaced by newer 250GB 
disks. The 200GB ST3200822AS work perfectly fine, while the 250GB ST3250820AS 
disks cause data corrution. 

Presently the cluster is empty, so if you want do help me, your help to 
properly solve the issue would be highly appreciated (*).


Cheers,
Bernd

PS: The patches I posted work fine on these systems, but they are not upstream 
and I really would prefer to find a way in vanilla linux to prevent this
data corruption.

PPS: Its a bit funny with this cluster, since it is located at my university 
group and I did and do many calculations on it myself.  But presently I work 
for the company we bought it from and which is responsible to maintain it... ;)
Message details and related content
Bernd Schubert wrote:
On Sat, Jan 03, 2009 at 01:39:36PM +0000, Alan Cox wrote:
quoted
On Fri, 2 Jan 2009 22:30:07 +0100
Bernd Schubert [off-list ref] wrote:
quoted
Hello Bengt,

sil3114 is known to cause data corruption with some disks. News to me. There are a few people with lots of SI and other devices
No no, you just forgot about it, since you even reviewed the patches ;)

http://lkml.org/lkml/2007/10/11/137
And Jeff explained why they were not merged:

http://lkml.org/lkml/2007/10/11/166

All the patch does is try to reduce the speed impact of the workaround. But as was pointed out, they don't reliably solve the problem the workaround is trying to fix, and besides, the workaround is already not applied to SiI3114 at all, as it is apparently not applicable on that controller (only 3112).
quoted
jammed into the same mainboard who had problems but that doesn't appear
to be an SI problem as far as I can tell.

There are some incompatibilities between certain silicon image chips and
Nvidia chipsets needing BIOS workarounds according to the errata docs.
Do you have details of these Alan?
Well, I already posted the the links to the discussion we had in the past.
The corruption issue is easily reproducible on Tyan S2882 with AMD-8111,
SiI 3114 and ST3250820AS disks. This is on a compute cluster, and we run into the problem, when a few ST3200822AS failed and got replaced by newer 250GB disks. The 200GB ST3200822AS work perfectly fine, while the 250GB ST3250820AS disks cause data corrution.

Presently the cluster is empty, so if you want do help me, your help to properly solve the issue would be highly appreciated (*).


Cheers,
Bernd

PS: The patches I posted work fine on these systems, but they are not upstream and I really would prefer to find a way in vanilla linux to prevent this
data corruption.
Some people have tried turning on the slow_down option or adding their drive to the mod15 blacklist and found that problems went away, but that in no way implies that their setup actually needs this workaround, only that it slows down the IO enough that the problem no longer shows up. It's a big hammer that can cover up all kinds of other issues and has confused a lot of people into thinking the mod15write problem is bigger than it actually is.
PPS: Its a bit funny with this cluster, since it is located at my university group and I did and do many calculations on it myself.  But presently I work for the company we bought it from and which is responsible to maintain it... ;)
Message details and related content
On Fri, Jan 2, 2009 at 9:30 PM, Bernd Schubert [off-list ref] wrote:
Hello Bengt,

sil3114 is known to cause data corruption with some disks. So far I only know
about Seagate, but maybe there issues with newer Samsungs as well?
I've experienced data corruption with a SII 0680 ACLU144 (on an ST
Labs' A-132 card) with a pair of Seagate ST3300622A drives.  I was
using them with MD in a RAID1 configuration.

James.
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help