Hi to all,

I have installed Ubuntu on one of my ESXI servers as a web server.

Yesterday i have been getting all errors on my system on boot.


and most of my commands do not work, such as "ls,chmod,netstat" and so on . the error is:

bash: /bin/ls cannot execute binary file.

FYI:
Kernel = 2.6.24-24-server #1 SMP Fri Sep 18 16:41:05 UTC 2009 x86_64 GNU/Linux

Thank you for your help.

Bash always produces errors when you try to use it like that. It is intended to be used on the command-line like that, to execute SHELL SCRIPTS, not binaries. Binaries do not run in the shell.

If this is not a fresh clean installation, I would be investigating if perhaps the previous installation may have had a lot of wrapper-scripts and/or shell aliases configured for some of these common commands you indicate are failing, and the aliases or wrappers are now broken with this new installation. Specifically, it looks like shell aliases were set up to run scripts, which subsequently ran the actual binary command.

Check /etc/profile and/or /etc/profile.d/* and/or ~/.profile and check for shell aliases that do not work. Try the command:
to look at any configured aliases.

Sasha

Check /etc/profile and/or /etc/profile.d/* and/or ~/.profile and check for shell aliases that do not work. Try the command:
to look at any configured aliases.

Sasha[/QUOTE]

SHELL#: alias -p ,,,, and alias outputs this ?

alias ls='ls --color=auto'

?? dose that make any sense to you .

Thank you for your help.

It makes sense -- when you use the ls "command" it runs ls --color=auto instead of simply ls but that does not explain why it results in "cannot execute binary file".

You could check whether aliases are the problem as Sasha suggested by running unalias -a. That would remove all your aliases so using the ls "command" should use the standard /bin/ls executable. You can always find out what ls actually is by type ls or which ls.

Yes, that's a common alias for `ls` -- it makes the ls listings colored, like for different filetypes, folders, etc. so that's OK.

Please show us the output of:
and from some directory, please show exactly the output of trying to use the ls command (copy and paste the exact output to your next post). And yes, what catkin wrote too -- `type /bin/ls`

Thanks Charles.

Sasha

Thank you for your reply guys .

here are the results.

# which ls
/bin/ls
# file /bin/ls
bin/ls: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), corrupted program header size, corrupted section header size.



To be honest it seems like the system it self is locked, when i boot up is shows some errors in rc.d/ nothing is really running.

I don't like that part about "corrupted program header size, corrupted section header size" -- doesn't sound healthy.

I believe there is a larger problem going on here, since you now mention:
I suggest you start at the very beginning:

Tell us about this EXSI server. Did it ever work right, such as before Ubuntu? What was it running before Ubuntu, if anything, and how did you go about putting Ubuntu on it.

Please post for us the contents of /var/log/dmesg and /var/log/messages from on the server, after booting it.

Sasha

Well,
I have an ESXI server running multiple system. and i installed a new Virtual Machine Ubuntu on it to run as a webserver, its been a week since iam running this system and it was fine until yesterday.

So Ubuntu is a Webserver running as a VM on ESXI .

dmesg .
Same binary issue .

cat /var/log/messages
Cant really post anything since my SSH is not even on and cant really export anything but , i have this.
all i see in the past 7 days is
"Mar 11 06:27:15 titan -- MARK --"
and thelist goes on .....

I'm now wondering if this thread would be better served in the "Virtualization" area of LQ -- what do you think? If you agree, I'll move it there for you.

Sasha

Go crazy do what ever you feel like. '

Has it been moved yet ?

and thankx

Yes, it has now been moved to "Virtualization" -- I hope this helps some as I myself am not experienced with VM stuff.

I also edited the title a little bit, to give a bit more insight into the thread.

Best of success!

Sasha

Is the OS you're having problems with in a VM? OR is it the host one? If it's one VM. Have you checked to see if your server was improperly shut down. Disk corruption can do serious damage to virtual HD image files and their contents.

Its the VM that is causing this error, other VM's is just fine.

I dont why most of my commands are not running.

Its either someone installed some buggy program or the VMDK file is just locked.

????
FYI >
its an Ubuntu Server. running as a VM on ESXI server.

What I'd do is decouple the guests VMDK, mount it and then check the system logs (maybe that will show clues), then verify hashes to see which utilities have been hit by corruption. If you made backups you could try and restore one but until you've got a fix on what causes the corruption reliability remains zero.