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.
View 1 Replies
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
[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
[code]....
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.
View 1 Replies View Relatedsuddenly after upgrade
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/.
[Code]....
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 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 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 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
View 3 Replies View RelatedI 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.
View 4 Replies View RelatedI have running 32bit Tomcat on 64bit Redhat machine. What is the maximum Xms Heapsize for 32bit applikation working in 64bit environment. Code: -Xms2048M -Xmx3300M Today I saw that my Tomcat swapping. Seems to bee problem with memory.
View 1 Replies View RelatedI have a database server running RHEL 5.1 32 bit that suffered some catastrophic failures about 6 months ago. We were able to patch it back together and keep it running, but now the manufacturing site it supports is going to shut down for two weeks and I would like to replace it permenantly. Does anyone have any guidance for that sort of thing? I'd like to have the new server up and running before hand, basically changing the hostname/ip and restoring the databases only on conversion day. I've done this in the past with HP UX - Red Hat conversions, but this is my first red hat to red hat move. Any advice or shortcuts?I forgot to add the other wrinkle. The new server will be running 64bit linux.
View 1 Replies View RelatedUbuntu 9.04 server (64bit)
8GB
(2) 320 WD HDD - RAID 1
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:
$ sudo mkdir /mnt/linux
$ sudo mount -t ext4 /dev/sda1 /mnt/linux
code....
Then, the following command should resolve the issue. :
$ sudo grub-install --recheck /dev/sda
installing swi-prolog on RHEL 5.4 64bit. during the make it returns the error
[code]...
From what I understand -fPIC is something that is only a concern on 64bit operating systems. I tried this on RHEL 5.4 32bit and it worked fine. How do I get past this error? I've tried disabling SElinux as recommended on the swi-prolog website, but that had no effect. I also tried compiling with "CFLAGS=-fPIC" but still the same issue. This happens on all my RHEL 5.4 64bit machines.
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
[code]....
I am not getting GUI in after installtion RHEL 5.0
My Mother board: Mercury
Model no1845 gcm
Moniter :LG 15''
I am trying to install the Linux version of Mathlab (32bit) into my openSUSE 11.1 (64bit). With STATA this was at the time possible, having installed the 32bit GTK. This is a program running Java. So since I have both 32bit and 64bit Java installed it should work, no? Copying files to /usr/local/temp as indicated OK
Decompressing O.K.
Code:
su -
cd /usr/local/temp
./install
Executing ./install gives following error: An error status was returned by the program 'xsetup', the X Window System version of 'install'. The following messages were written to standard error: /usr/local/temp/update/install/main.sh: line 86: /usr/local/temp/update/bin/glnxa64/xsetup: No such file or directory
Attempt to fix the problem and try again. If X is not available or 'xsetup' cannot be made to work then try the terminal version of 'install' using the command: install* -t or INSTALL* -t
If I well understand in line 86 the script is calling the 64 bit version of the file gnlxa64 to call the 64 bit version of the program that is not available (as academic version). I tried then the command line version.
[Code]....
While installing gcc 4.4, I get an error during "make" which says
Code:
Code:
Here are the steps I followed:
Code:
Code:
My kernel version is 2.6.18-164 and am running RHEL 5.3 on X86_64
I have a rocketraid 2640x4 with 2 500gb HDDs configured in my system. I also have a 3.5" usb floppy disk plugged in with the SCSI drivers When I boot the RHEL 5.5 x86 32 bit installer, i type in "linux dd" at the first screen. Then it asks me to load my drivers via the floppy disk which i do. When i get to the installation page of Linux after entering my serial key, it is not able to detect my HDD so i am unable to proceed. I have tried using drivers for RHEL 5, 5.1 and 5.2. There are no drivers for 5.5.
View 9 Replies View RelatedI just installed RHEL 6.1 and saw this when trying to compile ntfsprogs:
Code: [root@Alpo-Computer ntfsprogs-2.0.0]# ./configure checking build system type... Invalid configuration `x86_64-unknown-linux-': machine `x86_64-unknown-linux' not recognized configure: error: /bin/sh ./config.sub x86_64-unknown-linux- failed
Environment:RHEL 5.2 and 5.4 AP x86_64, 2 drives (sda, sdb), installing without optional features like clustering and virtualization. I have tried this for a couple of days now and just can't get it to work. My goal is to take the RHEL 5.2 DVD and RHEL 5.4 DVD and install them on separate drives of the same machine. I want the grub menu to give me a choice. I prefer to understand the steps and choices offered me by the install dialog to do this rather than fiddle with grub.conf. If that is not possible, I will write up the bug.
So far, I just get the the error 13 when trying to start the grub added second OS. I have read elsewhere that "Anaconda frequently recognizes the other operating system and sets up grub so you can boot from either operating system". That would be nice. The install dialog lets me choose a drive to install to. I have figured out that I need to check "review and modify partitioning layout" to enter the advanced grub choices. Do I have it install a boot loader for the 1st OS? Trying to add the 1st OS during the second OS install creates a grub conf with no kernel line in the added boot stanza.
We have not actually purchased support on a 2nd seat yet, so I can't go to them for this yet, and purchasing the seat may be silly if the machine can't run the OS.
I have tried several times to install RHEL 6 workstation onto a server machine. It has a dual drive RAID filesystem, whose configuration I had nothing to do with. The install procedes nicely but Displays a mdam error 127 before shutting down for the first real boot.
When booting a weird progress bar with at least 3 colors proceding at different rates displays for about 5 seconds followed by a very verbose kernel panic error which mentions tainted swap and scheduling while atomic. I suspect the error that caused the mess runs off screen too quickly to record.
Does anybody have a clue what might be happening? Even if I install minimal this happens so it appears to be a very low level hardware problem rather than a corrupt package.
I should mention that the machine runs on ubuntu 10.10 just fine, but my Lab PI wants to run it as a redhat system.
Environment: A 32-bit kernel RHEL5.3 system running on a virtual machine. The root(/) filesystem is on an LV.
Issue: Unable to resize the FS after extending the root LV since it is mounted. After extending the LV, online resizing of the FS was not supported and the root filesystem could not be unmounted while it was in use. On rebooting, I got a kernel panic error. In runlevel 1, I couldn't run chroot, couldn't find the /etc/fstab, root FS could not be mounted, fsck did not run (tried block 31 for second copy of superblock using dd count=1 bs=4k skip=31 seek=1 if=/dev/sda2 of=/dev/sda2), couldn't find any rpm on installation media to install unix-utils rpm. On running commands in runlevel 1,
I got the following output.
As we have executeable file extensions .exe , .msi and .msp for Windows. What is the file extension that is executable in Linux RHEL 5
View 3 Replies View Relatedshut down my RHEL 4 system with an error still present in the /etc/fstab file. Current symptom: When I now try to boot, everything hangs when "Enabling swap space". Highly likely, the reason is the failure to "Mount local filesystems" in the previous step (i.e. "mount point 0 does not exist" = error due to my incorrect line in the /etc/fstab file).Question: Is there any way that I can still boot my system, such that I can remove the incorrect line in the /etc/fstab file?
View 6 Replies View RelatedAny idea when the -D option was withdrawn ? I could not find much information on this . Also, what exactly is the difference between vgdisplay -v -D and just vgdisplay -v .
View 6 Replies View Relatedis possible to edited the default RHEL CD to have it automatically install RHEL based off of a kickstart file that I will store locally on the CD. My plan would be to put a cd in a server and have the OS automatically being installed.
View 3 Replies View Related
