After trying a bunch of other network and system trouble shooting things, I decided it was time to take the drastic step of replacing my seemingly working current Roon database with one from late last year. Sure enough that fixed the problem! So, it seems that Roon had corrupted its database AGAIN!!! Yes, this is the third database corruption I’ve had to deal with in as many years. And, it’s not sever specific beacuse I’ve experienced Roon database corruption on two different sever hardware setups.
@Daniel Thanks for your help, however, it would be great if you can let the developers know that this Roon’s penchant for corrupting its own database is something that needs to be addressed at the software architecture level. Whatever database technology you are using for the library is simply too unreliable for a consumer product. See the I would assume that Roon is using the latest DB technology - #40 by xxx thread for others who feel the same.