Hi,
Im getting these following errors,

An errors occured during the file system check.
dropping you to a shell:the system will reboot
when you leave the shell.

/dev/v01group00/logVO 100: UNEXPECTED INCONSISTENCY;
Run F Sck Manually without irq balance:[FAILED]

rm: cannot remove '/var/lock/subsys/rpc.idnapd'; Read only file system

*Error read block 52953121


im getting these error please anyone respond quick... i need to solve this issue within a day.....

Dude - have you considered following the message's advice, and running "fsck" manually?

Just a suggestion

PS:
Find a copy of your installation CD, and boot from it. That way you'll be sure your main drive isn't "mounted".

PPS:
Here's another link that might help:
http://forums.fedoraforum.org/showthread.php?t=92144

I'll try my best to help you, but mind you I'm relatively green compared to some other people you may hear from in a short while.

Firstly, check out this site: http://forums.devshed.com/linux-help...lly-71202.html

What that's basically telling you is to use fsck (manually, as stated), on your filesystem to check it. If you're running just a straight Linux drive, fsck /dev/hda1 as a command should work.


From the little that I've read (again, referring to the link), this might be in regards to a hard reboot that screwed up something with whatever Linux ext systems use to mark drives as clean or dirty.

Hopefully this points you in the right direction. Google this phrase for more information, slightly different than what you wrote but I found some stuff on this issue:

UNEXPECTED INCONSISTENCY Run FSck Manually without irqbalance:[FAILED]

It's possible that he's totally new with Linux, which we all were at one point--and had he known what fsck was he probably would have answered his own question.

When there's a problem in a given filesystem linux prevents you from booting normally by mounting it read-only or not mounting it at all if the problem is too severe.

You still have limited shell functionality. You should be able to run "fsck /dev/v01group00/logVO" and see what happens. If the file system can be fixed a reboot after that should be enough. You might need to add -f to the fsck line for it to actually do something.

If fsck complains for some reason you might need to do some extra work from a live dvd or other alternate boot media.

Fs failure, just like in Windows or any other OS, are a common thing when you suffer an electric outage or don't properly shut down your machine. So, make sure that that's not the problem.

Noch einmal:
Good luck .. PSM