CentOS has recently started booting slower than it did before. Just when X starts up and the screen is dark blue and the only thing is the hour glass in the middle of screen turning round and round. It stays like that for quite a while, and then later it will resume the normal boot process. This long pause did not exist before.
This seems to have started happening after I installed a FAT32 drive. So my guess is that for whatever reason, it takes CentOS a while to mount that drive. Actually, I'm a little concerned that maybe CentOS is doing something to the drive, some kind of directory reordering or something, because whenever I look at the drive from Windows and use Diskeeper (defragmenting software), it seems to have excessive fragmentation.
But I don't know for sure that linux is doing anything to the drive, and I don't even know for sure that it's because of the drive that the boot process now has this added delay.
So my first question, I suppose, is - What do I do to diagnose what is causing the delay in my boot process?
Dave
On Fri, 2005-09-09 at 15:10 +0900, Dave Gutteridge wrote:
CentOS has recently started booting slower than it did before. Just when X starts up and the screen is dark blue and the only thing is the hour glass in the middle of screen turning round and round. It stays like that for quite a while, and then later it will resume the normal boot process. This long pause did not exist before.
This seems to have started happening after I installed a FAT32 drive. So my guess is that for whatever reason, it takes CentOS a while to mount that drive. Actually, I'm a little concerned that maybe CentOS is doing something to the drive, some kind of directory reordering or something, because whenever I look at the drive from Windows and use Diskeeper (defragmenting software), it seems to have excessive fragmentation.
But I don't know for sure that linux is doing anything to the drive, and I don't even know for sure that it's because of the drive that the boot process now has this added delay.
So my first question, I suppose, is - What do I do to diagnose what is causing the delay in my boot process?
I would recommend that you remark out the line that mounts that drive in /etc/fstab and reboot to see if it still does that.
If it still happens, I would try to setup my machine to boot linux without that drive present and see if it happened. (That might entail changing some drive jumper settings).
I would recommend that you remark out the line that mounts that drive in /etc/fstab and reboot to see if it still does that.
Okay, I commented the line out of /etc/fstab and the long delay during the boot process is still there.
So now I'm at a loss to suggest any other recent configuration that I've done that could potentially be the problem.
Without having any other guesses about what is causing the delay, what would be a way to diagnose it?
Dave
On Sat, 2005-09-10 at 11:38 +0900, Dave Gutteridge wrote:
I would recommend that you remark out the line that mounts that drive in /etc/fstab and reboot to see if it still does that.
Okay, I commented the line out of /etc/fstab and the long delay during the boot process is still there.
So now I'm at a loss to suggest any other recent configuration that I've done that could potentially be the problem.
Without having any other guesses about what is causing the delay, what would be a way to diagnose it?
You could try changing the kernel entry in /etc/grub.conf and remove the "rhgb quiet" to disable the graphical boot. This will give you the classic linux boot look and you can watch what is happening as it goes through the startup and see where it is hanging. One thing that often causes a "longish" hang is bringing up an interface that doesn't have a network cable attached to it while it tries to find a dhcp server (although this is much better than it used to be).
-
Dave Gutteridge -
Johnny Hughes -
Sean O'Connell