JDGJr

Did you make it to 2 weeks? I'm happy to report that making those changes to my 7.1.4 system has given me 16+ days of uptime! Haven't had this in months.

Thanks for posting this. I'm still trying to prove my 7.1.4 system isn't crash prone. (I am wary of moving to the next beta) Interestingly, I made the /mnt/user -> /mnt/cache changes late this week - mostly to become consistent. I hope that gives me the positive result you're looking for. Question: do you see a line similar to 'CIFS: VFS: \\Server has not responded in 180 seconds. Reconnecting...' at the end of the syslog when your machine crashes?

I do not have Connect installed. Auto backups run once a week, but the system had been stopping every other day. I'm still prepping for rolling back to 6.12 and system has been more stable since I posted here. But I've been doing a lot of backups to other systems overnight when the stoppage had been common.

I've had the same problem with 7.1.4 - started with 7.0.1 but was less frequent back then. The only useful output I've seen appears in the log window if you have it open (it is not written to the log file): Server kernel: CIFS: VFS: \\Server has not responded in 180 seconds. Reconnecting... Most times it dies around 1:15am, hours after the last drive has spun down (noted in the log) I need to rollback to 6.12 - same hardware was stable back then.

I got this working! The discussion here was a big help. Question: Where have others located their mailbox files? I don't want to spin a HDD every time an email arrives or is read, but I can see the benefit of having the data protected by the array. Should I be concerned about the continuous activity on my main cache SSD? Maybe add a non-array SSD dedicated to email server files? Any suggestions on best practices? Thanks

My issue was resolved by upgrading from 6.8.3 to 6.11.5 and uninstalling and reinstalling docker image

I'm seeing same issue, even after forcing an update 10 minutes ago. Is there a way to rollback to a previous version (I don't need new functionality)

Yes, update went smoothly and your example for the port assignment helped. Took almost no time. Thanks for an excellent container!

Can anyone comment on their success upgrading to Roon 2.0?

Yes! I've upgraded several times and no problem

Same here! So glad this is working.

Should I add this disk to my array? Just ran preclear on a 10TB WD Elements external drive and it reported: # ATTRIBUTE INITIAL CYCLE 1 STATUS # # 5-Reallocated_Sector_Ct 0 1 Up 1 # Should I return this drive, run another cycle to see if it increases, or add the drive to my array? Thanks, John

I've switched to an older NUC (Intel NUC6CAYH) with 8 GB, similar to wcg66. I bought used it for less than $150 to be able to stream multichannel audio thru Roon, and it is working perfectly - now for multichannel and also as the server. I was able to easily upgrade Roon server software from 610 to 667.

Anyone have success upgrading to build 667? I was prompted to upgrade and it failed to restart. Eeven uninstalling the container and reinstalling and applying a backup didn't give me a running server. I'm running off a NUC temporarily, will try to get functional tomorrow. Is there a process to roll back to a working version (611? was working for me for almost a month)

I've been running L2.32 since setting up my new hardware around the 25th. Seamless operation here