Kendel

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by Kendel

  1. Over 3 days now.... so looks like that fixed it! Thanks for the help! Seems weird that the prior version 6.10.3 of Unraid didn't have a problem with that setting, but working anyways! Marking as resolved.
  2. Running clean so far on 6.11.5 after I disabled the C6 power state. Been a little over a day now.... Crossing fingers.
  3. So disabled everything noted above. Less than 6 hours after the parity check completed the server is again frozen and unreachable. It does seem odd that the server seems to keep churning along while the parity check is in progress (which takes about 1-1/2 days) and than it fails several hours later while the system is idle. Something going to sleep?? The last several times it has crashed I’ve not seen anything in the system log of a recent error etc.
  4. Let the parity check finished, rebooted, and disabled SMT. Less than a day later, complete server crash again..... trying to disable VT-x / VT-d now..... not looking promising.
  5. Ok, so found a BIOS update and made the update. Restarted 1st with 6.10.3, ran for a day or two no issues, so tried the new 6.11.3. Same problem has happened again after about 2 days.....complete frozen server, can't talk to the server and my router shows the computer not even there....... Forced to hard reboot and again parity check is running of course for the next couple of days. This is really a pain. No way to troubleshoot since no errors in the log that appear to amount to anything. I would like to just stay with 6.10.3 for now.... but what are the security risks? Are there separate security patches that can be installed in the meantime to 6.10.3? I see the Unraid website shows 6.11.4 and my server is now saying 6.11.5 is available. This can't be good for all of my hard drives...... Lost on how to proceed.....
  6. Now 6 days in with version 6.10.3. Appears to be an issue with the new version of Unraid and not a hardware problem (unless it is compatibility).
  7. Had reverted back to 6.10.3 when I started this post, so about 2-1/2 days in and no issues on the old version. I'll check back in a few days.
  8. I upgraded from 6.10.3 to 6.11.1. After the upgrade everything appeared to be okay, but within a couple days I found the server locked up. The gui was gone and couldn't connect remotely to the server. Went to the server physically and the screen was blank. No key presses, etc. would bring any prompt or characters to the screen. I was forced to hard reboot. Restarted the server and let it run the parity check. The parity check found some errors, but was expected due to the hard reboot. Another 2-3 days later after the parity check, same problem.... frozen. I disabled and deleted some of the plugins and disabled my dockers. Again the same problem. Reading the syslog, I didn't see anything in the history to show a problem that would cause the system to completely freeze. There are many rsyslog errors and a lot of the gui errors..... so I started being sure to close out of the gui when not in use. Same problem. After several 2 day long parity checks and the worry of wear on the drives, I reverted back to 6.10.3. System ran fine for a few days and then I saw 6.11.2 was released. Hoping this would resolve my issues, I updated again...... Same problems, so today went back again to 6.10.3. Really unclear how to troubleshoot since the server is completely locking up and can't gain any access to troubleshoot and anytime it locks up I have to wait a couple days and have the wear/tear on my hard drives every time. System has worked perfect for a few years before now, so hope the issues can be resolved. Thanks, Kendel kendelmedia-diagnostics-20221108-0000.zip syslog-192.168.1.191.log2.1
  9. Just as a followup..... Roon just had the latest patch to 1.8(build 778). The update went great and no issues. All of my library was still there. Awesome!! Thanks for the help all! Kendel
  10. Thanks All!! I'm trying option B since I've already lost my earlier libraries. Roon is running now building my "new" library. Hopefully this will work whenever the next Roon update comes along.... Thanks again for your help! Kendel
  11. with latest Roon release (1.8 build 764), I tried letting Roon perform its auto-update. I then Stopped the Docker Container and restarted it. My computer app then gave me the "waiting for the Roon core" message and I had to go to select a different one (which was the updated version). When I selected it, it was like a fresh install with no library, missing settings, no audio devices configured etc. Last time for (1.8 build 763) just a few days ago I just tried the update from within the app but with the same results. Since build 763/764 were only a couple days apart I hadn't backed up my library to try to reload it, but I know from a previous update I lost my library anyways and the backup didn't work. It's really a hassle to redo settings, etc. everytime there's a patch to Roon. Any suggestions on what I am doing wrong that a patched Roon doesn't see the newly patched Roon core?? I haven't revised any of the docker settings so I'm confused. Thanks, Kendel