• [6.9.0] Won't boot after 6.8.3 to 6.9.0 update


    Jobine
    • Solved Minor

    Hi, I have a little problem with the last update.

    I use the Update Assistant to be sure...

     

    I updated from 6.8.3 to 6.9 and my server was restarting in a loop

    /bzimage...ok
    /bzroot...ok

    and reboot non stop.

     

    Any idea ?

     

    Thank,

     

    IMG_0339 (1).JPG




    User Feedback

    Recommended Comments



    it seems that the unraid nvidia caused issue (source : os update assistant). after uninstall it, the update assistant conclude "No issues were found with your server that may hinder the OS upgrade. You should be good to go"

    Link to comment

    ALL WORK

    16 hours ago, SeeDrs said:

    I've have an issue with the microcode that's in bzroot causing it to hang at "bzroot... OK".  Running on a Supermicro X10 MB with a Xeon E5 V3.

     

    If you want to try without the microcode, after installing the 6.9 update via the GUI, run the following commands before rebooting.

     

    cp /boot/bzroot /boot/bzroot-orig
    dd if=/boot/bzroot-orig bs=512 skip=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') of=/boot/bzroot

     

    Those commands will strip out the microcode.

     

    -SeeDrs

    All works with your commans....

     

    Thank,

    Link to comment

    If I want to install version 6.9.1, am I better off running the commands again, before rebooting ?

     

    Thank,

    Link to comment
    On 3/4/2021 at 12:14 PM, SeeDrs said:

    I've have an issue with the microcode that's in bzroot causing it to hang at "bzroot... OK".  Running on a Supermicro X10 MB with a Xeon E5 V3.

     

    If you want to try without the microcode, after installing the 6.9 update via the GUI, run the following commands before rebooting.

     

    cp /boot/bzroot /boot/bzroot-orig
    dd if=/boot/bzroot-orig bs=512 skip=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') of=/boot/bzroot

     

    Those commands will strip out the microcode.

     

    -SeeDrs

     

     

    Why did you suspect microcode to blame?  Have you seen other reports of this on the web?

    Link to comment

    Based on SeeDrs response, I ran these commands and the 6.9.0 install worked.

    cp /boot/bzroot /boot/bzroot-orig
    dd if=/boot/bzroot-orig bs=512 skip=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') of=/boot/bzroot

    otherwise the boot froze at / bzroot ... OK

     

    For 6.9.1, I just want to know if I would be better off doing it to keep myself out of the problem.

     

    Thank,

    Link to comment
    18 minutes ago, Jobine said:

    Based on SeeDrs response, I ran these commands and the 6.9.0 install worked.

    
    cp /boot/bzroot /boot/bzroot-orig
    dd if=/boot/bzroot-orig bs=512 skip=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') of=/boot/bzroot

    otherwise the boot froze at / bzroot ... OK

     

    For 6.9.1, I just want to know if I would be better off doing it to keep myself out of the problem.

     

    Thank,

     

    I would rather want to find out why installing microcode update prevents boot.  Make sure your motherboard bios is up to date.

     

    Link to comment

    I just saw, it's not up to date, I have the penultimate version (one month before).

    I don't think it makes a difference.

     

    I just don't want to have to go back to 6.9.0 after.

     

    Can I run these commands to avoid (in prevention) the problem?

     

    Thank, 

    Link to comment
    16 hours ago, Jobine said:

    Can I run these commands to avoid (in prevention) the problem?

     

    Sure, it's your server.  But there are reasons Intel goes to great lengths to produce firmware updates.

    Link to comment

    I don't even know what these commands do.

    but it made the update from 6.8.3 to 6.9.0 work

     

    My question should have been, what are these commands for?

     

    Subsequently, I will update my bios.

    Link to comment

    The microcode of the CPU ? or what ?

    Why the update block without these commands ?

     

    How can I correct the problem? Just update the bios ?

     

    Thank,

    Edited by Jobine
    Link to comment
    22 minutes ago, Jobine said:

    The microcode of the CPU ?

     

    Yes.

     

    I would do as Tom suggests and update your BIOS.

     

    Link to comment
    On 3/9/2021 at 5:04 PM, Jobine said:

    Based on SeeDrs response, I ran these commands and the 6.9.0 install worked.

    
    cp /boot/bzroot /boot/bzroot-orig
    dd if=/boot/bzroot-orig bs=512 skip=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') of=/boot/bzroot

    otherwise the boot froze at / bzroot ... OK

     

    For 6.9.1, I just want to know if I would be better off doing it to keep myself out of the problem.

     

    Thank,

     

    I run UNRAID in a VM with GPU Passthrough where hypervisor.cpuid.v0 = FALSE.  I think the issue for me is that microcode cannot be applied to the CPU through a virtual machine causing it to hang.

     

    When hypervisor.cpuid.v0 = TRUE there is no issue applying the microcode. I guess it's able to detect that it's a virtual machine and actually doesn't apply the microcode.

     

     

    -SeeDrs

    Link to comment

    I wanted to update my bios, it's already up to date !

    I had to manually stop the server, it was jammed at "Stopping emhttpd", anyone know why?

     

    Thank,

    IMG_0391.JPG

    Link to comment

    Is there a way to reflash the bios, to be sure?

     

    Any idea for my server which does not reboot with the emhttpd?

     

    Thank,

    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.