Grub Error Invalid Or Unsupported Executable Format
Contents |
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 desktop on
Error 13 Invalid Or Unsupported Executable Format Redhat
a separate partition and grub can't start the distro. I get “Error 13, invalid error 13 invalid or unsupported executable format windows 7 or unsupported executable format” message.This is all the more surprising because chainloader +1 never failed me before. I have also Ubuntu installed error 13 invalid or unsupported executable format centos 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 Linux root (hd0,0)
How To Fix Error 13 Invalid Or Unsupported Executable Format
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 #2 2012-07-09 06:56:24 Zancarius Member
Error 13 Invalid Or Unsupported Executable Format Windows 7 Ultimate
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: ~/ Registered: 2012-03-29 Posts: 279 Re: Error 13, invalid or unsupported executable format[SOLV
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki invalid or unsupported executable format grub Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation
Error 13: Invalid Or Unsupported Executable Format Cisco
User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu error 13 invalid or unsupported executable format centos 6 Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [SOLVED] Error 13: Invalid or https://bbs.archlinux.org/viewtopic.php?id=144707 Unsupported Executable Format Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 7 of 7 Thread: Error 13: Invalid or Unsupported Executable Format Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch https://ubuntuforums.org/showthread.php?t=1517773 to Threaded Mode June 25th, 2010 #1 vmsean View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Jun 2010 Beans 4 Error 13: Invalid or Unsupported Executable Format Hello all, I've searched all over the internet and have found numerous threads on this topic, none of which have helped me fix the problem. I'll post as much info I can about my setup. I have 3 hard drives... one is for ubuntu (9.10), one is for my data, and one is for Windows7. It looks like this: 1st drive (hda) = ubuntu 2nd drive (hdb) = data 3rd drive (hdc) = windows I used to be able to dual boot no problem (via grub menu) until I updated to Ubuntu 9.10 awhile ago. Now I get the ever so popular "Error 13" message anytime I try to boot into Windows. I've tried everything with regards to tweaking my menu.lst file. The odd thing is, if I physically remove drives 1 & 2, my computer will boot into windows with no problem, wh
HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie GRUB http://www.linuxquestions.org/questions/linux-newbie-8/grub-error-invalid-or-unsupported-executable-format-638484/ error: Invalid or unsupported executable format User Name Remember Me? Password https://bugs.launchpad.net/bugs/365331 Linux - Newbie This Linux forum is for members that are new to Linux. Just starting out and have a question? If it is not in the man pages or the how-to's this is the place! Notices Welcome to LinuxQuestions.org, a friendly and active Linux invalid or Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink invalid or unsupported is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux
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 a separate partition, this partition must also be mounted: $ sudo mount -t ext4 /dev/sdaX /boot Then, the following command should resolve the issue. : $ sudo grub-install --recheck /dev/sda Leo Milano (lmilano) wrote on 2009-07