Re: Miscomputed CRC's

Just a quick note of thanks for the all the advice on this problem. The
problem seems to have been a motherboard fault where it was not refreshing
the memory correctly. The faulty machine failed on the very last test of
memtest86, which was a bit-fade test. I wonder that it worked at all
really; but there you go. I replaced the motherboard with one from one of
my spare machines, but it wouldn't power up, so I had to resort to
cannibalising a second spare, and that is now working fine.

Thanks again, everyone. :-)

Richard.

On Tue, 14 Jan 2020 at 12:04, Richard Gray <[email protected]>
wrote:

> I didn't ignore anything helpful that anyone has suggested, as evidenced
> by my subsequent posts. The server chassis on which this problem occurs is
> my perimeter firewall, among other things, so doing a memory test means
> taking it offline, and cutting myself off from the internet.
>
> It's all a question of time and minimising the impact on my users, so
> running a memory test for any length of time means an overnight run. I
> wasn't ignoring anyone's advice, really.
>
> Let us part as friends. :-)
>
> Richard.
>
> On Tue, 14 Jan 2020, 09:17 Matus UHLAR - fantomas, <[email protected]>
> wrote:
>
>>
>> On 13.01.20 18:40, Richard Gray wrote:
>> >I have tried a single pass of memtest86,
>>
>> tried memtext86+ ?  how much RAM?  It's a physical machine I assume.
>>
>> >Additionally, I have tried the --hash option on my latest incremental
>> >backup and the hash *doesn't* match, using sha512.
>>
>> try multiple passes on the same machine. If they produce different result,
>> you surely have a HW problem.
>>
>> >On Mon, 13 Jan 2020 at 17:21, Denis Corbin <[email protected]> wrote:
>> >> If you see the amount of executable instruction versus the amount of
>> >> data that a RAM has to hold today, this is not that much surprising.
>> >> Added to this the fact the kernel is located at a fixed place, still
>> >> the same anytime you reboot, it may well have no change to use the
>> >> faulty portion of RAM...
>> >>
>> >> you should have confirmation by running memtest86+ as "suggested" by
>> >> Matus. Until then faulty memory is still an hypothesis to be
>>
>> actually Mihai recommended it first.
>>
>>
>> P.S.  I didn't want to be rude, you just seemed to ignore very valid
>> recommendation to test memory.
>>
>> --
>> Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
>> Warning: I wish NOT to receive e-mail advertising to this address.
>> Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
>> (R)etry, (A)bort, (C)ancer
>>
>>
>> _______________________________________________
>> Dar-support mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/dar-support
>>
>

_______________________________________________
Dar-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dar-support