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
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...?
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
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'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 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'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.
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:
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
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.
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 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.
I have a problem installing CentOS 5.5 over lan. I set up a dhcp3 server and it works, client got an ip. I set up a tftpd-hpa server and it works, client can boot the install image of CentOS 5.5 I set up an apache server and it seems to be impossible... In the installation marathon I clicked through the menu to the choice of the web server where my installation files are available. I enter the ip 192.168.138.1 and the path CentOS-5.5 and CentOS tells me "Unable to retrieve http://192.168.138.1//CentOS-5.5/images/stage2.img" . Thats right because the two slashes are not right. Where the hell come the two slashes from???
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've just moved a server across to CentOS 5.5 64-bit and I have been trying to get some custom software running on it. However I'm getting an unusual error during run time: sched_setaffinity: Invalid argument I've had this software working on a old versions of Gentoo (2.6.12-gentoo-r6) and Fedora. And the latest version of Ubuntu server 10.04.1. (All 64 bit). It looks remarkable similar to: Core test failed on s390x RHEL6 If v7 bug fix and enhancement update has been incorporated into CentOS 5.5 64 bit yet? Or how I might find out.
I'm trying to install PPTP following this guide http://www.dotcomunderground.com/blogs/2010/04/10/poptop-pptp-centos5-installation-setup/but when I enter the command yum --enablerepo=poptop-stable install pptpd
I have a multiboot system chainloaded by SUSE grub. I have installed CENTOS on an extended partition thrice with various grub install options available in install media. I am unable to chainload CentOS with SUSE grub or PCLinuxOS grub.
Here is my menu.lst -
# Modified by YaST2. Last modification on Mon Sep 20 05:43:13 SGT 2010 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader default 0
[Code]....
How do I get CentOS to boot from openSUSE 11.2-11.3 grub.
i traying to install php memcache module and alot of other things but evrytime i tray to use yum i got this error $Loading "fastestmirror" plugin Options Error: Error parsing '1enabled=1': invalid boolean value i have centos 5 server 64bit is there anyone now what this error and how to fix it
It seemed that it would be simple enough: take the 'f' option in the expert menu of fdisk to put partitions in order after a gap had been created by a deleted partition and then make corresponding changes in /boot/grub/grub.conf because the root partition was shifted.
Well, it didn't work out that way. No matter what I try, I either see the error 15 at Stage1.5 or the error 28, which is even stranger (file does not fit into memory). All this before I even see a grub menu. It just does not get that far.
Does anyone want to take as stab at guessing what might have happened here and whether I have a chance at recovering without having to reinstall? I can provide concrete data, if anyone would be kind to give it a try. Hoping that this is a known problem and something can be guessed from what I stated here but I can be as specific as needed, just don't want to generate noise if there are no takers.
After a reboot, my PC just hang. It says "insmod : error inserting '/lib/raid456.ko : -1 File exists ..." then followed by a kernel panic. I have tried to boot using rescue mode but it couldn't find any Linux partition, thus no /mnt/sysimage was mounted. It left me at a shell and I'm stuck there.
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'm running a fresh install on an intel i7 system on an asus p6t deluxe v2 motherboard with the onboard NIC (Marvell Technology pci-e). I know the NIC is working as when I boot into the onboard OS that Asus provides (Asus Express Gate SSD)I have a working net connection.Booting up CentOS hangs at determining IP information for eth0 and eventually fails with the following error:PING xxx.170.30.1 from xxx.170.31.231 eth0: 56(84) bytes of data---xxx.170.30.1 ping statistics ---4 packets transmitted, o received, +3 errors, 100% packet loss, time 2999ms, pipe 3 failed.
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 am trying to install Centos 5.6 on a motherboard with a built in Marvel 88SE61xx drive controller.NO drive arrays are configured using the Marvel BIOS configuration utility.During the install CENTOS displays loading MARVEL_PATA driver and it waits and waits and waits.Looking on one of the system message screens I get the following types of messages:qc timeoutfailed to identifyI/O errorLink is slow to respondSRST failed errno=16ata4: reset failed - giving upAny ideas as to how to get CENTOS to recognize the drives connected to the motherboard Marvell controller on a NON-RAID configuration?
