Fedora 9 boot failure Unable to execute “/bin/sh”

5 pts.
Tags:
Fedora 9 boot
Greetings!  (I apologize if this got posted twice. not sure what happened) Fedora 9 Here is one for you. While configuring nfs client, I edited fstab and then used the mount command it properly returned an error since I did not have the nfs server completly set up on another machine I set up the other machine, then issued my mount command again. This time the error was something I had never seen: Unable to execute "/bin/sh" mount .... As I remember. got the same thing (Unable to execute "/bin/sh") when I tried shutdown, figuring I'd reboot  would not shutdown, so used the gui and logged out, but then could not shut down or login. So, reset the machine and then the boot errors: Red Hat nash version 6/0/52 starting drivers/hid/usbhid/hid-core.c: couldn't find an input inturrupt endpoint mdadm: /dev/md0 has been started with 3 drives (out of 4). init: Unable to execute "/bin/sh" for rcS: No such file or directory init: rcS main process (527) terminated with status 255 init: Unable to execute "/bin/sh" for rcS: No such file or directory init: rcS post-stop process (528) terminated with status 255 Kernal alive so got out the Rescue disk, and after the rescue is set up, the process tells you that you can do chroot /mnt/sysimage to make your system root. But, when I issued the chroot command it returns this: chroot: cannot run command '/bin/sh' : No such file or directory I am able to cd and explore my file system ok.
I have checked /etc/shells and /bin/sh is there
I relinked (   ln -s /bin/bash /bin/sh   ) and got a reply that indicated the link was there. What is going on?
Any ideas how to get this thing to boot?  I have about a TB of data in the RAID array I want to get to somehow.
The full text of the screen from most recent boot attempt:
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.24-14.fc9.x86_64 ro root=UUID=837a78b1-1f56-4c07-8903-a91e44fb9159 rhgb guiet
[Linux-bzImage, setup=0x2e00, size=0x1f63b8]
initrd /initrd-2.6.25-14.fc9.x86_64.img
[Linux-initrd @ 0x37ce7000, 0x3085e8 bytes]
Decompressing Linux... done.
Booting the kernel.
Aperture pointing to e820 RAM Ignoring.
Your BIOS doesn't leave a aperture memory hole
Please enable the IOMMU option in the BIOS setup
This cost you 64 MB of RAM
Red Hat nash version6.0.52 starting
mdadm: /dev/md0 has been started with 3 drives (out of 4).
init: Unable to execute "/bin/sh" for rcS: No such file or directory
init: rcS main process (528) terminated with status 255
init: Unable to execute "/bin/sh" for rcS: No such file or directory
init: rcS post-stop process (529) terminated with status 255
Kernel alive
*****that's all!
Have fun, Paxton


Software/Hardware used:
Fedora 9
ASKED: December 8, 2011  9:29 PM
UPDATED: February 28, 2012  3:23 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following