• Server won't boot after stable 6.11.0 update


    John S
    • Solved Urgent

    I updated my headless server about 3 days ago from the previous latest stable version to 6.11.0 however it never came back online. After connecting to monitor today I see that it tries to boot gets to the automatic Unraid boot screen then loops and starts over continuously.

     




    User Feedback

    Recommended Comments

    Does the looping start right after the menu or you see some text? If there's some text see if you can catch where it loops with a photo or video.

    Link to comment

    After the menu comes up then below that it says "loading bzimage  Ok" then says "loading bzroot" and reboots.

    Edited by John S
    Link to comment
    Just now, John S said:

    After the menu comes up then below that it says "loading bzimage  Ok" then says "loading bzroot" and then starts over.

    How mmuch memory does the system have?

    Link to comment

    This is an i9-9900k system running with 32gb of memory. Primarily used for Plex. This is about my 6 or 7th plex server but my 1st Unraid. I buillt this one to run on Unraid which it has been since day 1 which is approx 2 years ago.

     

    Link to comment

    It might be worth trying downloading the zip file for the release from the Limetech site and extract all the bz* type files over-writing the ones on the flash.

    Link to comment

    Where can you do that? I'm not seeing a downloadable link or section on the website.

    Edited by John S
    Link to comment
    3 hours ago, John S said:

    Where can you do that? I'm not seeing a downloadable link or section on the website.

    The links for the last 3 stable releases are at the bottom of the Download page - the same one that has the USB Creator tool download.

    Link to comment

    So it's back up and working but not fixed.  I found the download page and downloaded 6.11.0. I copied all of the bz files except for the bzimage and rebooted it. It went one step further from previously. The  bzimage ok (previously shown) and now showed bzroot ok (not previously shown) but it rebooted again from that point. Since I'm not sure what bz files are or what they do I then looked into the previous file folder on the unraid thumb drive and copied all of those bz files and the system rebooted. It apparently reverted back to 6.10.3 but it is working. Couldn't get 6.11 to work so I guess I'll wait on the next update. 

    Thank you for the assist!

    Link to comment

    You need to copy all the bz* files, including the .sha256 files from a release to the root of your flash boot device.  Also should copy the file 'changes.txt' since some plugins look at that to determine release version.

    Link to comment

    That's what we did do. I copied all of the bz files expect the image file, when that didn't work then I copied the bz image as well, no change. Now I did not copy the txt file. I'll go back and try to update it again and if it get stuck again at least I'll have a road map back to getting it working again.

    Link to comment

    So just to make sure that I didn't miss anything, I just repeated the entire process with the same results. I upgraded to 6.11.0 from within the menu. After rebooting the system went into a repeating loop. I copied all 11 bz files + change.txt file from a downloaded copy of 6.11.0, no change. I copied and replaced all bz files & the change.txt from the previous folder. Rebooted and it worked.

    Edited by John S
    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.