Grub Error 13 Invalid Or Unsupported Executable
Contents |
fails with GRUB error 13: Invalid executable format General support questions including new installations Post Reply Print view Search Advanced search 4 posts • Page 1 of 1 nilie Posts: 3 Joined: 2009/05/05 04:02:11 Booting CentOS v5.2 fails with GRUB how to fix error 13 invalid or unsupported executable format error 13: Invalid executable format Quote Postby nilie » 2009/05/05 04:36:10 Hello everybody,I'm trying to
Error 13 Invalid Or Unsupported Executable Format Windows 7
install a dual booting machine with OpenSUSE v11.1 32bit and CentOS v5.2 64bit. I installed OpenSUSE first and allowed it to install and
Centos Error 13 Invalid Or Unsupported Executable Format
configure grub in the MBR and after that I wanted to proceed with CentOS v5.2. The installation went fine with two notable exceptions:- when I had to configure grub installation parameters, CentOS offered me only 2 solutions: either
Error 13 Invalid Or Unsupported Executable Format Windows 7 Ultimate
install it on the MBR of the first hard disk or not installing it at all. Other distributions are more flexible allowing you to install it in the boot sector of the root partition for example. Because I didn't want to ruin the existent grub configuration, I reluctantly accepted not to install it for CentOS assuming that I could manually configure the entry later in grub's menu.lst file.- when I was presented with the options for software error 13 invalid or unsupported executable format rhel components installation, I've clicked on virtualization category/function because I intend to use the machine as a VMware host. There was no guidance on screen at that point and I blindly assumed that by choosing the virtualization function I would get necessary tools and drivers that will help me further on. It seems that this was a wrong move as you can see it below.After completing the installation, I tried to search for a template or guiding on how the menu entry in menu.lst should look like but the grub directory was empty, not surprisingly because I've told CentOS earlier not to install it. Using the files in the /boot directory from the CentOS installation I tried to improvise a menu entry but it's not working. The boot stops with famous Error 13: Invalid or unsupported executable format. Using the file command to check what kind of files I'm trying to load as kernels I'm getting :marte:~ # file /mnt/vmlinuz-2.6.18-92.el5xen/mnt/vmlinuz-2.6.18-92.el5xen: gzip compressed data, from Unix, last modified: Tue Jun 10 19:20:51 2008, max compressionmarte:~ # file /boot/vmlinuz-2.6.27.21-0.1-pae/boot/vmlinuz-2.6.27.21-0.1-pae: Linux/x86 Kernel, Setup Version 0x209, bzImage, Version2.6.27.21, RO-rootFS, root_dev 0x809, swap_dev 0x2, Normal VGAObviously, the CentOS kernel file is not in the right format and the xen word gave me a bad feeling. Doing a little research, I found that the xen kernel contains a Linux kernel that runs on t
jmak Member Registered: 2008-12-21 Posts: 394 Error 13, invalid or unsupported executable format[SOLVED] Hello,I've just finished fixing the partition issue in the morning with much help from this forum community and now I have another one. I've installed arch-enlightenment invalid or unsupported executable format grub4dos desktop on a separate partition and grub can't start the distro. I get “Error 13, invalid or unsupported executable format” message.This is all the more surprising because chainloader +1 never failed me before. I have also Ubuntu installed and arch execute perfectly chainloader +1 with ubuntu – no problem, only arch can't start arch. Interesting. Here is the menulist to make clearer what I mean.# (0) Arch Linux title Arch http://www.centos.org/forums/viewtopic.php?t=13361 Linux root (hd0,0) kernel /boot/vmlinuz-linux root=/dev/sda1 ro initrd /boot/initramfs-linux.img # (1) Arch Linux title Arch Linux Fallback root (hd0,0) kernel /boot/vmlinuz-linux root=/dev/sda1 ro initrd /boot/initramfs-linux-fallback.img title Ubuntu root (hd0,1) chainloader +1 title Arch Enlightenment root (hd0,2) chainloader +1Lots of people having this problem but my search found no usable solution to this problem. Now I have arch-enlightenment installed by I can't start it. Last edited by jmak (2012-07-09 23:50:08) Offline https://bbs.archlinux.org/viewtopic.php?id=144707 #2 2012-07-09 06:56:24 Zancarius Member From: NM, USA Registered: 2012-05-06 Posts: 207 Re: Error 13, invalid or unsupported executable format[SOLVED] Hmm, how did you build/install your kernel? The only times I can recall seeing this is if there was something wrong with the kernel or I had done something by mistake.What you might want to do to eliminate most possibilities is to chroot from an Arch live CD and run mkinitcpio:mkinitcpio -p linuxBe sure your /etc/mkinitcpio.conf has the appropriate hooks for your system, otherwise you might have a working kernel but it won't boot (especially if you're using LVM and forget the LVM hook).This may not be of much help, but it'll be a start to figure out what went wrong. He who has no .plan has small finger.~Confucius on UNIX. Offline #3 2012-07-09 12:22:33 jmak Member Registered: 2008-12-21 Posts: 394 Re: Error 13, invalid or unsupported executable format[SOLVED] This was a regular install following the installation guide. Offline #4 2012-07-09 13:02:08 windscape Member Registered: 2010-04-30 Posts: 69 Re: Error 13, invalid or unsupported executable format[SOLVED] Hi,As a workaround, why not boot the Arch Enlightenment kernel directly, just like you do with Arch itself? Why is a chainloader necessary? Offline #5 2012-07-09 13:11:36 chamber Member From: ~/ Re
Assigned to Milestone grub (Ubuntu) Edit Confirmed Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: grub (Ubuntu) Filed https://bugs.launchpad.net/bugs/365331 here by: sadicote When: 2009-04-23 Confirmed: 2010-01-09 Target Distribution Baltix BOSS Juju https://access.redhat.com/solutions/232313 Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Confirmed Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project invalid or (?) Also affects distribution/package Nominate for series Bug Description I got this immediately after an update and reboot. Tried booting from live CD and using sudo grub-install /dev/sda1 but got a "device not found" message in the terminal. I am/was running Jaunty with occupies my entire 160 GB hdd. I think the Jaunty updater causes the problem when on ext4. Disk invalid or unsupported /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x556b556b Device Boot Start End Blocks Id System /dev/sda1 * 1 19128 153645628+ 83 Linux /dev/sda2 19129 19457 2642692+ 5 Extended /dev/sda5 19129 19457 2642661 82 Linux swap / Solaris ubuntu@ubuntu:~$ Add tags Tag help sojourner (itsmealso2) wrote on 2009-05-08: #1 this occured to me after a fresh install of jaunty ( released version) with ext4 and then changing sources .lst to karmic and updating, all went well until I installed the 2.6.30-1 kernel , with that kernel I would get grub error 13 , with 2.6.28-11 the boot was ok , reinstalling grub from within karmic allowed me to boot the 30-x kernels , there are several reports of this in the karmic dev forum and reinstalling grub does not seem to work for everyone . David Stansby (dstansby-deactivatedaccount) wrote on 2009-05-08: #2 I've had exactly the same experience of sojourner above. Vish (vish) wrote on 2009-06-29: #3 This solved the problem for me, fr
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red Hat Cloud Computing Back Red Hat CloudForms Red Hat OpenStack Platform Red Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss Data Grid Red Hat JBoss Web Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services Back Consulting Technical Account Management Training & Certifications Red Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log Out Language Back English español Deutsc