sittingmongoose

Members
  • Posts

    325
  • Joined

  • Last visited

Report Comments posted by sittingmongoose

  1. 1 hour ago, DiscoverIt said:

    Was it improperly binding interfaces on boot?

     

    It’s just a bit irritating as my first question was if a change to NFS occurred and the only concern was diagnostics and not a single mention of this supposed change. 

    And yet someone else came in here, stated they had the issue, provided diagnostics and unraid was magically able to find and fix the issue...It's almost as if the diagnostics tell unraid what they need to find and fix the problem...SO WEIRD!

    • Haha 1
  2. 15 minutes ago, John_M said:

    No, you're not. That table was for @turnipisum's AMD hardware. In your earlier post you say you have a 9900K for which Intel specifies DDR4-2666.

    https://ark.intel.com/content/www/us/en/ark/products/186605/intel-core-i9-9900k-processor-16m-cache-up-to-5-00-ghz.html

    Ah you are right, sorry.  Either way, server passes 4 days on memtest with no issues so certainly not a problem with my ram.  Also, back on beta 25 it’s not crashing at all.

    • Like 1
  3. 1 minute ago, TwoFive5 said:

    Once it crashes and reboots you won't see anything in the log from before, so nothing would be in there about what caused it. Normally you could turn on syslog server so it would capture those logs before the crash and store them on your server, but that is currently broken until the next release it looks like.

     

    https://forums.unraid.net/bug-reports/prereleases/690-beta25-through-690-beta35-syslog-server-broken-error-in-logs-r1003/

     

    So in your case not having a remote computer to log to sucks. I guess the best option like u said would be to go back to a known working version until newer betas come out.

     

    Mine seems to crash randomly once a week so hopefully I'll be able to catch what is causing it on mine this time.

    Is there an easy to follow how to for logging to another computer?  I might be able to use my dads windows computer as that’s on the same network.

  4. 3 minutes ago, TwoFive5 said:

    That is way more frequent then what I am experiencing. Are you able to get logs before the crash? It might help figure out exactly what is causing it.  Not sure if that is an option for you but I was able to get syslog server running and sent the logs to another computer on my network and using Kiwi syslog server to capture them. 

    I did post my diagnostics and enhanced syslog but I don’t see anything in there at all telling.  And it’s random, it probably won’t crash overnight at all.  But randomly during the day it will.  I can’t even pin down a thing it’s doing to trigger it.

     

    don’t have an option to run a remote syslog as it’s kinda remote.  Nor do I even know how to do that.

  5. 12 minutes ago, TwoFive5 said:

    Yea I realized that as well. I was able to get syslog server up and running incase it happens again so I'll have logs when it crashes. So far no crashes since my earlier comment. Did you revert back to an earlier build, and did that solve the crashes?

    I am going to have to revert back to beta 25 tomorrow.  I was trying to stick with it for a few days so @limetech could look at it and fix it for the future but I can’t wait any longer.  It’s crashing every .5 to 2 hours.  Besides rendering my server pretty much useless, it’s not shutting down gracefully so it’s only a matter of time till something dies.

     

    I’m worried this issue will continue to carry forward into future releases because it started with beta 29 for me.

  6. 15 minutes ago, turnipisum said:

    I've got 8x 16gb strips running at 2133mhz so well within spec. I was running it at 2666mhz which is still in with suggest max. Dropping ram speed was one of the first things i did when i started getting issues as well as memory test.

    image.png.3b686d4a37596a22888260baa0a21c68.png

     

    I am also within spec, 4x16gb of ddr4 3000mhz.  Memtest not showing any errors.

  7. Another update...crashing about every hour randomly.  I tried seeing if Plex might be the cause either through disk access or the gpu and nothing.  I tried like 10 streams, direct play, transcoded and hardware transcoded and that didn't trigger it.  Tried them all at the same time, tried mixing disks, tried only accessing movies on the one sas card versus the other, nothing.

  8. 4 hours ago, turnipisum said:

    Oh crap i don't get it that many times a day revert back to a beta that worked for you. mines random can be 3-5 days a day or like 12 days longest up on beta 35 is 17 days i think.

     

    What is your server hardware?

    asrock z390, 9900k, supermicro 846, 2x lsi 9207(ones an external model and the other is internal), p2000, 3x 1tb 970 evo plus ssds, dual 1200watt server psus. using 1 windows 10 vm but its just idling, I haven't touched the VM since I upgraded at all.  I will try to disable the vm to see if that's it.

     

    I can't pin a rime or reason to it.  No errors in logs, and it seems random, it seems to stay alive through the night and die a few times during the day.....and again, beta 25 is stable.  I am going to roll back but I figured I would stay on this for a few days to let @limetech gather some data to fix it in the next release.

     

    Edit: VMs being disabled didn't change anything.  Just crashed again.  Going to try disabling hard accel aka not using the p2000.

     

    Edit 2: Crashed again with no P2000...So its not gpu related....