jzawacki

Members
  • Posts

    37
  • Joined

  • Last visited

Report Comments posted by jzawacki

  1. 4 hours ago, JorgeB said:

    Change to ipvlan or update to v6.12.4 and see the release notes.

    Good luck with that.  When I attempted to use ipvlan, the entire unraid server had issues talking to the network.

     

    I was hoping to no longer be a part of this topic as my server had been running fine for over 6 months without issues.  Then, being super dumb, I updated to 6.12.4 and the server kernel panic'd literally the next day.  Hopefully, after it finishes a parity check, it'll go back to normal.  Fingers crossed.

  2. 22 minutes ago, sage2050 said:

    glad I found this thread...

     

    I wish there was a solid answer/fix.  For me personally, It had to do with one of the dockers.  I installed docker and portainer on my backup server, moved a bunch of dockers to it, and although I still have 9 dockers running full time on unraid, my server uptime is currently 21 days and I can't remember the last time it kernel panic'd.  Now, since I'm posting this, it'll kernel panic by the end of the night.

  3. Well, I had to switch back to macvlan due to some network weirdness.  unraid had been running for 20 days without issues, but I had some dockers that wouldn't stay connected and it wasn't till I realized that unraid couldn't check to see if there was a version update available, did I blame it on the docker ipvlan setting.  Switched it back to macvlan and all the network weirdness went away and the server hasn't kernel panic'd yet, so I'm keeping my fingers crossed.

  4. There is a lot of info here.. so I'm just going to chime in so that I receive notifications as this thread progresses.  Not speaking on the cause of anyone else's kernel panics, but mine match a few of these screenshots verbatim. 

     

    I've been running Unraid for as long as I can remember and running dockers since they were originally introduced.  My server has been rock solid this entire time, even after upgrading MB/Proc/RAM, adding 10G NICs, replacing HDDs, etc.

     

    Even with 6.9.2, never had any issues.  Out of the blue, I decided to upgrade to 6.10.0 and everything went south.  Random kernel panics.  Obviously, blaming it on the upgrade, reverted to the previous version, 6.9.2 but the kernel panics continued (in hindsight, is it possible that 6.10.0 made changes to the docker configs causing 6.9.2 to continue having issues?).  Doing the research, assumed it was hardware related and replaced the MB/Proc/RAM and the kernel panics continued.  I noticed that it appeared the kernel panics seem to happen around the time the Appdata Backup/Restore was scheduled, so I started diving into that.  Found some errors accessing files, so thought it might be corruption issues.  Resolved all that, moved appdata to different drives, on to/off of cache, etc.  Turned off all containers and slowly turned them on, one at a time (over the course of a month), to see if I could pinpoint the cause, but nothing was repeatable.  Everything appeared to be random.  As of two days ago, my server had been running for 28 days with all dockers running without issues.  So, when it kernel panic'd the other day, I remove Appdata Backup/Restore, moved everything docker related onto the protected array and it kerenel panic'd that evening.

     

    Anyway, latest change I am testing (finger's crossed) is changing the docker setup to use ipvlan instead of macvlan.  if that doesn't work, I'm going to plug another NIC in and try using eth# instead of br0 for the dockers that need a static IP to operate properly.

     

    PS:  I learned of ctop, which is like top for docker containers.. loving it.  Wish it was built into Unraid or that Unraid had that information available within the web GUI.