ERROR: "/sbin/dracut --force --add-drivers "vmxnet3 vmw_pvscsi vmxnet" while installing vmware tools.
Article ID: 340279
Updated On:
Products
Issue/Introduction
Symptoms:
- Unable to install/upgrade VMware tools
- widely observed for the Linux machine
- While upgrading the vmtools on one of the RHEL 6.7 version encounter an ERROR: "/sbin/dracut --force --add-drivers "vmxnet3 vmw_pvscsi vmxnet" /boot/initramfs-2.6.32-573.e16.x86_64.img 2.6.32-573.e16.x86_64 >/dev/null2>&1" exited with non-zero status. your system currently may not have a functioning init image and may not boot properly. DO NOT REBOOT! Please ensure that you have enough free space available in your /boot directory and run this configuration script again
- vmware-install.log will have similar entries
This program previously created the directory /var/lib/vmware-caf/pme/data/input, and was about to remove it. Since there are files in that directory that this program did not create, it will not be removed.
This program previously created the directory /var/lib/vmware-caf/pme/data, and was about to remove it. Since there are files in that directory that this program did not create, it will not be removed.
This program previously created the directory /usr/lib/vmware-caf/pme/bin, and was about to remove it. Since there are files in that directory that this program did not create, it will not be removed.
This program previously created the directory /etc/vmware-caf/pme/config, and was about to remove it. Since there are files in that directory that this program did not create, it will not be removed.
This program previously created the directory /etc/vmware-caf/pme, and was about to remove it. Since there are files in that directory that this prograam did not create, it will not be removed.
This program previously created the directory /etc/vmware-tools, and was about to remove it. Since there are files in that directory that this program did not create, it will not be removed.
This program previously created the directory /etc/vmware-caf, and was about to remove it. Since there are files in that directory that this program did not create, it will not be removed.
ERROR: "/sbin/dracut --force /boot/initramfs-2.6.32-573.el6.x86_64.img 2.6.32-573.el6.x86_64" exited with non-zero status.
Your system currently may not have a functioning init image and may not boot properly. DO NOT REBOOT! Please ensure that you have enough free space available in your /boot directory and run this command: "/sbin/dracut --force /boot/initramfs-2.6.32-573.el6.x86_64.img 2.6.32-573.el6.x86_64" again.
Execution aborted.
Environment
VMware vSphere ESXi 7.0.0
VMware vSphere ESXi 6.5
Cause
- This happens when the underline Linux machine has been modified, this is not VMware issue, to resolve please do follow the steps or else contact OS vendor.
- This is not related to space query, Inside the OS and also on the datastore level there could be a plenty of space available.
Resolution
1. Reinstall the coreutils package using YUM method
# yum reinstall coreutils
2. Execute rpm -va and verify that there is no "missing" entry for mkfifo as shown below.
# rpm -Va |& tee /tmp/rpmva2.out
3. If no errors exist, execute the below command to verify completion.
# dracut -v -f --debug /boot/initramfs-2.6.32-573.el6.x86_64.img 2.6.32-573.el6.x86_64 |& tee /tmp/dracutmkfifo.out
After performing above steps go ahead and installed vmware-tools.
If YUM is not configured in your Linux Machine, then you need to manually download the coreutils package [ Link will be provided as it depends on linux distributions ]
If any error appears then do check the logs of Dracut log, the log would be available in /var/log inisde the OS. You might see similar to ERROR Failed to install /etc/system-fips
1. Look whether the system-fips file is present under /etc and make sure the extension is proper. In an occasion you might see it as system-fips.bak which you can copy it as system-fips
2. Post correcting the extension re-try installation of vmware tools should go through without a problem
3.Reboot the VM
Feedback
