Forums

Jopelepoop
Jopelepoop
Offline
Resolved
0 votes
Today found some updates for samba, so after installing them (needed to temporary add a repo) everything was installed, but samba would not start anymore.
So, i thought it might be a good time to check for more updates.

First did a yum clean all and then a yum update.

Suddenly over 560 updates were found/needed. I decided to install them and after a reboot no i get:

Failed to open \EFI\clearos\grubx64.efi
start_image() returned not found

I did not do a yum update base install before, as i was not aware of the latest distro update of april.

Does anyone know howto fix?

System uses softraid with two disks (mirrored)
Friday, April 05 2019, 06:33 PM
Share this post:
Responses (11)
  • Accepted Answer

    Jopelepoop
    Jopelepoop
    Offline
    Friday, April 12 2019, 06:27 PM - #Permalink
    Resolved
    0 votes
    Dave Loper wrote:

    Can we get an update as to where you are on this issue?



    Hi Dave,

    Well i thought it was already clear that i had fixed it by taking a different route, to copy the missing files.

    After my system was up and running again, i did do a

    yum update app-base
    yum update


    No more problems with grub and/or samba and Clearos at latest version.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 11 2019, 06:22 PM - #Permalink
    Resolved
    0 votes
    Can we get an update as to where you are on this issue?

    Generally speaking if you do this you will satisfy all problems that we are aware of at this time:

    yum update app-base
    yum update
    The reply is currently minimized Show
  • Accepted Answer

    Jopelepoop
    Jopelepoop
    Offline
    Sunday, April 07 2019, 06:05 PM - #Permalink
    Resolved
    0 votes
    Nop, not using the AD connector only directory server
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, April 07 2019, 02:01 PM - #Permalink
    Resolved
    0 votes
    I saw a problem with libtevent and libldb on a business system (not supposed to be updating at this phase) and the Active Directory Connector. Are you using the AD Connector on Community per chance?
    The reply is currently minimized Show
  • Accepted Answer

    Jopelepoop
    Jopelepoop
    Offline
    Sunday, April 07 2019, 12:01 PM - #Permalink
    Resolved
    0 votes
    I know, but unfortunately i only saw about the updated app-base, after i got the problems.
    All started, because i just wanted to update Sambe, for which i saw updates in my console.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, April 07 2019, 11:36 AM - #Permalink
    Resolved
    0 votes
    @Jopelepoop,
    If your system had updated app-base already, all you needed was a "yum clean all" and it would have picked up the missing packages automatically. You would not, however, have done any harm installing the way yo did as the packages in centos-unverified are the same as you'd have got if you had done a "yum clean all". The "yum clean all" would have flushed your yum cache which, at that point, was probably still pointing to the centos 7.5 repos, and it would have then picked up the centos 7.6 repos.

    I'll have to try out Dave's instructions when I get the chance. I know a different way to make the file system read/write.
    The reply is currently minimized Show
  • Accepted Answer

    Jopelepoop
    Jopelepoop
    Offline
    Sunday, April 07 2019, 11:12 AM - #Permalink
    Resolved
    0 votes
    Hi Dave, Nick,

    First of all thanks foyr quick response.

    Let me start by saying i fixed it, but i had to take another route then Dave suggested.

    I already read about the

    chroot /mnt/sysimage
    cd /
    cp -a /boot/efi/EFI/centos/* /boot/efi/EFI/clearos/
    exit
    reboot

    part, but i couldn't do a chroot /mnt/sysimage. Something about not able to do or not able to find (not sure eactly what it said).

    So i decided to try copy it on a different way. I booted not from the Clearos rescue anymore but from one of my other rescue USB devices (yay, lucky me, that i recently created and updated one). From ther i tried several different tools, but in the end with pmagic i could mount the sysimage amongs other partitions. Then i did copy the grubx64.efi file from Centos folder to Clearos.

    After that a reboot presented me with the latest and some previos kernels.

    First i Choose the newest, but at a certain point it took me to a rescue prompt (not seen that one before), so i decied to boot into the previous kernel.

    Then i could boot my Clearos server fine again, i just thought lat's give it another go and run the update to the latest kernel again.

    No problems after that anymore and also Samba was working fine again!

    @Nick,

    Normally only default (none test) repo's are the ones i am using, but when i saw in my console the update for Samba and i tried to update, my system complained about missing depenedencies, regarding libtevent and libldb.

    so installed only those two with:

    yum --disablerepo="*" --enablerepo="centos-unverified" install libtevent and yum --disablerepo="*" --enablerepo="centos-unverified" install libldb

    After that the samba update ran without a problem with the default repo's.

    My grub version at this point is: grub2-2.02.1-0.76.v7.1.x86_64
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, April 06 2019, 01:07 PM - #Permalink
    Resolved
    0 votes
    Make sure to do a manual update and ensure that you are running the latest grub2:

    grub2-2.02.1-0.76.v7.1 or later

    yum clean all && yum update

    Closing the bug. https://gitlab.com/clearos/upstream/centos/grub2/issues/1

    If you already have the issue, follow the troubleshooting steps:


    Boot in rescue mode, perform the following:

    Choose option 1 to attempt to find your ClearOS install and mount it.
    chroot /mnt/sysimage
    cd /
    cp -a /boot/efi/EFI/centos/* /boot/efi/EFI/clearos/
    exit
    reboot
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, April 06 2019, 10:34 AM - #Permalink
    Resolved
    0 votes
    Once you have booted in rescue mode, perform the following:

    Choose option 1 to attempt to find your ClearOS install and mount it.
    chroot /mnt/sysimage
    cd /
    cp -a /boot/efi/EFI/centos/* /boot/efi/EFI/clearos/
    exit
    reboot
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, April 06 2019, 09:40 AM - #Permalink
    Resolved
    0 votes
    If you system is not bootable, use the ClearOS ISO image to boot into rescue mode. Have it try and mount your ClearOS system and then you can view your ClearOS under /mnt/sysimage wiith

    chroot /mnt/sysimage

    From there, we can look at your EFI health under:

    cd /boot/efi/EFI/clearos
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 05 2019, 08:39 PM - #Permalink
    Resolved
    0 votes
    I am a bit confused about what you've done. Which repo did you also enable? You should not have had to enable anything. Samba should have updated from clearos-updates, clearos-centos and possible also clearos-centos-updates. They should have been switched over to the 7.6 repos with last night's update to app-base and are all normally enabled. I'd be concerned it you enabled some of the other repos then did a yum update.

    There is a known issue with the samba update in that it does not restart winbind after installation. A new package is being built I write this. The issue is non-fatal. All you need to do is restart winbind with a "service winbind restart", then samba will start OK (or do a "service smb start").

    What version of grub2 do you have ("rpm -q grub2")? I've asked Dave if he can post about this one.
    The reply is currently minimized Show
Your Reply