Samba SharePoint Unavailability and Fixes (ref#SA4FLJ)

[benjamin]

Hi @Mark_Sealey,

Thanks for the updates and additional information! A few thoughts on what you’ve shared so far:

There are two overlapping problems:

1. A hung/zombie backup process on the Titan. The "Another backup has already started" error means Roon OS still thinks a backup job is running, likely a ghost from a previous failed attempt. Neither IP address will work until this lock is cleared. The only thing that clears it right now is the full power-pull reset.
2. The multiple RoonServer entries in macOS Local Network privacy. These are almost certainly leftover permission entries from previous Roon installations or updates. They're not causing the hung backup directly, but they can cause the Mac-side "Waiting for server" connection issues after a Titan restart.

For the IP address confusion (reserved vs. non-reserved): The reserved IP (.198) is the correct one to use going forward — that's the one that will stay stable. The reason it showed "jellyfish" (searching) rather than finding the share is likely because the Samba share was configured on the Titan pointing to the old non-reserved address (.210). The share path needs to be re-entered in Roon using .198 and saved fresh.

For the multiple RoonServer Local Network entries: These are harmless duplicates but worth cleaning up. The simplest approach is just to leave only one enabled and leave the rest off. Vadim’s toggle-off/toggle-on advice was right; the key thing is making sure at least one “RoonServer” and “Roon” entry is on.

@Mark_Sealey

But single-clicking on ‘Done’ takes me back to that screen and into a loop

Have you tried clicking the purple IP address? That should open the webUI for you.

The most important part - we’ll need to review a fresh set of Roon Server logs from your Nucleus. Could you please bring the machine back online if possible, it should auto-enable diagnostic mode and get us what we need.

Thank you, Mark!

[Mark_Sealey]

Very many thanks, @benjamin, for your supportive, full and helpful reply!

I have read through it carefully noting everything you suggest.

May we go through the several issues that need addressing in stages, please?

So, first:

@benjamin

1. A hung/zombie backup process on the Titan. The “Another backup has already started” error means Roon OS still thinks a backup job is running, likely a ghost from a previous failed attempt. Neither IP address will work until this lock is cleared. The only thing that clears it right now is the full power-pull reset.

I can see exactly how that has come about. Bearing in mind the need to respect the hard- and software integrity(/fragility) of data, how exactly should I perform the ‘power-pull’ reset, please?

@benjamin

The reserved IP (.198) is the correct one to use going forward — that’s the one that will stay stable… “jellyfish”…The share path needs to be re-entered in Roon using .198 and saved fresh.

I tried that. But without success, I’m afraid. I deleted the .210 address in Roon’s Backup procedure… ‘X’ → gone.

But now I can’t get Roon to connect to the .198 address, even after removing the share in the macOS Settings and adding it again; indefinite jellyfish even after restarting Roon etc.

and:

@benjamin

But single-clicking on ‘Done’ takes me back to that screen and into a loop

Have you tried clicking the purple IP address? That should open the webUI for you.

It doesn’t, No. I get this error.

If you would kindly help with these issues first, please, Benjamin, I believe that will leave these two to deal with next:

removing the old (previous installations, as you say) server instances. Especially because:

they can cause the Mac-side “Waiting for server” connection issues after a Titan restart.

How can I remove them? I can toggle them off in Settings here; but I need to remove them altogether, don’t I?

@benjamin

…review a fresh set of Roon Server logs from your Nucleus. Could you please bring the machine back online if possible, it should auto-enable diagnostic mode and get us what we need…

It is online; and has been active since that last substantive post of mine.

Do I need to reboot Titan now in order for log monitoring on your end to be activated?

Which is the safest way for me to do that, please… hardware, software, web GUI?

Thanks so much again here!