File corrupted when backing up to a Synology NAS (Only happens on one machine)
I'm not sure whether this is a Synology problem, Acronis backup problem or my PC but would like to see if anyone else has had the same problem.
To set the scene, I have two computers on the network; one for my wife Marina and one for myself and they are called, rather unimaginatively, Michael and Marina. I also have a Synology unit called Ziggy (My wife was a Quantum Leap fan). They are connected via powerline connecters and everything has been working great for the last few years.
The two machines each have an SSD with Windows 10 operating system and a separate SSD drive for data. These are backed up weekly to the Synology using their own separate copies of Acronis Home Image and at different times of the day when they are not being used.
However, in the last few months, although Marina's machine backs up without any problem, I have started to get a 'file corrupted' error message from Acronis on my machine within minutes of the backup starting.
Things I have ruled out:
1. Synology unit. No problems with Marina backing up to the same share where my machine was being backed up to albeit a different folder on that share.
2. Network. The above rules out the network too.
3. Acronis software. I have run the software with the destination changed to a spare external disk drive and it works perfectly. I have also tried EaseUS backup software and get the same result; error when copying to the Synology unit but success when copying to an external drive. I have tried uninstalling and reinstalling Acronis but no luck.
4. I also thought that it might be a problem with my machine's ethernet port so bought a USB to ethernet adaptor but still the same problem. Also tried a USB wifi dongle but, again, same error.
The only thing I haven’t done is reinstall Windows but I did take the opportunity to upgrade my machine to Windows 11 but that hasn't made much difference (apart from me wishing I'd stayed with Windows 10)
If anyone can think of anything or have come across this I would be eternally grateful for any help.
Kind regards
Michael
Hi Steve
Thanks for the information above. I've run the assistant and go the relevant log which I have tried to attach below to see if anyone can work out what has gone wrong (It means nothing to me I'm afraid)
It wont let me attach it as a file and when I put my link for my google drive it says you cant do that eithet
Michael, write the link to your google drive for the log(s) as a non-clickable link, i.e. leave off the https:// start of the link.
Thanks . Its
drive dot google dot com/ followed by
/file/d/1I6ZarWk4x0GUhDFyTEQTFtZwMTvBa6cE/view?usp=share_link
Michael, thanks for the Backup Worker log - this shows the backup to the NAS proceeding fine up to end when Acronis was trying to write out the backup file data to the NAS.
17/05/2023 08:00:23:312 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=pcs_co_file_writev(\\?\UNC\ZIGGY\Backup\LokiV2\windows11\WDC WDS500G2B0C-00PXH0 211070WD.tibx) failed: 59 (pcs_err=4);
17/05/2023 08:00:23:312 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=pcs_co_file_writev(\\?\UNC\ZIGGY\Backup\LokiV2\windows11\WDC WDS500G2B0C-00PXH0 211070WD.tibx) failed: 59 (pcs_err=4);
17/05/2023 08:00:23:312 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=pcs_co_file_writev(\\?\UNC\ZIGGY\Backup\LokiV2\windows11\WDC WDS500G2B0C-00PXH0 211070WD.tibx) failed: 59 (pcs_err=4);
17/05/2023 08:00:23:312 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=pcs_co_file_writev(\\?\UNC\ZIGGY\Backup\LokiV2\windows11\WDC WDS500G2B0C-00PXH0 211070WD.tibx) failed: 59 (pcs_err=4);
17/05/2023 08:00:23:312 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=pcs_co_file_writev(\\?\UNC\ZIGGY\Backup\LokiV2\windows11\WDC WDS500G2B0C-00PXH0 211070WD.tibx) failed: 59 (pcs_err=4);
17/05/2023 08:00:23:313 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=pcs_co_file_writev(\\?\UNC\ZIGGY\Backup\LokiV2\windows11\WDC WDS500G2B0C-00PXH0 211070WD.tibx) failed: 59 (pcs_err=4);
17/05/2023 08:00:23:313 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=pcs_co_file_writev(\\?\UNC\ZIGGY\Backup\LokiV2\windows11\WDC WDS500G2B0C-00PXH0 211070WD.tibx) failed: 59 (pcs_err=4);
17/05/2023 08:00:23:313 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=pcs_co_file_writev(\\?\UNC\ZIGGY\Backup\LokiV2\windows11\WDC WDS500G2B0C-00PXH0 211070WD.tibx) failed: 59 (pcs_err=4);
17/05/2023 08:00:23:313 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=io#1: reopen: write 773992448:4194304 failed with err -5017;
17/05/2023 08:00:23:313 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=io#1: reopen: started, timeout 0, previous error -5017;
17/05/2023 08:00:33:918 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=ar#1: failed to open the archive: corrupted page is found at 747683840;
17/05/2023 08:00:33:918 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=ar#1: reopen failed: failed to read volume 0: -5003 Data is corrupted: CRC mismatch or internal data structures mismatch;
17/05/2023 08:00:34:027 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: reopen failed (time left 0/0ms): -5003 (Data is corrupted: CRC mismatch or internal data structures mismatch);
17/05/2023 08:00:34:027 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: write 4194304 err -5003, offs 773992448;
17/05/2023 08:00:34:027 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: write 4194304 err -5003, offs 744632320;
17/05/2023 08:00:34:027 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: write 4194304 err -5003, offs 761409536;
17/05/2023 08:00:34:027 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: write 4194304 err -5003, offs 757215232;
17/05/2023 08:00:34:027 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: write 4194304 err -5003, offs 748826624;
17/05/2023 08:00:34:027 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: write 4194304 err -5003, offs 753020928;
17/05/2023 08:00:34:028 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: write 4194304 err -5003, offs 769798144;
17/05/2023 08:00:34:029 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: write 4194304 err -5003, offs 765603840;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=ar#1: archive closing \\?\UNC\ZIGGY\Backup\LokiV2\windows11\\WDC WDS500G2B0C-00PXH0 211070WD.tibx;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=inf; message=lsm#1: dedup_map nr_lookup=7692 nr_found=30 false+=23 (0.30%/76.67%);
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: write 192512 err -5003, offs 778186752;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: time=0d01:06:18 total req=225 (rd=0 wr=205 sync=20), pgreq=190034 (rd=0 wr=190034) sync=1382394.1 ms;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=io#1: pg cache hit=2046 ra_hit=0 ra_pages=0 ra=0.00%;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=lsm#1: dmap reads: dir=8 leaf=187 ra=0 (0.00%) pgs;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=lsm#1: segment_map reads: dir=8 leaf=377 ra=0 (0.00%) pgs;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=lsm#1: dedup_map reads: dir=8 leaf=105 ra=0 (0.00%) pgs;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=ar#1: umap allocations=10718 times, 0ms total, 0ms max, 0ms average nr=0 pgs=0 runs=10 skip=10718 skip/find=10664; left exts=0 pgs=0 (avg=-1.$);
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=ar#1: commits: 11 times, 1382459ms total, 288105ms max, 125678ms average;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=ar#1: wait stats: wr 3854426 rd 0 compr 3003 decompr 0 (ms);
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=lsm#1: dmap writes: 235 pgs;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=lsm#1: dmap merges: 8 times, 15ms total, 3ms max, 1ms average;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=lsm#1: segment_map writes: 468 pgs;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=lsm#1: segment_map merges: 8 times, 17ms total, 3ms max, 2ms average;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=lsm#1: dedup_map writes: 132 pgs;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=lsm#1: dedup_map merges: 8 times, 11ms total, 2ms max, 1ms average;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=ar#1: seg=774.52 MB avg=77.09 KB user=1453.70 MB ratio=51.52% pad=23668338 (3.06%);
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=ar#1: slices=2 user=1389MB data=738MB meta=0MB unused=3MB/0.41% deallocated=0MB/0.00%;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=ar#1: archive mode=rewrite reopen=1:0 commit=9/9 size=0/778379264 uuid=e72fbb47b72f5e4ae6eb440129196fa9 type=disk features=d--au--h-;
17/05/2023 08:00:34:036 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=ar#1: archive close (user read=0MB write=1390MB) rc=-5003 (Data is corrupted: CRC mismatch or internal data structures mismatch);
17/05/2023 08:00:34:038 PM +01:00 12000 I00000000: Pid: 11740 type=log; level=err; message=image backup: failed to close archive: 0x4000d;
17/05/2023 08:00:35:513 PM +01:00 12000 I00000000: Pid: 11740 type=commonerror; value= ?? ,K??The file is corrupted.$moduleAdisk_backup_vs_1028$fileAe:\jenkins_agent\workspace\common\ati-disk_backup\1028\product\main\core\resizer\archive3\archive3_error.cpp$funcA`anonymous-namespace'::ConvertArchive3Error$lineN???????_5?0Data is corrupted: CRC mismatch or internal data structures mismatchfunctionAarchive_stream_write_shbufpathW\\?\UNC\ZIGGY\Backup\LokiV2\windows11\\WDC WDS500G2B0C-00PXH0 211070WD.tibx$moduleAdisk_backup_vs_1028$fileAe:\jenkins_agent\workspace\common\ati-disk_backup\1028\product\main\core\resizer\archive3\utils.cpp$funcA`anonymous-namespace'::ArchiveWriterImpl::CoroutineFunc$lineNjA; id=1;
17/05/2023 08:00:35:513 PM +01:00 12000 I00000000: Pid: 11740 type=retcode; value=4095; id=1;
17/05/2023 08:00:35:513 PM +01:00 3912 I00000000: Pid: 11740 >>> exit
17/05/2023 08:00:35:513 PM +01:00 12000 I00000000: Pid: 11740 type=quit; id=1;
The log is suggesting that the .tibx file on the NAS is corrupted so the first action here should be to try creating a new backup task using a unique name to see if the issue repeats or not?
If the same failure / error continues with the new backup task then this would indicate that the corruption could be happening during the transfer of data across your network to the NAS.
One other possibility is a potential memory issue on the source PC but in which case I would expect the errors to happen for local backups as well as those to the NAS. Note: overclocking of PC components can cause some very strange errors for backup applications.
Thanks Steve for your help on this one.
I've done a few other tests and it's definitely this particular PC's network connection as I've tried saving other files from this PC to the synology and it just hangs or times out.
I've tried all the relevant network 'fixes' from the internet but no luck.
I have a spare PC in the garage so I might 'restore' my current Pc's windows on to that one and see if I get the same problem. If I do then I know it is definitely the Windows software and I'll have to bite the bullet and reinstall Windows.
Thanks again
Michael, you say they are connected with Powerline connectors. Have you tried testing those?
Gentlemanmike wrote:Thanks Steve for your help on this one.
I've done a few other tests and it's definitely this particular PC's network connection as I've tried saving other files from this PC to the synology and it just hangs or times out.
I've tried all the relevant network 'fixes' from the internet but no luck.
I have a spare PC in the garage so I might 'restore' my current Pc's windows on to that one and see if I get the same problem. If I do then I know it is definitely the Windows software and I'll have to bite the bullet and reinstall Windows.
Thanks again
Thanks for sharing the updates.
Cheers.
Fixed!
I looked at the possibility that it might be a powerline adaptor problem and I had heard that the BT ones I was using were maybe not the best. I decided to update them to Devolo ones (I've had these many years ago and they were great; not sure why I changed them for BT ones) and the problem has resolved itself.
Thanks to everyone for their help though.
Mike, great that you have identify the root cause and resolved it!
I have used various T-Link powerline adaptors in the past but a few years back I bit the bullet and invested in a Netgear Orbi wireless mesh system with a base router and two satellites which cover our whole house without the need for powerline devices. It took a few tests to position the satellite boxes in the best places but has been far superior to the old solution!
I backup my own boxes across the mesh system to my Synology NAS at the other end of the house.
Gentlemanmike wrote:Fixed!
I looked at the possibility that it might be a powerline adaptor problem and I had heard that the BT ones I was using were maybe not the best. I decided to update them to Devolo ones (I've had these many years ago and they were great; not sure why I changed them for BT ones) and the problem has resolved itself.
Thanks to everyone for their help though.
Hello!
Thanks for sharing what helped you to solve the issue.
Feel free to participate anytime.
Cheers!