# Re: Why does one get mismatches?

- List: linux-raid
- 3 messages, 3 authors
- Page: https://ratatoskr.run/linux-raid/2010/01/6609321/t

## Re: Why does one get mismatches?

- From: Goswin von Brederlow \<hidden\>
- Date: 2010-01-28 20:24:46 
- Message: https://ratatoskr.run/linux-raid/2010/01/6609321.md

```text
"Tirumala Reddy Marri" [ref] writes:

> I just tried and miss-match count is zero. Interesting, is XOR engine
> doing something wrong ? . Then I ran a test where I raw-write the file
> to /dev/md0. Then did the raw-read for the same size. In this case XOR
> matched as expected. Then I failed a drive using "mdadm -f /dev/md0
> /dev/sda". Then I read the same size data again from /dev/md0. And
> checksum matches too. 
> What is this mean XOR engine is doing right thing. But "chec/repair"
> test is not functioning properly with XOR-engine ?
>
> Or is this something to do with  how the buffers are handled ? may they
> are cached ?
>
>
> -Marri

No idea. But if everything works without the XOR engine and gives
mismatches with then I would think there is a software or hardware error
there and not in the cable or disks.

MfG
        Goswin
```

## Re: Why does one get mismatches?

- From: Jon Hardcastle \<hidden\>
- Date: 2010-01-29 15:37:05 
- Message: https://ratatoskr.run/linux-raid/2010/01/6609355.md

```text
--- On Thu, 28/1/10, Goswin von Brederlow <goswin-v-b@web.de> wrote:

> From: Goswin von Brederlow <redacted>
> Subject: Re: Why does one get mismatches?
> To: <redacted>
> Date: Thursday, 28 January, 2010, 20:24
> "Tirumala Reddy Marri" [ref]
> writes:
> 
> > I just tried and miss-match count is zero.
> Interesting, is XOR engine
> > doing something wrong ? . Then I ran a test where I
> raw-write the file
> > to /dev/md0. Then did the raw-read for the same size.
> In this case XOR
> > matched as expected. Then I failed a drive using
> "mdadm -f /dev/md0
> > /dev/sda". Then I read the same size data again from
> /dev/md0. And
> > checksum matches too. 
> > What is this mean XOR engine is doing right thing. But
> "chec/repair"
> > test is not functioning properly with XOR-engine ?
> >
> > Or is this something to do with  how the buffers
> are handled ? may they
> > are cached ?
> >
> >
> > -Marri
> 
> No idea. But if everything works without the XOR engine and
> gives
> mismatches with then I would think there is a software or
> hardware error
> there and not in the cable or disks.
> 
> MfG
>         Goswin
> --
> 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
> 

i think my RAM is fecked - does that sound like a possible cause? memtest86 gives PAGES of red errors when run but the POST gives nothing and the machine boots.... it has 512MB

i have some more on order as a speculative.. 


      
--
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
```

## Re: Why does one get mismatches?

- From: Bill Davidsen \<hidden\>
- Date: 2010-02-01 21:10:15 
- Message: https://ratatoskr.run/linux-raid/2010/02/6609437.md

```text
Jon Hardcastle wrote:
> --- On Thu, 28/1/10, Goswin von Brederlow [ref] wrote:
>
>   
>> From: Goswin von Brederlow <redacted>
>> Subject: Re: Why does one get mismatches?
>> To: <redacted>
>> Date: Thursday, 28 January, 2010, 20:24
>> "Tirumala Reddy Marri" [ref]
>> writes:
>>
>>     
>>> I just tried and miss-match count is zero.
>>>       
>> Interesting, is XOR engine
>>     
>>> doing something wrong ? . Then I ran a test where I
>>>       
>> raw-write the file
>>     
>>> to /dev/md0. Then did the raw-read for the same size.
>>>       
>> In this case XOR
>>     
>>> matched as expected. Then I failed a drive using
>>>       
>> "mdadm -f /dev/md0
>>     
>>> /dev/sda". Then I read the same size data again from
>>>       
>> /dev/md0. And
>>     
>>> checksum matches too. What is this mean XOR engine is doing right thing. But
>>>       
>> "chec/repair"
>>     
>>> test is not functioning properly with XOR-engine ?
>>>
>>> Or is this something to do with  how the buffers
>>>       
>> are handled ? may they
>>     
>>> are cached ?
>>>
>>>
>>> -Marri
>>>       
>> No idea. But if everything works without the XOR engine and
>> gives
>> mismatches with then I would think there is a software or
>> hardware error
>> there and not in the cable or disks.
>>
>> MfG
>>         Goswin
>> --
>> 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
>>
>>     
>
> i think my RAM is fecked - does that sound like a possible cause? memtest86 gives PAGES of red errors when run but the POST gives nothing and the machine boots.... it has 512MB
>
> i have some more on order as a speculative..
>   

I would bet that your RAM is broken. Any errors indicate bad RAM, no errors indicate no persistent error. Scrap that RAM. More will make the machine faster, too.

-- 
Bill Davidsen [ref]
 "We can't solve today's problems by using the same thinking we
  used in creating them." - Einstein

```
