• Centos not working after upgrading to 6.9.1


    Lilarcor

    Everything is fine when I upgraded unraid os from 6.8.3 to 6.9.1. But one of my vm(centos 7, 3.10.0-957.27.2.el7.x86_64) isn't working any more. It's bootable, means I can see the kernel core selection splash screen, after that, the cursor stops in a black screen then no more movements. So far, I have to rollback to 6.8.3 so the centos vm is working again. 




    User Feedback

    Recommended Comments

    Not hijacking this topic, but I have the same problem. After updating the VM template I got this error. My Ubuntu VM's still working after the upgrade to 6.9.1

     

    But all the CentOS VM's showing this error after updating:

     

    image.thumb.png.770897e465337a48f77c3b820f35c0c1.png

    Link to comment
    On 4/7/2021 at 12:02 PM, Leandres said:

    I have the same problem.

     

    That isn't the same problem reported by the OP. Yours is different. What is at the PCI address shown in the error message?

    Link to comment

    The error above disappears when I don't choose 2.0 (EHCI). After selecting one of the others I'm able to update te template. But the VM still doesn't boot up....

     

    image.png.f69bfe4138e00ff0b0a28323c127577d.png

     

     

    After Grub:

    image.thumb.png.3268c0db4546eccfe74ad933a1276ed4.png

    Link to comment

    Just VNC.

     

    I just gets better: after downgrade my OS, my complete cachepool (4 disks SSD) is not configged anymore. Which means all my VM's and dockers are gone / not accessable 

     

    How to make those 4 disks get back into the cache pool so I can access my data?

    Link to comment
    6 minutes ago, Leandres said:

    Just VNC.

     

    I just gets better: after downgrade my OS, my complete cachepool (4 disks SSD) is not configged anymore. Which means all my VM's and dockers are gone / not accessable 

     

    How to make those 4 disks get back into the cache pool so I can access my data?

    Reverting back to 6.8.3

    If you have a cache disk/pool it will be necessary to either:

    restore the flash backup you created before upgrading (you did create a backup, right?), or

    on your flash, copy 'config/disk.cfg.bak' to 'config/disk.cfg' (restore 6.8.3 cache assignment), or

    manually re-assign storage devices assigned to cache back to cache

     

    This is because to support multiple pools, code detects the upgrade to 6.9.0 and moves the 'cache' device settings out of 'config/disk.cfg' and into 'config/pools/cache.cfg'.  If you downgrade back to 6.8.3 these settings need to be restored.

    • Thanks 1
    Link to comment

    Yes I made a backup, the config is back and my cache pool is working again. My heart almost stopped working... ;-)

     

    Now I will wait untill the CentOS bug is fixed before I upgrade my OS again. 

     

    Tnx Simon!

    Link to comment
    3 minutes ago, Leandres said:

    Yes I made a backup, the config is back and my cache pool is working again. My heart almost stopped working... ;-)

     

    Now I will wait untill the CentOS bug is fixed before I upgrade my OS again. 

     

    Tnx Simon!

    Good to hear that info was in 6.9.0 announcement but doesnt seem to be in later ones.

    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.