OpenVZ Forum


Home » General » Support » *SOLVED* Error 13: Invalid executable or unsupported format ???
icon5.gif  *SOLVED* Error 13: Invalid executable or unsupported format ??? [message #8881] Fri, 08 December 2006 16:10 Go to next message
arnaudsj is currently offline  arnaudsj
Messages: 9
Registered: December 2006
Junior Member
Hi,

I am running Centos 4.4 x64 and I thought I would try out to get OpenVZ running on this Opteron box, so I installed via YUM the latest stable kernel (2.6.9-023stab032.1-smp).

I modified the grub config and attempted to boot and I got the following error message:

Error 13: Invalid executable or unsupported format ???


Here is what I have in Grub:

title OpenVZ (2.6.9 x64 SMP)
        root (hd0,0)
        kernel /vmlinux-2.6.9-023stab032.1-smp ro root=/dev/Linux/CentOS console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-023stab032.1-smp.img
        boot


Any ideas? My main setup uses RAID 0 with LVM on top. My boot partition though is a standard ext3 100Mo partition on the sda.

Thank you for your guidance!

S├ębastien

[Updated on: Mon, 11 December 2006 07:28] by Moderator

Report message to a moderator

Re: Error 13: Invalid executable or unsupported format ??? [message #8883 is a reply to message #8881] Fri, 08 December 2006 16:34 Go to previous messageGo to next message
dim is currently offline  dim
Messages: 344
Registered: August 2005
Senior Member
Did you install x86_64 kernel rpm?


http://static.openvz.org/openvz_userbar_en.gif
Re: Error 13: Invalid executable or unsupported format ??? [message #8884 is a reply to message #8883] Fri, 08 December 2006 16:41 Go to previous messageGo to next message
arnaudsj is currently offline  arnaudsj
Messages: 9
Registered: December 2006
Junior Member
Yes!

ovzkernel-smp.x86_64                     2.6.9-023stab032.1     installed       
Matched from:
ovzkernel-smp
This package includes a SMP version of the OpenVZ kernel. Install the
ovzkernel-smp package if your machine uses two or more CPUs or CPUs with
hyperthreading technology.
Re: Error 13: Invalid executable or unsupported format ??? [message #8885 is a reply to message #8881] Fri, 08 December 2006 16:51 Go to previous messageGo to next message
dim is currently offline  dim
Messages: 344
Registered: August 2005
Senior Member
Do you have 32bit environment then?
`uname -a` with CentOS kernel, please.


http://static.openvz.org/openvz_userbar_en.gif
Re: Error 13: Invalid executable or unsupported format ??? [message #8886 is a reply to message #8885] Fri, 08 December 2006 16:55 Go to previous messageGo to next message
arnaudsj is currently offline  arnaudsj
Messages: 9
Registered: December 2006
Junior Member
This is what I have runing:
# uname -a
Linux andromeda 2.6.9-42.0.3.plus.c4smp #1 SMP Fri Oct 6 11:42:04 CDT 2006 x86_64 x86_64 x86_64 GNU/Linux
Re: Error 13: Invalid executable or unsupported format ??? [message #8887 is a reply to message #8886] Fri, 08 December 2006 17:02 Go to previous messageGo to next message
dim is currently offline  dim
Messages: 344
Registered: August 2005
Senior Member
1) `file /boot/vmlinux-2.6.9-023stab032.1-smp` output
2) full /etc/grub.conf content
3) `file /boot/vmlinux-2.6.9-42.0.3.plus.c4smp` output

Am I right, grub prints error when it is triyng to load kernel itself?


http://static.openvz.org/openvz_userbar_en.gif
Re: Error 13: Invalid executable or unsupported format ??? [message #8888 is a reply to message #8887] Fri, 08 December 2006 17:17 Go to previous messageGo to next message
arnaudsj is currently offline  arnaudsj
Messages: 9
Registered: December 2006
Junior Member
I think you are on to something:

# file /boot/vmlinux-2.6.9-023stab032.1-smp 
/boot/vmlinux-2.6.9-023stab032.1-smp: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), statically linked, not stripped


# file /boot/vmlinuz-2.6.9-42.0.3.plus.c4smp 
/boot/vmlinuz-2.6.9-42.0.3.plus.c4smp: x86 boot sector

Any other of my kernels listed in grub.conf below are showing this property (x86 boot sector)

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/Linux/CentOS
#          initrd /initrd-version.img
#boot=/dev/sda
default=3
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
serial --unit=0 --speed=9600
terminal --timeout=2 serial console

title CentOS (2.6.9-023stab032.1-smp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-023stab032.1-smp ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-023stab032.1-smp.img

title CentOS (2.6.9-42.0.3.plus.c4)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.3.plus.c4 ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-42.0.3.plus.c4.img

title CentOS (2.6.9-42.0.3.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.3.EL ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-42.0.3.EL.img

title CentOS (2.6.9-42.0.3.plus.c4smp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.3.plus.c4smp ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-42.0.3.plus.c4smp.img

title CentOS (2.6.9-42.0.2.plus.c4)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.2.plus.c4 ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-42.0.2.plus.c4.img

title CentOS (2.6.9-42.0.2.plus.c4smp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.2.plus.c4smp ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-42.0.2.plus.c4smp.img

title CentOS (2.6.9-42.0.2.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.2.ELsmp ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-42.0.2.ELsmp.img

title CentOS (2.6.9-42.0.2.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.2.EL ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-42.0.2.EL.img

title CentOS (2.6.9-34.107.plus.c4smp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-34.107.plus.c4smp ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-34.107.plus.c4smp.img

title  Gentoo Linux (2.6.14-r5 lvm2)
        root   (hd0,0)
        kernel /kernel-genkernel-x86_64-2.6.14-gentoo-r5 udev dolvm2 root=/dev/ram0 real_root=/dev/Linux/Gentoo init=/linuxrc lvmraid=/dev/md0 video=vesafb:ywrap,mtrr,1024x768-16@85 splash=silent,theme:emergence
        initrd /initramfs-genkernel-x86_64-2.6.14-gentoo-r5

title Windows XP (32bit)
        rootnoverify (hd0,2)
        chainloader +1



Also for some reason menu.lst is showing some quite different things... Not sure what happened (I wonder if it because I had installed Ubuntu a few months ago and it overwrote the grub config from Centos...
# cat /boot/grub/menu.lst 

# 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
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default         0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout         10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title         Windows 95/98/NT/2000
# root          (hd0,0)
# makeactive
# chainloader   +1
#
# title         Linux
# root          (hd0,1)
# kernel        /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=/dev/sdb3 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## ## End Default Options ##
serial --unit=0 --speed=9600
terminal --timeout=2 serial console

splashimage=(hd0,0)/grub/splash.xpm.gz

title CentOS (2.6.9-42.0.3.plus.c4smp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.3.plus.c4smp ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-42.0.3.plus.c4smp.img
        savedefault
        boot

title OpenVZ (2.6.9 x64 SMP)
        root (hd0,0)
        kernel /vmlinux-2.6.9-023stab032.1-smp ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-023stab032.1-smp.img
        boot


title CentOS new, kernel 2.6.9-42.0.2.ELsmp
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.2.ELsmp ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
initrd /initrd-2.6.9-42.0.2.ELsmp.img
boot



title CentOS (2.6.9-34.107.plus.c4smp)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.107.plus.c4smp ro root=/dev/Linux/CentOS clock=pmtmr noapic nolapic console=tty1 console=ttyS1,9600
initrd /initrd-2.6.9-34.107.plus.c4smp.img
boot

title           Ubuntu, kernel 2.6.15-26-amd64-generic
root            (hd0,0)
kernel          /vmlinuz-2.6.15-26-amd64-generic root=/dev/sdb3 ro quiet splash
initrd          /initrd.img-2.6.15-26-amd64-generic
boot

title           Ubuntu, kernel 2.6.15-26-amd64-generic (recovery mode)
root            (hd0,0)
kernel          /vmlinuz-2.6.15-26-amd64-generic root=/dev/sdb3 ro single
initrd          /initrd.img-2.6.15-26-amd64-generic
boot

title           CentOS, kernel 2.6.9-34.107.plus.c4smp
root            (hd0,0)
kernel          /vmlinuz-2.6.9-34.107.plus.c4smp root=/dev/sdb3 ro quiet splash
boot

title           CentOS, kernel 2.6.9-34.107.plus.c4smp (recovery mode)
root            (hd0,0)
kernel          /vmlinuz-2.6.9-34.107.plus.c4smp root=/dev/sdb3 ro single
boot

title           CentOS, kernel 2.6.9-34.ELsmp
root            (hd0,0)
kernel          /vmlinuz-2.6.9-34.ELsmp root=/dev/sdb3 ro quiet splash
boot

title           CentOS, kernel 2.6.9-34.ELsmp (recovery mode)
root            (hd0,0)
kernel          /vmlinuz-2.6.9-34.ELsmp root=/dev/sdb3 ro single
boot

title           CentOS, kernel 2.6.9-34.EL
root            (hd0,0)
kernel          /vmlinuz-2.6.9-34.EL root=/dev/sdb3 ro quiet splash
boot

title           CentOS, kernel 2.6.9-34.EL (recovery mode)
root            (hd0,0)
kernel          /vmlinuz-2.6.9-34.EL root=/dev/sdb3 ro single
boot

title           Ubuntu, memtest86+
root            (hd0,0)
kernel          /memtest86+.bin 
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title           Other operating systems:
root


...

Re: Error 13: Invalid executable or unsupported format ??? [message #8889 is a reply to message #8881] Fri, 08 December 2006 19:42 Go to previous messageGo to next message
Andrey Mirkin is currently offline  Andrey Mirkin
Messages: 193
Registered: May 2006
Senior Member
arnaudsj wrote on Fri, 08 December 2006 11:10

Hi,

I am running Centos 4.4 x64 and I thought I would try out to get OpenVZ running on this Opteron box, so I installed via YUM the latest stable kernel (2.6.9-023stab032.1-smp).

I modified the grub config and attempted to boot and I got the following error message:

Error 13: Invalid executable or unsupported format ???


Here is what I have in Grub:

title OpenVZ (2.6.9 x64 SMP)
        root (hd0,0)
        kernel /vmlinux-2.6.9-023stab032.1-smp ro root=/dev/Linux/CentOS console=tty1 console=ttyS1,9600
        initrd /initrd-2.6.9-023stab032.1-smp.img
        boot




Please change "kernel /vmlinuX-2.6.9-023stab032.1-smp ..." to "kernel /vmlinuZ-2.6.9-023stab032.1-smp ...".
Just one letter x to z.

Do you have vmlinuz-2.6.9-023stab032.1-smp in /boot directory?


Andrey Mirkin
http://static.openvz.org/userbars/openvz-developer.png
Re: Error 13: Invalid executable or unsupported format ??? [message #8892 is a reply to message #8889] Fri, 08 December 2006 20:22 Go to previous messageGo to next message
arnaudsj is currently offline  arnaudsj
Messages: 9
Registered: December 2006
Junior Member
Wow, that's scary - I have this in my boot directory:

-rw-r--r--  1 root root  1408100 Dec  5 23:30 initrd-2.6.9-023stab032.1-smp.img
-rw-r--r--  1 root root  1273754 Oct 19 17:14 System.map-2.6.9-023stab032.1-smp
-rwxr-xr-x  1 root root 10529921 Oct 19 17:16 vmlinux-2.6.9-023stab032.1-smp
-rw-r--r--  1 root root  2637165 Oct 19 17:14 vmlinuz-2.6.9-023stab032.1-smp


I have no idea how this vmlinux got in there...

Oh, well I updated the grub config and will try to reboot later tonight and will let you know!

Thanks!
Re: Error 13: Invalid executable or unsupported format ??? (solved) [message #8900 is a reply to message #8892] Sat, 09 December 2006 03:45 Go to previous message
arnaudsj is currently offline  arnaudsj
Messages: 9
Registered: December 2006
Junior Member
It worked!

Thank you for your help identifying the issue. I still have no clue though how this other vmlinuX file got created on the boot partition and caused this...

Sorry, if I wasted anybodies time on a typo in then end Wink
Previous Topic: *SOLVED* Bridge TCP/IP Trouble
Next Topic: *SOLVED* vzquota : (error) Quota on syscall for 101: Device or resource busy
Goto Forum:
  


Current Time: Sat Jun 15 10:44:58 GMT 2024

Total time taken to generate the page: 0.03754 seconds