dan4UR

My core is up and running. Also connection from android client is up again. Solution: I had to completely remove the Docker container, and manually remove the "roonserver" folder in appdata. Then I did a complete reinstall with allocations within the docker template. After this I wasn't still able to discover the core neither the android client nor Windows 10 Client. The solution was configure a new core. First was to restore from backup, restart the core and after that I logged in with my credentials and now everything ist up again and running.

After roon told me there is an update, I installed it the internal way and until now I'm not able to login or see my roon core. With started roon docker container I'm not able to see log. When stopped I'm able to see the docker log which says "permission denied". Tryed everything. Removing the old Docker, installed it completely new. Moving old appdata ... What else informations do need? Edit: 27.12.2023 22:18:40 /run.sh: line 39: /app/RoonServer/start.sh: Permission denied 27.12.2023 22:19:40 /run.sh: line 39: /app/RoonServer/start.sh: Permission denied 27.12.2023 22:20:40 /run.sh: line 39: /app/RoonServer/start.sh: Permission denied 27.12.2023 22:21:40 /run.sh: line 39: /app/RoonServer/start.sh: Permission denied This is my Log Edit2: 29.12.2023 17:42:05 00:00:00.000 Info: get lock file path: /tmp/.rnsgem0- 29.12.2023 17:42:05 00:00:00.003 Info: GetLockFile, fd: 34 29.12.2023 17:42:05 00:00:00.003 Info: GetLockFile, res: 0 29.12.2023 17:42:05 00:00:00.003 Trace: Nope, we are the only one running 29.12.2023 17:42:05 Initializing 29.12.2023 17:42:05 Started 29.12.2023 17:42:06 aac_fixed decoder found, checking libavcodec version... 29.12.2023 17:42:06 has mp3float: 1, aac_fixed: 1 29.12.2023 17:42:10 Running newest Log. Still no connection to the Roon Core ...

Just wanted to say Thank You @JorgeB. You are my hero 🥰 System is up and running. Did some reboot now, will update every Plugins and Docker and after that I'll start to upgrade to unraid 6.10.

Had to use it with "-f" Now the drive is still listed under UD. Just add it back to the cache pool, or hit the Format button before?

Thats correct. Is it enough to change the share settings from "Cache: only" to "yes" and start the mover ? I'll also shutdown any docker/VM from the settings tab. Maybe also some CA Backup. Some temporary files are not a big deal to lose them, since I can get them back. But docker instances with all the settings would be horror to me. After I added the freshly wiped NVMe back to the cache pool just setting up the old cache shares to "Only" and starting the mover ?

Hey, back again. Did not have much time the last days, but I think I have partially some good news. Disconnected the NVMe placed under UD and startet my rig. But what to do now? Delete dev1 under Historical Devices ? (So I think when I put it back in again, unraid shouldn't places it under UD again) Stop Array, Set Number of Discs of Cachepool to 1 and backup my Data/move it to the Array ? Or Should I now backup/move my Data to the Array ? I think first I'll wait for @JorgeB to look at my diagnostics if everything is OK. apollon-diagnostics-20220520-1035.zip

That will be hardest part of the operation 🤣

You know what. After my homeoffice session I`ll disconnect it from the mb and give it a try. When it's done, just boot and starting the array or anything else to do ?

Or maybe possible to deactivate the device in BIOS ? Or would it still be visible to unraid ?

Okay, will try it. Not that nice, since the NVMes are stored under a heavy heat spreader @ my Mainborad. But hopefully it will work after that 🤗

And here is the new file, but still the same 🤔 apollon-diagnostics-20220512-0951.zip

And here we go See diags after the reboot apollon-diagnostics-20220511-2141.zip Edit: Or should I also start the array ?

Hey @JorgeB, two diagnostics. First after fresh reboot with array stopped (...-1536.zip) Second with manually starting the array (...-1537.zip) Dashboard Screen: I hope someone could help finding a solution for rescueing oder rebuilding my cache pool. apollon-diagnostics-20220511-1536.zip apollon-diagnostics-20220511-1537.zip

Hello, had some big problems with my machine. I`ve got a Enermax AIO watercooler and this little guy just damaged. Was wondering my server was shut down. Then I started it, and just after booting and going to the Dashboard I've seen my lost Cache NVMe. But it was listed in UD 😀 (Yeah its alive) Then I saw my Cache is: Unmountable: no filesystem. After I realized this, the hole machine was hardly shut down. Went to the cellar and realized "Yes, my Server is offline." Took it, and connected it to a monitor to check the BIOS. Ohh hell. CPU Temp went in Seconds from 30°C to something 109°C and then it shut down. Checked the watercooler, disassembled it, cleaned the CPU and cooler block, applied new thermal paste and did another boot up. Same result. Now I changed to the boxed air cooler and e voila, CPU is chilling at 42°C 😇 But what now to do with my broken Cache pool. Disc 2 is still part of the pool, but disc 1 is positioned at unassigned devices. Shoul I still check if NVMe 1 is broken ? SMART doesn't show any error. Only Information I found was for Dev 1 (Cache Pool NVME 1): How can I restore the whole thing. All my Docker and Download Temp is/was stored in the Cache Pool ... 😪

Thats what I think. I'll shutdown my rig and connect a monitor since its headles. Maybe I'll find some information in the Bios.