• CentOS based VM (NethServer) fails to boot (starts the VM but cannot mount volumes inside qcow2 image)!


    NLS

    The VM fails to boot exactly after the graceful reboot to update to 6.12!

    Can it be related to KVM version change?

     

    A Windows based VM works fine.

    HELP!?

     

    boot-issue.thumb.png.a195e125c3060d0d19d9d87ed68dd8af.png




    User Feedback

    Recommended Comments

    The issue seems to be UNRAID.

    Aside from the attempts I have made (I can provide the details) to recover OS booting, I now tried a fresh install.

    (the same I used when I originally set up NethServer inside UNRAID years ago)

    The installer crashes, because seemingly of network issues, as it reports "couldn't open file /tmp-network-include".

     

    Back on the existing installation, note that the qcow2 image itself is fine, I managed to connect it to UNRAID (host), see the partitions inside (including the lvm partitions root and swap), I managed to mount the root partition and see the files inside.

    So the disk image is ok.

     

    The problem started right after 6.12 reboot.

    Something changed in kvm/libvirt/qemu/uefi that prohibits NS7 from running.

     

    Link to comment

    NEWER UPDATE which seems to point UNRAID as the probem.

    Attempting to install fresh does NOT find any usable disk and does NOT find any usable network!

    Seems that with 6.12, CentOS7 does not recognise ANY virtio device!

     

    So I changed vdisk to be SATA and network to be e1000 and it works!

    Definitely an issue!

    Link to comment

    Changed Status to Open

    Changed Priority to Other

     

    Pity nobody actually reacted when priority was urgent.

    Edited by NLS
    Link to comment
    6 hours ago, NLS said:

    Pity nobody actually reacted when priority was urgent.

    How is it urgent? There is a workaround.

     

    Not a showstopper, data loss, or server crash.

    Link to comment
    14 minutes ago, JonathanM said:

    How is it urgent? There is a workaround.

     

    Not a showstopper, data loss, or server crash.

     

    This is why I changed the priority.

    But before finding the solution myself, it was urgent at least to me, as NethServer (which is a full small business server, so potentially important to some of us) was not running. No mail etc.

     

    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.