Munenori Ohuchi wrote:
> Could you try the following patch?
> ...
> If you have a device like 'ad4' which is detected as
> 'udma=UDMA100', this patch will work.
The drive in question looked like this in the verbose boot-log:
ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
ad4: 71540
Hi Daniel,
Could you try the following patch?
You can apply this patch in freebsd 7.0 just by copying and
pasting to your shell.
Before you apply this patch, you can check as follows
if this works on your environment or not.
1. Set bootverbose mode.
cat >> /boot/loader.conf << EOF
boot_verbo
Manjunath Ranganathaiah wrote:
> Could be in-memory data corruption. How much RAM installed on the
> system?
I doubt it. If it was a RAM problem then all drives would be affected.
___
Daniel Eriksson (http://www.toomuchdata.com/)
___
freebsd-stable@fre
On 7/1/08, Daniel Eriksson <[EMAIL PROTECTED]> wrote:
>
> The server with 570 SLI chipset has a bunch of new SATA-300 drives
> hooked up to the MCP55 controller and it is giving me silent data
> corruption (easily detectable by running ZFS scrub, every time I run it
> new checksum errors show up).
On Wed, Jul 23, 2008 at 02:32:01PM +0200, Daniel Eriksson wrote:
> > I am having problems with silent data corruption on (some) drives
> > connected to an MCP55 SATA controller.
>
> The original problem showed up when talking to (brand new) Samsung 1TB
> drives in SATA-300 mode hooked up to the on
I wrote:
> I am having problems with silent data corruption on (some) drives
> connected to an MCP55 SATA controller.
The original problem showed up when talking to (brand new) Samsung 1TB
drives in SATA-300 mode hooked up to the onboard controller. I have now
tested with a 750GB Seagate drive in
On Tue, Jul 1, 2008 at 5:01 AM, Daniel Eriksson <[EMAIL PROTECTED]>
wrote:
>
> I am having problems with silent data corruption on (some) drives
> connected to an MCP55 SATA controller.
>
I have an MCP55 controller here running most of my RAID array. When I
origionally loaded this machine, I ha
On 02/07/2008, Chris Rees <[EMAIL PROTECTED]> wrote:
> > Date: Wed, 2 Jul 2008 10:55:07 +0200
> > "Daniel Eriksson" <[EMAIL PROTECTED]> wrote:
> > Jeremy Chadwick wrote:
> >
> >> Can the OP get some non-Samsung disks for testing?
> >
> > I've got a 750 GB Western Digital that I've been planni
> Date: Wed, 2 Jul 2008 10:55:07 +0200
> "Daniel Eriksson" <[EMAIL PROTECTED]> wrote:
> Jeremy Chadwick wrote:
>
>> Can the OP get some non-Samsung disks for testing?
>
> I've got a 750 GB Western Digital that I've been planning to use to
> verify if it's a SATA-150 / SATA-300 problem (it can be ju
Jeremy Chadwick wrote:
> Can the OP get some non-Samsung disks for testing?
I've got a 750 GB Western Digital that I've been planning to use to
verify if it's a SATA-150 / SATA-300 problem (it can be jumpered to
SATA-150), but the drive is packed with valuable data that I'd have to
move elsewhere
Jeremy Chadwick wrote:
Which makes me wonder if there's multiple revisions of the MCP55, or, if
Samsung drives simply don't behave properly with that chipset (this has
my vote).
Daniel has the same revision (as I can see from pciconf).
--
WBR, Andrey V. Elsukov
On Wed, Jul 02, 2008 at 11:17:48AM +0400, Andrey V. Elsukov wrote:
> Daniel Eriksson wrote:
>>> I have two motherboards with MCP55. They work well and I didn't
>>> see any data corruption.
>>
>> Do you have SATA-150 or SATA-300 drives connected to the motherboards?
>
> All drives are SATA-300:
> Fr
Daniel Eriksson wrote:
I have two motherboards with MCP55. They work well and I didn't
see any data corruption.
Do you have SATA-150 or SATA-300 drives connected to the motherboards?
All drives are SATA-300:
FreeBSD 6.2:
1x WDC WD3200YS-01PGB0/21.00M21
FreeBSD 8.0:
5x WDC WD5001ABYS-01YNA0/59
Andrey V. Elsukov wrote:
> I have two motherboards with MCP55. They work well and I didn't
> see any data corruption.
Do you have SATA-150 or SATA-300 drives connected to the motherboards?
___
Daniel Eriksson (http://www.toomuchdata.com/)
___
freebsd-s
Daniel Eriksson wrote:
I'm not sure if the problem is amd64 specific or not, but it seems the
people that have reported problems have all run amd64 (and not i386).
This might be a coincident though.
I have two motherboards with MCP55. They work well and I didn't
see any data corruption.
1. ASU
Chris Rees wrote:
> I have a 570 SLI too (Asus M2N-SLI Deluxe), I've been looking for an
> excuse to put FreeBSD on here :)
>
> I'll start installing it, anything I should do to make this
> error more obvious?
No, if it is a common problem with this chipset and/or MCP55 controller
revision (whi
> Date: Tue, 1 Jul 2008 11:01:17 +0200
> From: "Daniel Eriksson" <[EMAIL PROTECTED]>
>
> I am having problems with silent data corruption on (some) drives
> connected to an MCP55 SATA controller.
>
> I have two servers, both running RELENG_7_0/amd64. One has the 570 Ultra
> chipset, the other has 5
Søren Schmidt wrote:
> Please try the attached patch, or even better try a -current kernel.
The patch made no difference on RELENG_7_0 unfortunately. (And I cannot try
CURRENT on this server.)
___
Daniel Eriksson (http://www.toomuchdata.com/)
___
free
Jeremy Chadwick wrote:
> With the same cables? Not that I want to use cables as a
> scapegoat, but in this case it seems applicable.
With the same cables, yes.
> Can you provide "atacontrol cap" output for one of the drives?
# atacontrol cap ad4
Protocol Serial ATA II
device mod
Hi
OK, the only "modern" nVidia board I have is MCP51 based, however it
uses the same codepath as the MCP55.
Anyhow, there has been fixes fro these in -current, thats not in any
of the releng's yet.
Please try the attached patch, or even better try a -current kernel.
-Søren
ff
Descripti
On Tue, Jul 01, 2008 at 11:01:17AM +0200, Daniel Eriksson wrote:
> The server with 570 Ultra chipset has a bunch of older 250GB SATA-150
> drives hooked up to the MCP55 controller and it is working just fine.
> The server with 570 SLI chipset has a bunch of new SATA-300 drives
> hooked up to the MC
Andrey V. Elsukov wrote:
> Which patch did you use?
I used BDM_SpeedSwitch1.zip
(http://www.samsung.com/global/system/business/hdd/faq/2007/10/29/184337
BDM_SpeedSwitch1.zip).
/Daniel
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org
Daniel Eriksson wrote:
Unfortunately the drives does not have a jumper for setting SATA-150
speed (they are Samsung 1 TB drives), and trying to force the drives to
SATA-150 speed with the "patch" provided by the manufacturer does not
seem to work (the drives still negotiate SATA-300 speed). I wil
Hi
I'll look into that providing I can find HW to work on, IIRC I have
one in the ATA collection but I have to verify when I get to the lab.
-Søren
On 1Jul, 2008, at 11:01 , Daniel Eriksson wrote:
I am having problems with silent data corruption on (some) drives
connected to an MCP55 SAT
24 matches
Mail list logo
