Multiple computers backup on NAS
I don't know if anyone is looking at this forum anymore, but I'll give it a try.
I have installed a Synology DS220+ on my Windows network. I have two computers I am trying to back up to it, both running Windows 10. For one computer it works like a charm. The other computer is a problem. I am using a wired connection.
The second computer will back up to a USB-connected HDD. When I try to backup to the NAS it gives me a file system error. When I check the network connection, it tells me that the connection is good.
It appears to be creating the file on the drive, but somehow not finishing the task.
I have attached a backup log in .zip.
Appreciate any help anyone can give me.
Attachment | Size |
---|---|
backup_worker_2022-12-31-20-58-04.0.zip | 2.67 KB |


- Log in to post comments

Steve,
Thank you.
When you say to restart windows, a cold boot, or do you mean a reload?
- Log in to post comments

Thomas, just do a restart of Windows, no need for a reload!
- Log in to post comments

So...I have run VSSDoctor. I am attaching a .zip file including a bunch of logs, the VSS doctor report, and screenshots of various windows. [May be a different reply, since I can't upload files right now for some reason.]
The VSS Doctor report indicates that I don't have enough room in the recovery sector (D:). Everything I know how to do seems to indicate that D: is empty, except for the chkdsk report, which indicates that it has files in it. I don't know enough to know if those are some sort of system file that needs to remain and I can't see in a Dir command, even as an administrator. Do I need to just deep format that logical drive?
The VSS report indicates that there are "Bad Blocks" somewhere on the laptop drive, but I don't know enough to decipher that. I've run chkdsk as Administrator on c: and d: and it says both are clean.
I have one of those 'It seems obvious to me' questions. It will back up to a USB-attached HDD, but not to the NAS. Why would that be?
- Log in to post comments


Thomas, the forum has a maximum upload file size of only 3MB which may be why you are seeing issues doing so. The VSS Doctor report text file should only be a few KB to allow it to be uploaded as a file attachment.
If there are reports of bad blocks then is this from a SSD rather than HDD drive? The drive maker should normally provide diagnostic tools that can check the whole drive rather than checking individual partitions.
Dedicated diagnostic utilities from the disk manufacturers take the longest time to complete the checks, but provide the most accurate methods of checking whether the disk is good or needs replacement:
- Western Digital drives: Western Digital Dashboard
- Seagate disks: SeaTools for Windows
- HGST disks: HGST Windows Drive Fitness Test (WinDFT)
- Intel SSDs: Intel Memory and Storage Tool (GUI)
- Samsung drives: Samsung Magician
- ADATA drives: ADATA SSD ToolBox
- Kingston SSDs: Kingston SSD Toolbox, Kingston SSD Manager
- Transcend SSDs: Transcend SSD Scope
- Silicon Power disks: SP ToolBox
- Toshiba disks: Toshiba PC Diagnostic Tool Utility
- Crucial disks: Crucial Storage Executive
- SanDisk disks: SanDisk SSD Dashboard tool / SanDisk SSD Dashboard user guide
- Log in to post comments

VSS Doctor errors:
Disk Free Space Available:
Some disks have insufficient free space. Perform a cleanup.
C: is OK
D:\ 83MB of 631MB is free. Minimum storage size: 320MB. (Free space is below required minimum.)
EVENT LOG
Some VSS-related errors or warnings occurred during the previous day.
The device: \device\Harddisk0\DR0, has a bad block (I've got a dozen of these.)
So...Would it be possible to unassign D: from the current recovery partition, shrink the operating system volume and create a new partition as D: with about 1GB of space? Can I trick Acronis like that?
Again, running CHKDSK on C: and D: shows no errors. CHKDSK shows 551MB in 13 files on D:, but running DIR on D: in administrator mode shows nothing.
I'm sure you can tell, I'm one of those people who buys software and expects it to just work the way it is supposed to. One time I tried to do something in Acronis and the tech folks finally had to tell me that they didn't know why it didn't work, but if I upgraded to versions it would.
And I don't understand why I can't upload files here anymore.
- Log in to post comments

D:\ 83MB of 631MB is free. Minimum storage size: 320MB. (Free space is below required minimum.)
This is a common error and should have no direct impact. What you can do is to omit that partition from your backup task by going back in to the Source selection > Disks & Partitions then click on the option to show / hide hidden partitions and deselect it.
The device: \device\Harddisk0\DR0, has a bad block (I've got a dozen of these.)
Create an Acronis system report zip file then extract the disks.txt report from the archive and post that as a file upload attachment - this will confirm which drive has the error and what Acronis sees that error as?
See forum topic Scheduled backup REFUSING to run where I have been looking at a disk issue via using the disk report - to see an example.
- Log in to post comments

The files I have been trying to upload are anywhere from 16kb to 257kb. "The file could not be uploaded." Is there any possibility that it's because TI2020 is out of the support window?
I am running Micron Storage Executive on my SSD. I suspect it will take about ten hours total.
I have eliminated non-data partitions from my sources.
FWIW, it is clear that something is happening. There is a .tibx file being created and added to. It appears that the first backup is being done in pieces, as opposed to all at once.
I have started a clean backup. The .tibx file is growing. I'll reply when it's done and try to upload something.
- Log in to post comments

I still don't understand why it would back up to an external USB-connected HDD, but not to the NAS.
Be that as it may, I have tried running Micron Storage Executive on the SSD, and it fails. So there may be a hardware problem. Also, from what I can see, some of the errors in the Disk log may indicate that there are registry problems.
I'm going to throw in the towel and do a cold load of Win10 and see if that fixes things, a draconian solution. If this doesn't work, then I'll just need to replace the SSD.
- Log in to post comments

Thomas,
Reinstalling Windows is an extreme measure. You should attempt to run Windows File Checker first and see if it can help here.
From an admin command prompt or Windows PowerShell run the following sfc /scannow This should run on a SSD fairly quickly. If it finds errors it will let you know and will report if they were fixed. if errors were found run the command again then repeat until no errors are reported.
- Log in to post comments

I did the extreme and ran a cold reload of the OS. It works now. I tried a repair install first, to no avail.
Funny thing. I JUST started getting Steve Smith's replies in my email about 3 this afternoon. 18 days. And still don't have all of them. And do not yet have Enchantech's reply.
Thank you, gentlemen, for your counsel.
- Log in to post comments