Issue with Rock on NUC not Automatically Loading Music Folders from Synology NAS (ref#MKHOEL)

[guimx (max)]

@Geoff_Coupe

Bene, puoi mantenere la struttura delle cartelle così com’è sul NAS e aggiungere semplicemente la cartella di livello superiore come singola voce di cartella controllata in Roon…

I’m doing the work (glad to see all tags are being kept correctly), I didn’t think it will take a long time to load all the music but that’s ok, when it’s done we’ll see if the problem persists or is solved.

[DDPS]

Or as an administrative user prefaced with the “sudo” command.

[benjamin]

Hi @guimx,

I see you’ve been helped by some of the best in the Roon community!

@guimx

when it’s done we’ll see if the problem persists or is solved.

Certainly keep us posted on how things go

[guimx (max)]

@benjamin

Tienici sicuramente aggiornati su come vanno le cose

Here we go again, I made the change of the Storage folders reducing them to 2 as in the screenshot below

@benjamin

Certainly keep us posted on how things go

Here we go again, I made the change of the Storage folders reducing them to 2 as in the screenshot below:

[guimx (max)]

Unfortunately the problem has not been solved and Roon still does not see the new music folders that are added… while the ROCK operating system works very well with a very large library on NUC 13 I3, 32GB, 500GB.

[guimx (max)]

Now I proceed by trying the remedy for Synology 916+ suggested above by DDPS

[Geoff_Coupe]

@guimx

Unfortunately the problem has not been solved and Roon still does not see the new music folders that are added…

Not even after you force a rescan of your NAS by using the “3 dots” menu option by your Watched Folders in Roon?

[guimx (max)]

@Geoff_Coupe

Not even after you force a rescan of your NAS by using the “3 dots” menu option by your Watched Folders in Roon?

Yes, by manually forcing the rescan of the folder in Folder Archive, the album is added (this already happened before).

Even the solution /sbin/sysctl -n -w fs.inotify.max_user_watches=800000 does not lead to any results.

In addition, in the same way, deleting disks does not work when they are deleted first in the NAS, and the only way is to do a Restart from the OS mask.
I wonder if there is something to enable in the Bios of the NUC, for example I had seen a checkmark “Force power on the SSD disk”?
Do you think the problem is that it is a NUC 13 that is not officially supported?

[Geoff_Coupe]

@Suedkiez posted the likely explanation for what you are experiencing two days ago at the top of the thread - Your NAS is not telling Roon OS that something has changed in its filesystem.

That’s why there is the scheduled rescan setting in Roon. From the screenshot you posted earlier, it is currently set to be every 4 hours. You can alter this in the Edit Storage Location page:

[guimx (max)]

@Geoff_Coupe

ha pubblicato la probabile spiegazione di ciò che stai riscontrando due giorni fa all’inizio del thread: il tuo NAS non comunica a Roon OS che qualcosa è cambiato nel suo file system.

Ecco perché c’è l’impostazione di scansione programmata in Roon. Dallo screenshot che hai postato prima, è attualmente impostata ogni 4 ore. Puoi modificarla nella pagina Modifica posizione di archiviazione:

Thanks I know there is this setting available, my question is if there is any way to solve the problem of bad communication between ROCK and NAS. The problem is quite annoying since I am used to immediate folder recognition. I would like to know from Roon if there are any possibilities to solve the problem, when will NUC 13 be supported?

[Geoff_Coupe]

@guimx

I would like to know from Roon if there are any possibilities to solve the problem, when will NUC 13 be supported?

That’s two questions both of which are unlikely to be answered directly by Roon Labs.

1. As said earlier, file changes are not being reported to Roon OS by the NAS - and it’s down to the SMB implementation on the NAS to do this - there may be nothing that can be done by Roon Labs in Roon OS to mitigate this. Note: this has nothing to do with your running Roon OS on a NUC 13 - it can happen with Roon OS running on earlier generations as well.
2. Roon are likely to update the list of supported NUCs at some point, but they are very unlikely to pre-announce that fact. It’s not their habit to pre-announce things.

[guimx (max)]

@Geoff_Coupe

Come detto in precedenza, le modifiche ai file non vengono segnalate a Roon OS dal NAS, e spetta all’implementazione SMB sul NAS farlo

as I wrote previously I have some doubts that the problem is with the NAS since under the Windows operating system it works regularly…

[Geoff_Coupe]

Apples and oranges. Whatever the cause, this has been signalled as an issue by Roon Labs since ROCK was introduced:

• Most NAS devices do a poor job reporting changes to Roon, which may necessitate more frequent rescans in order to detect newly added content

[benjamin]

Hi @guimx,

@Geoff_Coupe is pointing you in the right direction here - your best bet is to adjust the automatic rescan interval in the case.

[DDPS]

@guimx

Even the solution /sbin/sysctl -n -w fs.inotify.max_user_watches=800000 does not lead to any results.

What happens when you re-issue the command:

/sbin/sysctl fs.inotify.max_user_watches

If it doesn’t report 800,000, then the value isn’t sticking.

[guimx (max)]

@DDPS

Se non viene segnalato 800.000, il valore non è valido.

I definitely tried and it says 800,000 but unfortunately it doesn’t change the way ROCK and Nas communicate.

[DDPS]

OK, that’s interesting. I am sorry. Perhaps that only works when running Roon on NAS.

[Suedkiez (Just a fellow user like you)]

When running Roon on NAS, the OS accesses the file system directly and the inotify setting will have an effect. If it goes over SMB there are additional layers and it probably depends on the SMB configuration like @Geoff_Coupe wrote

[DDPS]

Yep makes 100% sense.