Migz93

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Migz93

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Had another crash shortly after my last post. Put my GPU back in and then removed all reference/usage of iGPU and I've now been up for 9 days with no crash. So for me the issue is related to iGPU with a 9700k on this box. Still very strange that my 2nd box which runs an i5 8400 (which seems to use the exact same UHD Graphics 630 iGPU) didn't crash at all on 6.9.x Theres not much else I can do now as I don't know exactly what with the iGPU is causing the crashes, unless anyone has any ideas for something to try. Thankfully that CPU is powerful enough to run wit
  2. Latest update, moved all my containers except plex back to the main box early/mid last week and still no crashes. Moved plex yesterday and this evening my box has just crashed again, definitely something related to plex & the latest unraid version. Could be iGPU related. I've pulled out my GTX GPU for now incase maybe it's conflicting with the iGPU (Which i doubt). If it crashes again which it probably will, next step will be removing any reference/usage of iGPU from plex and unraid and using software transcoding for a bit. Weird thing is that I had plex runnin
  3. That's exactly what my entry in my go file looks like
  4. Interesting catch! Current update is that I brought docker engine online Wednesday and then brought a small handful of containers on yesterday (tdarr, tdarr-node, telegraf, bazarr & hddtemp) I'm going to get all my containers back up & running minus plex as thats the only one using the iGPU, if still no crashes after a day or two i'll start plex too. Should mention I'm using the hotio image for plex, although have been for the longest time with no issue.
  5. Quick update, currently at 5 days 13 hours uptime with no restarts/crashes. I enabled VMs Saturday evening and started up my single VM on that box. Tomorrow/Thurs I'll enable docker but without any containers and go from there. I also vaguely remember, when i was on the 6.9 betas i think my issue back then was actually a freeze like some people have reported, I'm sure i remember having to actually hold the power button to kill the whole system and then bring it back but then since 6.9 & 6.9.1 stable I haven't had to do that it's just restarting.
  6. Just a quick update, with docker engine stopped on my main box I so far haven't had a reboot since, 1 day 22 hours uptime which is the longest it's gone. Although will wait till at least a week uptime before re-enabling docker engine, seeing if it starts restarting again and work out what container is doing it. I should also mention there's a mix of people having their server hang and become completely unresponsive until rebooted and people who have their server just restart randomly by itself but excluding the reboot part the server is acting fine. My issue is t
  7. I did indeed get another crash since, I saw there was a new unraid release today so I tried that but still another crash since. I went to try safe mode but then found most of my disks don't show because I assume it's not loading the drivers for my LSI card so for now I've reverted to normal boot but with Docker engine turned off. Will see how that goes. Will also see if theres a way for me to just load the drivers for my LSI card so i can use safe mode but still access plex on a 2nd box using the files on the crashing one.
  8. Hmmm, that's interesting. Noticed we both have 1650 variant cards, could be something or could be nothing. Although checking now, i don't have the ICH Nvidia Driver plugin, i did have the original LinuxServer one but as i'm not using the GPU at the unraid level i've just removed it. Will see how my crashes go, if i get another one I'll try removing the GPU completely and if it crashes again i should have Plex & related tools setup on my 2nd box and i can try safe mode.
  9. Thanks for having a look Jorge. I will get it into safemode ASAP, just need to setup my 2nd box to serve my plex and see if it continues to crash.
  10. Hi All, I'm hoping you can help me. I've recently upgraded to Unraid 6.9.0 and since then I've been having regular occurrences of Unraid crashing/restarting. I'm not sure if its actually crashing but I do know it's randomly rebooting. As far as I know I've changed nothing between 6.8.3 which was completely stable and 6.9.0 which has had several restarts since. My box runs 1 Windows 10 VM with a GPU passed through for rarely used remote gaming and then the usual stack of media related containers: Plexs Lidar Sonarrs Radarrs Bazarr
  11. Working perfectly now, thank you very much for such a quick fix!
  12. Thanks for working on that so quick, I can confirm that when I open the webpage for each API instance they correctly identify the other server as online/offline. Although it seems like the MQTT message that's coming in every 15 or so seconds no longer has the "On" entry, one of my messages: { "arrayStatus": "Started", "arrayProtection": "", "moverRunning": false, "parityCheckRunning": false, "title": "GDUnraid", "cpu": "Intel® Core™ i7-9700K CPU @ 3.60GHz", "memory": "32 GiB DDR4 ", "motherboard": "ASUSTeK COMPUTER INC. TUF Z39
  13. Awesome! Both on both, one does have the VM service currently disabled but has an attached USB device regardless.
  14. As far as I can tell it only seems like the on check is incorrect. Its pulling down the other stats like name/array status/dockers correctly
  15. How does the "On" check work? I currently have two Unraid boxes, as the 2nd one has some containers that rely on the first one being up, when I reboot the first one I have to make sure I stop the specific containers on the 2nd one also. Saw this API tool and thought awesome I can just get something configured in HA/Node-Red to automatically stop the containers when I need to but the "On" monitoring seems to be a bit iffy. Originally I had an instance of the API on each box but only configured to point at the box it was hosted on, that obviously didn't capture "On: false" whene