Boot Error 13
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 06 Oct 2016 19:08:10 GMT by s_hv987 (squid/3.5.20)
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
Chainloader /bootmgr Error 15
this forum community and now I have another one. I've installed arch-enlightenment
Error 13 Invalid Or Unsupported Executable Format Redhat
desktop on a separate partition and grub can't start the distro. I get “Error 13, invalid or error 13 invalid or unsupported executable format centos 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 http://answers.microsoft.com/en-us/windows/forum/all/windows-7-no-boot-error-13invalid-or-unsupported/728c7727-34b8-428a-af44-ec62fd27dd9f – 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) 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 https://bbs.archlinux.org/viewtopic.php?id=144707 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 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
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 AskUbuntu Official https://ubuntuforums.org/showthread.php?t=1517773 Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu http://unix.stackexchange.com/questions/27001/unable-to-boot-vm-error-13-invalid-or-unsupported-executable-format Forum Community Ubuntu Official Flavours Support General Help [SOLVED] Error 13: Invalid or Unsupported Executable Format Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is error 13 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 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 error 13 invalid 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, which sort of tells me that I don't need to run any recovery on the windows drive. Anyhow, here's an output of relevant info. Any help would truly be appreciated. sudo fdisk -l Code: Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x76a6af7e Device Boot Start End Blocks Id
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 Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for 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 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 virtual-machine xen vmware share|improve this question edited Dec 30 '11 at 23:11 Gilles 370k686711122 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 370k686711122 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 prompt: grub > find /vmlinuz. This should