CentOS 5 :: Died, Kernel File Not Found \ Get:Error 13: Invalid Or Unsupported Executable Format?
Aug 31, 2011
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
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'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/.
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 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:
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'm trying to install Fedora 13 VM on my CentOS 5.5 64 bit install following the below link. I used this same process to install a CentOS 5.5 VM just to test the process. Now when I try to follow it making changes for Fedora Im getting an error.[URL] config file:
kernel = "/install/vm/fedora/vmlinuz" ramdisk = "/install/vm/fedora/initrd.img" name = "fedora13"
[code]...
In the CentOS link I posted it said to use kernel from the xen directory.Ive found out that the last fedora version that shipped with xen was fedora 8. Does anyone know where I can find a fedora 12/13 xen kernel? Ive searched google for hours and can not find a xen kernel. Actually I'm to the point where I would even use ubuntu or any similar distro if I could find a xen kernel.
I have ripped quite a few movies onto my server and I play them on my PS3 with mediatomb. I haven't changed any of the settings in handbrake except I was playing around with the quality meter on the video tab. Some of my movies will play and others won't. The ones that do not play say something about an unsupported file type. They also will not play in Movie Player.
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 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 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 have just done a reinstall of Centos 5.3 on a dedicated server (via a KVM). My partition arrangement was the default presented to me by the installer:
As you can see, I'm using LVM for everything other than /boot (I need to use LVM for an app I am testing).
On reboot, I get the following:
[QUOTE]
It looks like it can't find vmlinuz-2.6.18-128.el5 in /boot.
I have rebooted using the Centos Install Disk 1 and gone in to rescue mode. Rescue mode mounted my / under /mnt/sysimage, from there I could see that /boot had been mounted from /dev/sda1 as it should be.
However, there was no initrd.image or /vmlinuz-2.6.18-128.el5 under /boot or /boot/grub. Shouldn't the CentOS installer have created these?
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)
I've been trying to use tracepoints on a newly installed Centos5.5 download, and crash when I call register_trace_sched_switch, which maps to tracepoint_probe_register(sched_switch, my_func) in tracepoint. h/DO_TRACE, where my_func is the function I want called back on a thread switch. I'm trying to do this from an installable module.So I downloaded the sources for 5.5 (current, 2.6.18-194), with the intention of kprinting my way through the above problem.Unlike the downloaded kernel, which is an "ELF 64-bit LSB shared object" (I'm building for an Intel Atom), when I build using "make" in my rpmbuild/BUILD/kernel-26..18/linux-2.6.18.x86-64/ directory, I get an "ELF 64-bit LSB executable". When I try to boot it, I get the complaint "Error 13: Invalid or unsupported executable format".
The closest thing I could find on the web, was a suggestion, for some powerpc system, to use the "ELF executable" format instead of "ELF shared object", the opposite of my issue, and that such could be forced by using a CONFIG-RELOCATABLE manifest.I couldn't find any .config manifest that looked likely to produce the result I want.
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'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:
Can someone tell me how to correct the "Invalid module format"? I hope that correcting the "Invalid module format" error, I will not have the "Unknown symbol in module" error.
Note: I am using wlan1 for this module as I previously am online with the wlan0 network.The same error occurs if I use ./wlan0up.