Grub Error 13 When Loading Backtrack
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 Overflow the
How To Fix Error 13 Invalid Or Unsupported Executable Format
company Business Learn more about hiring developers or posting ads with us Unix & error 13 invalid or unsupported executable format centos Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of grub error 13: invalid or unsupported executable format 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
Error 13 Invalid Or Unsupported Executable Format Windows 7
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
Redhat Error 13: Invalid Or Unsupported Executable Format
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 prompt: grub > find /vmlinuz. This should display the
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Installation, Upgrades and Live Media GRUB: "Error 13: Invalid or unsupported executable format" on error 13 invalid or unsupported executable format rhel standard kernel FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All
Invalid Or Unsupported Executable Format Grub4dos
Albums FAQ Today's Posts Search Installation, Upgrades and Live Media Help with Installation, FedUp & Live Media (Live CD, USB, DVD) problems. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 30th January 2008, 03:41 PM grounder Offline http://unix.stackexchange.com/questions/27001/unable-to-boot-vm-error-13-invalid-or-unsupported-executable-format Registered User Join Date: Jan 2008 Location: Montreal Posts: 12 GRUB: "Error 13: Invalid or unsupported executable format" on standard kernel We have a new PC, with 2G RAM, Intel Core duo E4500 (64-bit) and ST325041 0AS SCSI Disk, running Vista. My last Linux install was RedHat 5.3, a decade ago :-). We first freed 20G of disk to make room for Linux. No issue. Then we tried installing to disk from Fedora-8-x86_64-DVD, but this failed for unknown http://forums.fedoraforum.org/showthread.php?t=179808 reasons (the last messages seem to indicate problems with /dev/sda -- it also made Vista slow to start until we zapped the two partitions Fedora had created in the freed space). So we decide to try and install to a 4G flash drive instead, and from a live CD. We booted from Fedora-8-Live-x86_64, no problem, then ran the "Install do disk". This ran to completion with no apparent problem. I hadn't yet understood much about GRUB, so I don't know exactly what I answered, but I avoided the HDD's MBR. This created two partitions on the flash drive: ~200M (/boot) and 3.7G (LVM -- with no swap). The resulting /boot can be mounted from the live CD (as /dev/sdb1). Then, in Vista, we added the /boot partition using EasyBCD. Given what happens next, this must be where GRUB was installed (and not the MBR of the flash drive). On rebooting, Vista's boot environment presents us with both choices. If I select Linux, I end up with the "grub>" prompt after an error message about not being able to boot. But there I can't get the kernel loaded. grub> root (hd0,0) grub> kernel (hd0,0)/vmlinuz-2.6.23.1-42.fc8 This last command gives: Error 13: Invalid or unsupported executable format So obviously I am finding the kernel in the /boot partition. Other names give "File not found". I rebooted from the live CD, and ran cksum on the kernel in my fl
fails with GRUB error 13: Invalid executable format General support questions including new installations Post Reply Print view Search Advanced search 4 posts • http://www.centos.org/forums/viewtopic.php?t=13361 Page 1 of 1 nilie Posts: 3 Joined: 2009/05/05 04:02:11 Booting CentOS v5.2 fails with GRUB error 13: Invalid executable format Quote Postby 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. I installed OpenSUSE first and allowed it to install and configure grub in the MBR error 13 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 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 invalid or unsupported 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 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 stop