Linux Error 13 Invalid Or Unsupported Executable Format
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 how to fix error 13 invalid or unsupported executable format 04:02:11 Booting CentOS v5.2 fails with GRUB error 13: Invalid executable format Quote Postby error 13 invalid or unsupported executable format windows 7 nilie » 2009/05/05 04:36:10 Hello everybody,I'm trying to install a dual booting machine with OpenSUSE v11.1 32bit and CentOS v5.2 64bit. redhat error 13: invalid or unsupported executable format I installed OpenSUSE first and allowed it to install and 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 centos error 13 invalid or unsupported executable format had to configure grub installation parameters, CentOS offered me only 2 solutions: either 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
Error 13 Invalid Or Unsupported Executable Format Windows 7 Ultimate
that I could manually configure the entry later in grub's menu.lst file.- when I was presented with the options for software 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 0x80
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support
Error 13 Invalid Or Unsupported Executable Format Rhel
AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu invalid or unsupported executable format grub4dos PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Installation & Upgrades [SOLVED] Get "Error 13: Invalid or unsupported executable format" logging into Ubuntu MATE Having an Issue With Posting ? Do you want http://www.centos.org/forums/viewtopic.php?t=13361 to help us debug the posting issues ? < is the place to report it, thanks ! Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 12 Thread: Get "Error 13: Invalid or unsupported executable format" logging into Ubuntu MATE Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode August 29th, 2015 #1 https://ubuntuforums.org/showthread.php?t=2292617 spython01 View Profile View Forum Posts Private Message Spilled the Beans Join Date Aug 2015 Beans 16 Get "Error 13: Invalid or unsupported executable format" logging into Ubuntu MATE Apologies in advance if I should be posting this first in the Ubuntu-MATE or CentOS forums but the community here seems quite friendly and responsive so here goes: I had originally installed Ubuntu MATE 15.04 on my laptop with separate partitions for root (/) and home (/home), leaving approximately 35GB free in an unallocated partition. I then tried installing CentOS 6.7 into the unallocated space but now, when I try to start Ubuntu MATE via GNU GRUB version 0.97, I get the "Error 13: Invalid or unsupported executable format" message. While I can still log into CentOS, I can now no longer log into Ubuntu MATE. Below is the output of "fdisk -l" run through the CentOS terminal, where /dev/sda1 is the Ubuntu root partition, /dev/sda2 is the Ubuntu home partition and /dev/sda3 is the Ubuntu swap partition. /dev/sda4, /dev/sda5 and /dev/sda6 all pertain to CentOS. How can I boot back into Ubuntu? Thanks in advance. Code: #fdisk -l Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinder
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 https://access.redhat.com/solutions/232313 CloudForms Red Hat OpenStack Platform Red Hat Cloud Infrastructure Red Hat Cloud https://bugs.launchpad.net/bugs/365331 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 invalid or 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 invalid or unsupported 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 Deutsch italiano 한국어 français 日本語 português 中文 (中国) русский Customer Portal Search Products & Services Ba
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 here by: sadicote When: 2009-04-23 Confirmed: 2010-01-09 Target Distribution Baltix BOSS Juju 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 (?) 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 /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, from > http://ubuntuforums.org/showpost.php?p=6977997&postcount=5 Quote: boot from the live medium and chroot into the Linux installation: $ sudo mkdir /mnt/linux $ sudo mount -t ext4 /dev/sda1 /mnt/linux $ sudo mount -t proc proc /mnt/linux/proc $ sudo mount -t sysfs sys /mnt/linux/sys $ sudo mount -o bind /dev /mnt/linux/dev $ sudo chroot /mnt/linux If /boot is on