• [6.9.0 and 6.9.1] Experiencing system locks every few days -- logs within


    kaiguy
    • Minor

    Truth be told I'm not 100% sure if this is due to 6.9.x, but the issues did start when I upgraded so I figured I'd give it a shot in here. Prior to 6.9.x, I had zero locks since deploying my current hardware from a year ago. The only material config change since the upgrade was that I began using my nvme drive as my primary cache drive, whereas before it was sitting idle in my server via unassigned devices. Also I no longer use unassigned devices but single- and multi-disk pools.

     

    At least one of the prior locks showed a CPU_CATERR event via my IPMI, but the last one did not (the forum thread on my motherboard had others running into this with prior BIOS versions and Intel Turbo Boost enabled, but I never experienced it). I just lost all connectivity and was unable to access the system via IPMI remote control.

     

    After one of the prior locks, I began running a local syslog server on the unraid server. This is what was captured prior to the lock:

     

    https://pastebin.com/raw/afA6Wd5a

     

    The only thing that stands out to me is CPU tainted errors. It does look like something similar happened earlier in the day, but the system continued to function. When this lock occurred, I believe there was writes occurring to the cache drive. I have since disabled turbo boost in the Tips and Tweaks plugin, and removed some plugins that are not commonly used.

     

    Diagnostics attached.

    titan-diagnostics-20210311-1331.zip




    User Feedback

    Recommended Comments

    Update: I seem to have narrowed down this issue to networking--some combination of utilizing br0 and also enabling "host access to custom networks." Even with containers not using br0 I get the kernel panic/hang when I have the host access option enabled under Docker settings. Something very strange going on. Disabled that setting and I've been good for 4 days.

     

    This report seems to have more action.

     

     

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.