General :: Booting Into Kernel - Error 13: Invalid Or Unsupported Executable Format
Sep 13, 2010
I've been playing around with trying to assemble a bare-bones Linux system on a disk.img file through a loop device. I compiled the most recent stable kernel and then copied it onto the root partition in the image. When I try to boot up into the image using qemu, grub gives me this:
Code:
Booting 'tiny'
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinux
Error 13: Invalid or unsupported executable format
Press any key to continue... I am confused because I compiled the kernel with 'make bzImage', and the architecture hasn't changed (qemu on the same machine used to build the kernel). So it should be bzImage format. Is that what this Error 13 means, or could it means something else is wrong...?
I have a weird problem with one of my servers (normal PC hardware). I was connected remotely using Putty, doing some stuff, and all of the sudden some commands, like "ls" stopped working, giving a "file or command not found" type of message. I restarted the ssh session, only to find out I couldn't log on any more (access denied). When I got home and rebooted the system, I was greeted with this:Booting 'CentOS (2.6.18-194.el5xen)'root (hd0,0)Filesystem type is ext2fs, partition type 0x83kernel /boot/xen.gz-2.6. 18-194.el5Error 15: File not foundPress any key to continue...Then I searched about this, found out that the files in /boot/grub/menu.lst did not exist at the specified location (/boot/xen.gz-2.6. 18-194.el5). Somehow I managed to find them in another place, copied them in place, and now I get:Error 13: Invalid or unsupported executable format
Reluctantly I made a temporary install of XP as follows Remove linux drive and install a wiped drive.format ntfs & install windows xp (w/sp3)shift ntfs drive to slave, replace linux drive as master and xp drive as slave. Add it to grub as follows:
Code: # boot=/dev/sda1 default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz titlem$ Windows XP code....
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've been googling all afternoon to fix this error I get. The situation is as follows: I have multiple harddrives (3x320gb and 1x160gb) all on the SATA interface. One of these drives contains Windows, and the rest I use for programs and downloads. I've installed Ubuntu 9.04 from a USB-stick using the installer's partitioner to make some room for Ubuntu (Ext4 filesystem). I've tried Ubuntu and SUSE in the past.
2.6.38-10-generic-pae ===> Error 16: Incosistent filesystem structure 2.6.38-10-generic-pae (recovery mode) ===> Error 13: Invalid or unsupported executable format 2.6.38-10-generic ===> Error 13: Invalid or unsupported executable format
[code]....
b08e48b7-1194-49c1-a743-91e7ee90334e is a link to /dev/dm-2 which is my root partition on nvidia raid
PS: At first it did not boot at all dropping out to grub shell, but I managed to boot it with gparted live usb stick and chroot to Ubuntu and re-install grub, but now 2.6.38-8 kernel works and 2.6.38-10 is not
A few days ago I booted up my computer as normal and loaded vista. It loaded fine, but then froze at the login window. I restarted my computer but this time when I tried to load vista I got the "Error 13" message. Ubuntu still loads up fine however.
I'm fairly certain that I'm using Grub - Legacy, and since most posts that I see post the contents of the menu.lst file, I will too Code: # menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8), # grub-md5-crypt, /usr/share/doc/grub # and /usr/share/doc/grub-doc/. ## default num # Set the default entry to the entry number NUM. Numbering starts from 0, and code....
A few days ago I booted up my computer as normal and loaded vista. It loaded fine, but then froze at the login window. I restarted my computer but this time when I tried to load vista I got the "Error 13" message. Ubuntu still loads up fine however.
I'm fairly certain that I'm using Grub - Legacy, and since most posts that I see post the contents of the menu.lst file, I will too
Code: # menu.lst - See: grub(8), info grub, update-grub(8) # grub-install(8), grub-floppy(8), # grub-md5-crypt, /usr/share/doc/grub # and /usr/share/doc/grub-doc/.
i have just discoverd i can't enter my windows 7 via grub boot menu i get error 13 Invalid or unsupported executable format what can i do? # This entry automatically added by the Debian installer for a non-linux OS # on /dev/sdb1
I run a small home/hobby server. I attempted to upgrade it this morning. It was previously using 8.04 lts. I followed the instructions found here, [URL].. Upgrade for Ubuntu Servers (Recommended) I followed the on-screen instructions. After the installation was complete, I rebooted the server. On start up, I was greeted by this message "error 13: Invalid or unsupported executable format." I have since tried booting into every 10.04 kernel listed. However, the results are the same. I have attempted to find a solution via web search, but have had difficulty finding a solution that is appropriate for my situation.
I have 4 partitions in my system, out of which two(sda1, sda2) have windows on them. I have installed RHEL 4 32 - bit on sda3 and after that , installed installed RHEL 64-bit on to a partition sda 5. Now i am unable to boot into RHEL 32-bit. The error i am getting is Error 13: Invalid or unsupported executable format.
I was installing opensuse on the c partition and it gave errors so i aborted it now i click on windows and it says invalid or unsupported executable format chainloader +1 so then i proceeded to try and fix this by changing the menu.lst to this:
And now it tells me that disk isnt found so i need to know what to put in the menu.lst to load the actual windows partition and then fix the original error.
On my Laptop is an 80 GB HD. I installed Windows XP first (at this point it worked perfectly) then installed on the same HD, but on other partitions Archlinux.
The whole thing looks like this now:
/dev/sda1 <--- Windows xp /dev/sda2 <--- arch linux (/, etc, etc^^) /dev/sda3 <--- homes /dev/sda4 <--- boot partition (grub)
(I got no SWAP partition, I got 4gb RAM (well can only use 3, since my system doesn't support 64bit), and my friend told me there's no absolute need for a a swap :>)
Arch Linux is booting perfectly (and very fast), but Windows XP doesn't want to boot anymore :> (Just if it's from any importance: In the partition program I took the "bootable" flag away from my XP Partition and set it to sda4 - I thought I need to do that, but now I'm not so sure anymore :P )
My entry in the file /boot/grub/menu.lst looks like this (I also tried various others)
title Windows root (hd0,1) makeactive chainloader +1
When I boot and choose the Windows XP in the GRUB boot menu, the following message appears:
error 13: invalid or unsupported executable format
When I set root(hd0,1) to root(hd0,0) (what seemed the most logical to me) and boot again selecting the windows xp, then the GRUB cosole appears.
So what did I do wrong - or better said: what should I do now?
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 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 the boot sector of the root partition for example. Because I didn't want to ruin the existent grub onfiguration, 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 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 compression
After coming home one evening I found my server was turned off. My suspicions lead me to believe we had a storm and the power went off, then the UPS went off and finally at that point the server went off too. I think my server was set to allow security updates. After it turned of and restarted it seems it made a change to Grub and upgraded it to Grub2. In doing so I now get the following message:
Error 13: Invalid or un supported executable format
I have tried to do the following:
url
This solved the problem for me, from > url
Quote:boot from the live medium and chroot into the Linux installation:
Bottom Line: Dvd Drive died in my toshiba laptop and it was replaced (not before tech for some reason reformatted the Win7 partition... which was 100% un-needed, but thats beside the point now. I redid win7 (the tech installed vista) and am TRYING to "redo grub". Facts: The Slackware AND Ubuntu Partitions ARE STILL THERE and when i use SuperGrub Boot CD (which doesn't restore my grub by itself) to boot into slackware, i can see ALL THE CONTENT of both Linuxes still there including grub on ubuntu partition
(Tri-Boot: Ubuntu, Slackware, and WIn7) I had it working for two years or so, SO i know this "setup" works fine. I am A) Trying to do this as simply as possible. B) Trying to avoid the need to download a 800MB ISO (as seen for this issue on this forum) and trying not to have to reformat Ubuntu Partition (though I have the .Debs I have downloaded for it backed up ... all 1.7GB of them) I have /dev/sda1 as win7, /dev/sda2 as Slack and /dev/sda3 as Ubuntu (which contains Grub Legacy).. Every command I do seems to result in an error like "invalid command" or "invalid Execution format " (i think that second one is right) type errors. I compiled (awhile back) a few kernels for Slackware, but feel goofy that I cant figure what i this out (what i thought was going to be a "2 minute" fix)
I have installed win xp(sda1) win 2003(sda2), centos 5 (sda7) and mint 5(sda5) on 4 partitions and swap (sda6).All OS work fine except centos 5. When from the boot menu I choose Centos 5, I get the following error:File system type is ext2fs, partition type 8x83.Kernel /boot/vmlinuz 2.6.18.92.el5xem root/dev/sda7Error 13 invalid or unsupprted excecutable formatBut I 'm sur that I have format /dev/sda7 as ext3
I successfully built the sources for 64 bit linux drivers from [URL].... on the 64 bit F14 machine: Linux localhost.localdomain 2.6.35.6-45.fc14.x86_64 #1 SMP Mon Oct 18 23:57:44 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux and got wl.ko:
i installed SLES 11 sp1 as guest on openSUSE 11.3 host, then change the adapter network from 'NAT' to 'Bridged Adapter', but when i hit start i got this error message: Failed to open a session for the virtual machine sles. Failed to open/create the internal network 'HostInterfaceNetworking-wlan0' (VERR_SUPDRV_COMPONENT_NOT_FOUND). Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND). One of the kernel modules was not successfully loaded. Make sure that no kernel modules from an older version of VirtualBox exist. Then try to recompile and reload the kernel modules by executing '/etc/init.d/vboxdrv setup' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND). but when run: sudo /etc/init.d/vboxdrv setup
I had Windows 7 and Windows XP. It was 3 partitions in one HD (two OS' and one for files) and another separate HD (which doesn't have any system, it's just media files and stuff). When booted, I used to get the Windows 7 screen, that allowed me to either boot 7 or XP. I thought I had tested 7 enough and wanted to try Ubuntu, so I (from the Ubuntu CD which I downloaded and burned) deleted the 7 partition and made a 2GB swap partition, and, what was left, an Ubuntu partition on which I installed it.
Now when I boot I get an Ubuntu boot screen that shows several Ubuntu options and a WinXP option. Ubuntu works fine, but if I choose WinXP, I get "Error 12: Invalid device requested". I didn't change anything more than what I said. The details for the WinXP boot option seem to be:
What can I do to be able to boot WinXP again? (and also Ubuntu, whenever I want to). The only thing I can think of is using Windows XP CD's restore thing to restore the boot menu, but that would stop me from using Ubuntu...
I have a raid5 on 10 disk, 750gb and it have worked fine with grub for a long time with ubuntu 10.04 lts. A couple of days ago I added a disk to the raid, growd it and then resized it.. BUT, I started the resize-process on a terminal on another computer, and after some time my girlfriend powered down that computer! So the resize process cancelled in the middle and i couldn't acess any of the HDDs so I rebooted the server.
Now the problem, the system is not booting up, simple black with a blinking line. Used a rescue CD to boot it up, finised the resize-process and the raid seems to be working fine so I tried to boot normal again. Same problem. Rescue cd, updated grub, got several errors: error: unsupported RAID version: 0.91. I have tried to purge grub, grub-pc, grub commmon, removed /boot/grub and installed grub again. Same problem.
I have tried to erased mbr (# dd if=/dev/null of=/dev/sdX bs=446 count=1) on sda (ide disk, system), sdb (sata, new raid disk). Same problem. Removed and reinstalled ubuntu 11.04 and is now getting error: no such device: (hdd id). Again tried to reinstall grub on both sda and sdb, no luck. update-grub is still generating error about raid id 0.91 and is back on a blinking line on normal boot. When you'r resizeing a raid MDADM changed the ID from 0.90 to 0.91 to prevent something that happend happened. But since I have completed the resize-process MDADM have indeed changed the ID back to 0.90 on all disks.
I have also tried to follow a howto on a similar problem with a patch on [URL] But I cant compile, various error about dpkg. So my problem is, I cant get grub to work. It just gives me a blinking line and unsupported RAID version: 0.91.
I have a problem with loading the powersaving kernel module p4-clockmod.ko. When I try inserting the module (via modprobe or insmod) I get FATAL: Error inserting p4_clockmod (/lib/modules/2.6.31.8-mediaserver/extra/p4-clockmod.ko): Invalid module format The module has been compiled together with the kernel. Other modules load with no problem at all. I've tried recompiling the kernel (after re-installing the sources, make xconfig from scratch) - no avail. There's only one kernel source package installed. Searching the forum and google didn't yield a helping answer.
I'm having some troubles with nfsd in slackware-current. When I start the service, I get the following error messages: Quote:
WARNING: Error inserting sunrpc (/lib/modules/2.6.33-smp/kernel/net/sunrpc/sunrpc.ko): Invalid module format WARNING: Error inserting auth_rpcgss (/lib/modules/2.6.33-smp/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko): Invalid module format WARNING: Error inserting lockd (/lib/modules/2.6.33-smp/kernel/fs/lockd/lockd.ko): Invalid module format FATAL: Error inserting nfsd (/lib/modules/2.6.33-smp/kernel/fs/nfsd/nfsd.ko): Invalid module format
The mount fails from the clients with the error message: Quote: mount.nfs: access denied by server while mounting jupiter:/media/Backup A look at syslog from the server side gives: Quote: exportfs: exports duplicate symbol exportfs_decode_fh (owned by kernel) mountd[28198]: getfh failed: No such device kernel: exportfs: exports duplicate symbol exportfs_decode_fh (owned by kernel)
1. Create a "Hello world" executable. 2. Attach files to it. 3. Add the code in in "Hello" executable to extract the files to a custom location.
1st is simple.
For second, above mentioned article suggest that CArchive can be created using Python. It means you can create a CArchive using "hello" executable and other files. How do you do that using Python?
For 3rd, I need more info about the implementation using C.
These days, I tried to compile my own kernel. Now, it seems work. However, when the kernel is booting, I always get the error message like below: acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed It looks that something is wrong with my acpi subsystem's configuration. But no matter How I reconfig it, this message still occurs. My distribution is UBUNTU 10.04 LTS original kernel with the distribution is 2.6.32 My own kernel is 2.6.35
I'm new to openSUSE and as a matter of fact, to linux too. I've got a Linksys WUSB600N wireless adapter which used to work fine with some live versions of linux that I was testing out before moving onto suse... Each time, upon booting using live CDs, I used to copy the driver I had downloaded from:
Then 'make' and get into the driver's os/linux directory to load the driver using 'insmod rt2870sta.ko' Now, upon doing a 'make' and 'make install', followed by the 'insmod rt2870sta.ko', I get the error saying:
insmod: error inserting 'rt2870sta.ko': -1 Invalid module format
I tried doing 'modprobe -rv rt2870sta' and didn't get any error messages. But while doing 'modprobe -v', this error shows up: insmod /lib/modules/2.6.27.7-9-default/kernel/drivers/net/wireless/rt2870sta.ko FATAL: Error inserting rt2870sta (/lib/modules/2.6.27.7-9-default/kernel/drivers/net/wireless/rt2870sta.ko): Invalid module format
I have an old Dell Optiplex GX240 running Windows XP hooked up to my Olevia HDTV. I'd like to format this computer and install Ubuntu 10.04.After burning the Ubuntu install disk, I hook the computer to the tv via HDMI and reboot to the CDROM but upon booting I receive an 'Invalid Format' error and no video is shown.I did some searching - there is very little info about this problem. This post http://ubuntuforums.org/showthread.php?t=1063217 seems to indicate that the solution is to hook up the computer to an old CRT monitor, then after the computer has booted, switch the HDMI cable to the tv.This solution is unsatisfactory. Does anyone have experience with this problem? Is there another way to get around this problem?
I'm successfully hosting an https site on my single available public facing IP address - but I want to expose a couple of internal web sites. Essentially, I have:[URL]..I get most of the way there by using mod_proxy and the directive:
