Poweredge 2900 painfully slow. Fresh install.

[Apower1984]

Fresh install of centos 7. Minimum install only.
It takes almost 5 minutes to boot after post. After entering the username, it takes 10 seconds to prompt for the password. After entering the password, it takes approx 30 seconds to get to the prompt.
The system is a dual quad Xeon 2.0 with 20 gb ram and aperc 6I. I have updated the bios, perc, and bmc firmware to the latest versions. The perc has a raid 5 array with 5 10k sas drives. Read ahead, and force write back.

I also tried 6.6 with the same results.
Top looks fine, free looks fine.

Any suggestions? The system is unusable like this. It runs server 2012 r2 perfectly.

I don't really know where to start looking.

Thanks!

[TrevorH]

Well, a 29xx is about 10 years old so it won't be the fastest machine on the block but that does sound slow. Are you running a GUI on it? Perhaps it's the video adapter that slows it down?

[Apower1984]

I realize its an old system. but with 16ghz of total processing power and 20G of ram it should be way better. just a simple command like ifconfig.. the output is extremely slow.

There is no GUI. It is a minimum install. No packages have been installed. No settings have been modified from the default installation.

[Apower1984]

Just an update. I have install a few packages for commands such as ifconfig lspci etc. I have also run yum update and made sure everything is the latest release.
Also, even ping is slow to respond. I can ping my router and get <1ms replies. There are several switches between my pc and the router. When I ping the centos box I get delays even though it is connected to the same switch that sits on my desk at work.

Pinging 192.168.151.179 with 32 bytes of data:
Reply from 192.168.151.179: bytes=32 time=26ms TTL=64
Reply from 192.168.151.179: bytes=32 time=11ms TTL=64
Reply from 192.168.151.179: bytes=32 time=13ms TTL=64
Reply from 192.168.151.179: bytes=32 time=18ms TTL=64

getinfo all:
http://pastebin.centos.org/29356

[Apower1984]

anyone?

[Apower1984]

resolved.

solution: http://serverfault.com/questions/249761 ... ng-locally