Re: Miscomputed CRC's

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Richard,

Too bad for the hardware cost, but hopefully you could preserve your
data... I would never have thought dar could be able to preserve data
that way :^)

And thanks you for this feedback

Best Regards,
Denis

On 17/01/2020 11:43, Richard Gray wrote:
> 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]
> <mailto:[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] <mailto:[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]
> <mailto:[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] 
> <mailto:[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] 
> <mailto:[email protected]> 
> https://lists.sourceforge.net/lists/listinfo/dar-support
> 
> 
> 
> _______________________________________________ Dar-support mailing
> list [email protected] 
> https://lists.sourceforge.net/lists/listinfo/dar-support
> 
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEOzEprx3d76WjfYGPCDGwvQPYsYIFAl4iFsYACgkQCDGwvQPY
sYIuQw/9Ez2kyQW8vAaXmQFJQW9dQDfNaKOV7zwCF7OTPIjUb8+1RxNKreM2RaVT
pZAzm8ag0J12hjsLiAORRYofO+DdKMl3Ihh4FWgfv5vYGYqVl4sd0eF3tLGF5jBa
keqoANHOuipC1VJFTDBFVm2NovKClSJrtTFLj/e+ZcTXzwA8a1ziHZxyg+PMqQ1d
NMzneGaNONtEv74jeqJrQvaDbp52Z3/waCZXX55GVyTRAjfP1rSOaSckspbjHGPe
TPYFgr4csHgQV24fZcJ8d4V/BV4dKOPqwRk3XLCH4yN5nzGeugPiVJ3Xbt7t/ccn
1rPgK54H4GwM2FrqEGwCXLgzsPq3ba4YE/XiZFRIAUgstZl86LIf/KfmQl2d9Hi0
2kF7JabthHNIwNp8bpcchJJNoJ/OEeQP18jMRorx8m+AUYxVnMljMyCqRI+wdcb9
BvBmN3HOXOezuTFLqkjxJp9eTB/gZ1DZe0tWh1hni7HzUBVMKLL2iqb9Dp4IL3zE
gCK3IljRQBDg1A+9KqLLy6j5DkCt7wqK0EDNc6OscL9gWxMB4BYquS6p/qNtcety
1p3l1YHr/aA74g9j5Kw16b1LFi+IVxSsPjxcYlYD6ReGFP/J9VZL7ggW9i/IaeVV
QWC+vS5WlF3azGJIxwnnDA7tW+QYPavG0Jc2LCkijvEqlkS2WsE=
=bKbH
-----END PGP SIGNATURE-----