-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ouch. That sounds scary.
The first time I had such a problem I discovered it while trying to
burn a 600+MB avi file to a CDR. I burned a CDR and the md5sum of the
avi file on the disc didn't match. So I burned another one and it
didn't match either
> Date: Fri, 08 Mar 2013 22:26:24 -0500
> From: Kevin Korb
> If it were me, based on my previous experience, I would shut down both
> systems and run memtest86+ or "Windows Memory Diagnostics" on both
> systems. Make sure to enable the extended tests. Let them run
> over
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/08/13 22:16, xiaolong mou wrote:
> Thanks. I suspected hardware issue as well. However I did a local
> rsync test at the USB drive side and NAS side with the same files.
> If there was a local hardware problem (RAM or USB hard drive driver
> etc
Thanks. I suspected hardware issue as well. However I did a local
rsync test at the USB drive side and NAS side with the same files. If
there was a local hardware problem (RAM or USB hard drive driver etc)
it should show up in this test, but everything was fine!
Could it be network driver somehow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have seen this behavior before. Twice.
Both times the cause was bad RAM on the target system. The bad RAM
was corrupting the files within the disk write cache so that rsync
believed it was writing the correct data but the disk was not getting
the
Hi,
I am backing up about 500G of data from a linux-based NAS to a USB
hard drive attached to a router (rt-n16 with tomatousb firmware). Both
NAS and the router have rsync-3.0.9. The router is running rsync in
the daemon mode. To test the set up, I rsync'd the files to the empty
USB hard drive, th
