Jump to content
  • No network after 6.8 upgrade with 802.3ad


    ksarnelli

    I just upgraded from 6.7.2 to 6.8.0.

     

    I have link aggregation configured using 802.3ad and after the upgrade my unraid server was no longer accessible from my network.  I accessed the console through IPMI and can see that br0 has a reserved IP in the 169.254.X.X range, indicating that it couldn't contact the DHCP server.  Already tried rebooting again.

     

    Everything was working (for years) before the upgrade.  Any ideas?



    User Feedback

    Recommended Comments

    Please open a topic under general support instead of this bug report.

    Bonding is working fine with Unraid 6.8. Something in your system and/or environment is likely not correct.

    image.png.56e085d56cc4821151000b375e9ca0f1.png

    Share this comment


    Link to comment
    Share on other sites
    2 minutes ago, bonienl said:

    Please open a topic under general support instead of this bug report.

    And please also add the diagnostics ( tools -> diagnostics ) to that post.

    Share this comment


    Link to comment
    Share on other sites

    I'm surprised to see someone had the same problem as me. My issues mysteriously disappeared after 4 to 5 restarts. All is ok now. I hope your issues dissolve as easily as mine did.

    Regards

    Share this comment


    Link to comment
    Share on other sites
    6 hours ago, BrettC said:

    I'm surprised to see someone had the same problem as me. My issues mysteriously disappeared after 4 to 5 restarts. All is ok now. I hope your issues dissolve as easily as mine did.

    Regards

     

    Apparently we weren't the only ones, I found this thread: 

     

     

    As far as adding diagnostics it's not that simple without a network connection and the only access being a console via IPMI.  I'm pretty sure it has something with bonding+bridging but I didn't have time to continue experimenting and finally just disabled bonding in unRAID and disabled the LAG on my switch to get the server running again.  Not sure when I will have time to troubleshoot further.

    Share this comment


    Link to comment
    Share on other sites
    2 minutes ago, ksarnelli said:

    Not sure when I will have time to troubleshoot further.

    If you find time, open a topic under general support.

    So far people reporting network issues had some (lingering) configuration mistake in their network settings.

    Newer linux kernels are less forgiving to mistakes and this becomes apparent when upgrading.

    Share this comment


    Link to comment
    Share on other sites
    7 minutes ago, ksarnelli said:

    As far as adding diagnostics it's not that simple without a network connection and the only access being a console via IPMI.

    From the IPMI console type

    diagnostics

    This saves a zip file on your flash device under folder /logs.

    You can take the flash device out (after shutting down your server) and post said file.

    Share this comment


    Link to comment
    Share on other sites
    2 hours ago, bonienl said:

    From the IPMI console type

    
    diagnostics

    This saves a zip file on your flash device under folder /logs.

    You can take the flash device out (after shutting down your server) and post said file.

     

    Thanks - next time I have a chance I will do that and post to general support as you requested.

    Share this comment


    Link to comment
    Share on other sites


    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.