I do a daily data backup of certain folders on my MBP to a Synology on my network, using Arq. The destination folder is something like
Today, Arq began failing, and reporting it could not find the destination. I can see the destination in Finder and I can navigate to the destination via a browser. It’s there.
So I start up a new destination (call it "Destination2) and went to configure it in Arq. Arq says it cannot find /Volumes/SynologyHome/Destination2, so I copied the path of that location from Finder and see that something has changed /Volumes/SynologyHome to /Volumes/SynologyHome-1/.
The latter works in Synology, but I don’t know what or why something in MacOS (or Synology OS, or perhaps death rays from Mars) changed it.
What version of Arq?
How is the share mounted? SMB, AFP?
Actually, that info does t matter. I’ve had this happen before. The fix (which you probably know) is to unmount or reboot, delete/rename the existing folder in /Volumes, then mount again.
SynologyHome Already existed, so macOS appended a -1.
Why? I dunno. Didn’t get removed properly when unmountef, etc.
Maybe the same reason my iMac Pro saw itself on my network yesterday and decided it should now be Johns-iMac-Pro-3.
In this case, macOS would have made the second mount point in the /Volumes folder.
If you want to mount, say, home, and /Volumes/home already exists, then macOS will use /Volumes/home-1 to mount the share to.
Sometimes, for unknown reasons (unknown to me), macOS leaves a folder lying around, which can lead to this. Other software may also errantly create the folder, thinking it is copying to a mounted share. That can leave files in the /Volumes/xxxx folder, which macOS would not use to mount a share.
That’s my understanding.