Hi ,
Im running Redhat 6.3 Version in Hp pavilion .Whenever i reboot my server it takes more than 25 minute to come alive .Force skipping of file check using "shutdown -rf now" even takes more than 15 min to come alive .

Does any one have any ideas to make my redhat server to boot faster without skipping filecheck

Call up Redhat support, they can help you out.

I agree with szboardstretcher; it sounds like you've got major issues. Those times are easily an order of magnitude too long.

my goodness, how old is that HP? that is performance as if you were running that on an old Pentium, first generation with less then 64M RAM.

sounds like you might also have some stale network connection issues, but as you are paying for RHEL, you should do as szboardstretcher recommends and contact RH for assistance with this issue.

call red hat , those times are WAY out of whack
-- my 13 year old Pentium 4 box ( SL6.4 )from power on to using it , only takes 45 Sec. - it is an old computer


but one thing you can do and RH tech support will have you do this first
so you might as well do it now

install "bootchart"
http://www.bootchart.org/index.html
http://prdownloads.sourceforge.net/b...rt-0.9.tar.bz2
SVN
or bootchart2
https://github.com/mmeeks/bootchart

build the source and run it
it outputs a svg image of the boot process
from that you can find out what is causing the jam up


now one thing that CAN really slow things down is the SELinux resetting ,if you disable SE then turn it back on

by "file check" do you mean smartd

Yes, it sounds like there are massive network-related timeouts going on here, and probably an unknown number of major hardware problems.

I suggest that you hire a local, truly-expert consultant to come in and help you to thoroughly diagnose the root cause of this outrageous problem. If they charge you several hundred US-Dollars an hour .. and they probably will .. pay it, because this situation in its present form is costing you far, far more than that. (Note: I am not advertising or volunteering ... as if I could, from halfway around the world.)

If you're providing services for some company who is "halfway around the world" from you, then kick the problem over to them as soon as you can, because any situation that is as outrageous as this one is, is costing all of you an unknown fortune and it must be stopped. (They might "stop it" by, e.g. chucking the computer and all the hardware now attached to it into the garbage can, and replacing it ... "don't bother to understand it, just Kill it, Bury it, and make it Go Away" ... as soon as they are made aware that the problem exists.)