Scheduled backups failed due to changed IP address on MacStudio (ref#XV6K3K)

[Mark_Salkind]

What’s happening?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

As of 3 weeks ago, all of my scheduled backups (I had four) are showing "Backup failed at .../Selected drive is full" None of the drives are full, as they are on a MacStudio with significant amounts of memory available. What did happen is that the IP address for the MacStudio (where backup folders are located) changed. I've tried to specify the new shared folder (using new IP address) with no success. I'm beyond frustrated as this must be the 10th time I've sought support for regularly scheduled backups that somehow stop working. For your information, it's a MacStudio running Sequoia 15.0.1. And also for your information, the four regularly scheduled backups have been working for the past five months or more.

Describe your network setup

Pakedge RK-1 Router; Nucleus is hardwired to Ethernet via a QNAP QSW-1208-8C-US 12 Port Unmanaged 10GbE Switch Twelve SFP+ with Shared Eight 10GBASE-T Ports

[Suedkiez (Just a fellow user like you)]

This is supposed to be a folder path, yes?

Why are you using > characters instead of / slashes to delineate folders?

[Mark_Salkind]

I just tried using slashes as you suggest and I still get the same result (see attached screenshot).

In fact, the moment I’ve completed entering the specified folder location, I get the message in red, even before I’ve clicked Add network share.

[Suedkiez (Just a fellow user like you)]

And what about the Username? The one you entered has a space, but Mac account names can’t have spaces.

FAQ: How do I create a shared folder on Mac and add it as a watched folder in...

[Mark_Salkind]

I removed the space in my username and voila, I was able to access the IP address/Users. However, as you can see from attached screenshot, I cannot access marksalkind, which is where the Roon_Backups folder is located.

[Suedkiez (Just a fellow user like you)]

Hmm. In the past this seems to have sometimes been caused by special characters in folder names, like here

"error loading folder unexpected error" after switching Roon Core

fixed issue by manually shifting folder by folder, had a folder with a extremely long folder name in Chinese, deleting that folder fixed it

Might be other causes too, a forum search for loading folder unexpected error brings up a range of cases. I don’t have a quick solution.

Maybe try to remove Roon_Backups from the path in the Network Share Location setup

[Mark_Salkind]

I really appreciate your help.

Here’s what’s interesting: when I click browse, then Add network share, I immediately get a message in red saying: “You can specify a directory in the share location as well, but it will be ignored.” That is, the message appears before I’ve even entered the Network share location and my username. I’ve rebooted my Nucleus Titan twice – and I still get the same result. I’ve also restarted the MacStudio but with no change.

When I remove the Roon_Backups from the Share location, I still get the same message (see the second attached screenshot): Error loading folder UnexpectedError.

Can someone from technical support at Roon provide some help here?

[benjamin]

Hey @Mark_Salkind,

Have you investigated the Mac at all in your setup? We’ve seen frequent reports of handshake issues between Roon and the recent Sequoia updates and is definitely worth taking a closer look at.

First, can you please navigate to macOS System Settings > Privacy & Security > Local Network , and make sure Roon is allowed. If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists.

If it does, here’s an article that you may find helpful for additional folder-sharing options via Mac:

FAQ: How do I create a shared folder on Mac and add it as a watched folder in...

[Mark_Salkind]

Let me quickly recap my problem (please bear with me):

I had four locations set up for scheduled Roon backups, as follows:

smb://IP_address/Users/marksalkind/Roon_Backups
smb://IP_address/Users/marksalkind/RoonBackups_New
smb://IP_address/Samsung T5/RoonBackups (an external SSD connected to Mac Studio)
smb://IP_address/Desktop/RoonBackups

Everything was working fine up through October 6th and was working fine with the Mac Studio running Sequoia 15.0.1

I left for a three-week trip abroad on October 8th and shut down my Mac Studio. As a result, the backups could not take place. When I returned from my trip and started up the Mac Studio and Roon, I saw a message that “Backup had failed; disc full” or something to that effect. I also discovered that my Mac Studio (directly connected to Ethernet) now had a new IP address.

I am familiar with the file sharing FAQ article – and clearly everything was set up correctly in terms of file sharing before October 6th or I would not have been able to have the regularly scheduled backups occurring without a problem for several months.

I have now removed all of my previous share locations and rebooted my Nucleus Titan. I’ve also deleted all of my shared folders under System Settings on the Mac Studio, rebooted the computer, and re-established all of my shared folders. I also tried what you suggested: toggling on and off Roon under Privacy & Security and rebooting the computer – this did not resolve the problem.

I have been able to establish a successful network share location using the externally connected Samsung T5 hard drive. But when I try to add network share using the other three locations I had established (now using the new IP address), I immediately receive a message saying “You can specify a directory in the share location, but it will be ignored.” And this message in red appears even before I have entered information about the location of the network share. This is a Roon notification, not a Mac Studio notification – see the first attached screenshot.

I do have a question about how to configure shared settings on the Mac Studio – see the second attached screenshot. Do you need to created shared folders for all parts of the location – or just the final destination folder? For example, for smb://IP_address/Users/marksalkind/Roon_Backups, do you need to create a shared folder for Roon_Backups and in addition for Users and marksalkind? Also, is it Mark Salkind (username on Mac Studio) that should be set to Read & Write, or Staff, or Everyone? If I try to set Everyone to Read & Write, Mac Studio doesn’t seem to allow this, as it will revert to Read Only. Any light you can shed on this would be helpful (none of it covered in the file sharing FAQ article).

Finally, I’m assuming Roon doesn’t need full disk access for file sharing to work.

Thanks for your help resolving these issues. At least I’m able to backup to the externally connected SSD Samsung hard drive.

– Mark Salkind

[noris]

Hello @Mark_Salkind ,

You mentioned removing the space from your username to access the folder but I don’t see your username on the access list screenshot you provided. I would look over your Mac User settings to determine the current username and add it to the access list. If you add the root folder as a shared folder, it should add the sub folders as well.

[Mark_Salkind]

I have added marksalkind to the list of shared folders under Settings, but I still cannot access Roon_Backups, a subfolder within IP address>Users>marksalkind.

Please review the screenshots I’ve attached:

1. Screenshot of Shared folders under Settings
2. Screenshot of Add Network Share dialogue box once I’ve added marksalkind under Shared Folders
3. Screenshot of my previously regularly scheduled backups (prior to turning off my computer for several weeks while traveling and the subsequent change in the computer’s IP address)

I’ve now literally spent several hours trying to address this issue. I have no understanding why I was able to access the backup folders previously but cannot do so now.

My plea: is there anyone on Roon’s technical staff who is familiar with MacOS (there must be, as I believe the CEO of Roon is a Mac user) and can help resolve this problem?

[daniel]

Hi @Mark_Salkind ,
I see that you’ve just been trying to connect with the IP address. Have you tried connecting with hostname instead?

[Mark_Salkind]

Yes, I tried repeatedly to connect this afternoon using the hostname, without success. Roon still responds: “Invalid network path specified.” Please see the screenshot I’ve attached.

– Mark

[Singleton (- Audio Astronaut)]

@Mark_Salkind ,

Try flushing the cache then rebooting your Mac.
https://help.dreamhost.com/hc/en-us/articles/214981288-Flushing-your-DNS-cache-in-Mac-OS-X-and-Linux

[Mark_Salkind]

I did flush the cache and rebooted the MacStudio. Still no success (see attached screenshot). This time I received this message: There was an Unexpected error: UnexpectedError. If I use the hostname, I receive this response: Invalid network path specified (see the second screenshot).

– Mark

[Singleton (- Audio Astronaut)]

@Mark_Salkind @benjamin @noris @Daniel ,

I believe Apple changed some of macOS Sequoia’s syntax and didn’t let anyone know. In any event I believe I’ve solved the case. Please review the example below and apply these findings to your Mac and let me know.

Singleton:

local host name “Nasa”

User name “Audio Astronaut”

Failed under macOS Sequoia testing:

• smb://172.20.10.4/users/audioastronaut/music/moonrocks

• smb://nasa/users/audioastronaut/music/moonrocks

• \172.20.10.4\users\audioastronaut\music\moonrocks

• \nasa\users\audioastronaut\music\moonrocks

I discovered that the following series of syntax on multiple machines work. I’ve found no mention of it in my research having discovered it while testing to resolve your issue.

100% success rate under macOS Sequoia:

• smb://172.20.10.4/moonrocks

• smb://nasa/moonrocks

• \172.20.10.4\moonrocks

• \nasa\moonrocks

Notice that your local host name or IP and a terminating directory are all that are required.

If your’s or any current Roon users media directory terminates at any of the 6 directories below I highly suggest relocating to a subdirectory in anticipation of future updates and or potential errors. I suspect that this may also have something to do with an issue of incorrect file permissions reported here as well. All the best.

[Mark_Salkind]

Yes, you have indeed solved the case! The syntax that you suggest works!

Thank you so much for experimenting to find the solution. Very much appreciated.

Mark