Grub Error 13 Invalid Or Unsupported
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack error 13 invalid or unsupported executable format redhat Overflow the company Business Learn more about hiring developers or posting ads with us Unix how to fix error 13 invalid or unsupported executable format & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for error 13 invalid or unsupported executable format centos users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up error 13 invalid or unsupported executable format windows 7 and rise to the top Unable to boot VM: Error 13: Invalid or Unsupported Executable Format up vote 5 down vote favorite I used VMWare vConverter and everything converted fine, but when I try to boot I get an error: The physical machine boots correctly, so I don't think it is a source machine issue. I am not sure why the VM won't boot; aren't VMs exact copies of source machines? linux kernel
Error 13 Invalid Or Unsupported Executable Format Windows 7 Ultimate
virtual-machine xen vmware share|improve this question edited Dec 30 '11 at 23:11 Gilles 372k696751126 asked Dec 16 '11 at 19:18 Bob Loblaw 36112 Was this a physical XEN-Dom0 server before? –Nils Jul 28 '12 at 19:39 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote You are trying to boot a Xen-specific kernel, intended for a Xen dom0, and also suitable for a Xen domU. I don't think that kernel works outside Xen. Install a regular kernel for a VMware guest. You'll need to boot from a rescue disk if you don't have any other kernel installed in that VM. share|improve this answer answered Dec 30 '11 at 23:10 Gilles 372k696751126 add a comment| up vote 0 down vote Grub can not find this kernel This could be for several reasions. The name of the kernel is wrong (since this is a xen kernel this would not supprise me). Try editing the line in the grub boot loader and remove the "xen" from the end of it. Grub is looking in the wrong place on the file system for the kernel. Again there is a good chance that this was caused by the V2V, possibly changing the partition numbers. To fix this one try running the following at the grub
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
Error 13 Invalid Or Unsupported Executable Format Rhel
and now I have another one. I've installed arch-enlightenment desktop on a separate invalid or unsupported executable format grub4dos 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 http://unix.stackexchange.com/questions/27001/unable-to-boot-vm-error-13-invalid-or-unsupported-executable-format arch. Interesting. Here is the menulist to make clearer what I mean.# (0) Arch Linux title Arch 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 https://bbs.archlinux.org/viewtopic.php?id=144707 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 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
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 https://bugs.launchpad.net/bugs/365331 Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build https://www.experts-exchange.com/questions/26722521/Grub-Error-13-Invalid-or-unsupported-executable-format.html 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 invalid or 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 invalid or unsupported 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 (lmi
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Grub Error 13 Invalid or unsupported executable format Want to Advertise Here? Solved Grub Error 13 Invalid or unsupported executable format Posted on 2011-01-07 Linux Operating Systems 1 Verified Solution 4 Comments 2,776 Views Last Modified: 2012-05-10 I have a machine setup to boot multiple OSes. The machine is partitioned into 8 partitions. hd(0,0) is setup as the boot partition, the following is the menu.lst on (hd0,0) #################################################################### # Use VI to change the following words according your host: # MYIPADDRESS, MYGATEWAY, and MYDEVICE. # # For example: # # :%s/MYIPADDRESS/192.168.167.33/g # :%s/MYGATEWAY/168.159.120.2/g # :%s/MYDEVICE/sda1/g (Replace sda1 for hda1 or cciss/c0d0p1) # ##################################################################### default 4 timeout 10 title 0 SLES 9 (Not Installed) root (hd0,4) chainloader +1 title 1 SLES 10 (Not Installed) root (hd0,5) chainloader +1 title 2 SLES 11 (sda7) root (hd0,6) chainloader +1 title 3 RHEL 4 (Not Installed) root (hd0,7) chainloader +1 title 4 RHEL 5.5 (sda9) root (hd0,8) chainloader +1 I recently installed RHEL 5.5 on sda9 which is bootable if I set grub to boot to (hd0,8). However if I set grub to boot to (hd0,0) I receive the following error message Error 13: Invalid or unsupported executable format. FYI I run the following commands to set grub to boot to (hd0,0) grub>root (hd0,0) grub>setup (hd0) 0 Question by:jo