Difference between revisions of "Invalid magic number 0 or unrecognized and unsupported file format error on boot"
m |
m |
||
| Line 1: | Line 1: | ||
<yambe:breadcrumb>Server administration tips and tricks</yambe:breadcrumb> | <yambe:breadcrumb self="Invalid magic number 0 or unrecognized and unsupported file format error on boot">Server administration tips and tricks|Server administration tips and tricks</yambe:breadcrumb> | ||
=Invalid magic number 0 or unrecognized and unsupported file format error on boot= | =Invalid magic number 0 or unrecognized and unsupported file format error on boot= | ||
Sometimes suddenly system may fail to boot with particular kernel with error messages of type "Invalid magic number 0 or unrecognized and unsupported file format error on boot". These can be caused by tboot module which can be removed using: | Sometimes suddenly system may fail to boot with particular kernel with error messages of type "Invalid magic number 0 or unrecognized and unsupported file format error on boot". These can be caused by tboot module which can be removed using: | ||
| Line 28: | Line 28: | ||
<yambe:breadcrumb>CentOS|CentOS</yambe:breadcrumb> | <yambe:breadcrumb>CentOS|CentOS</yambe:breadcrumb> | ||
<yambe:breadcrumb self="Invalid magic number 0 or unrecognized and unsupported file format error on boot">Server administration tips and tricks|Server administration tips and tricks</yambe:breadcrumb> | |||
Revision as of 07:35, 27 August 2018
<yambe:breadcrumb self="Invalid magic number 0 or unrecognized and unsupported file format error on boot">Server administration tips and tricks|Server administration tips and tricks</yambe:breadcrumb>
Invalid magic number 0 or unrecognized and unsupported file format error on boot
Sometimes suddenly system may fail to boot with particular kernel with error messages of type "Invalid magic number 0 or unrecognized and unsupported file format error on boot". These can be caused by tboot module which can be removed using:
yum -y remove tboot
Unfortunately tboot uninstallation or removal is not perfect and lines in /etc/grub.conf still refer to tboot module. To make matters worse reinstallation of kernel also does not helps as the new lines added to grub also refer to tboot module even after it is removed. Thus to solve the problem manually edit '/etc/grub.conf' and change entries like:
title OpenVZ (2.6.32-042stab084.14)
root (hd0,4)
kernel /tboot.gz logging=vga,serial,memory
module /vmlinuz-2.6.32-042stab084.14 ro root=UUID=3d38f7f9-b741-411d-9a40-181cb6e946e8 intel_iommu=on rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
module /initramfs-2.6.32-042stab084.14.img
to
title OpenVZ (2.6.32-042stab084.14)
root (hd0,4)
# kernel /tboot.gz logging=vga,serial,memory
kernel /vmlinuz-2.6.32-042stab084.14 ro root=UUID=3d38f7f9-b741-411d-9a40-181cb6e946e8 intel_iommu=on rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
initrd /initramfs-2.6.32-042stab084.14.img
Part of steps learned from http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=migr-5091338
<yambe:breadcrumb>CentOS|CentOS</yambe:breadcrumb>
<yambe:breadcrumb self="Invalid magic number 0 or unrecognized and unsupported file format error on boot">Server administration tips and tricks|Server administration tips and tricks</yambe:breadcrumb>
