I'd like to find out what takes the most time in my boot process from GRUB to the Ubuntu login screen. How can I profile my boot process to find out what's taking so long?
on 01/30/2012 – Made popular on 01/30/2012
My EC2 (Ubuntu 12.04 server) took about 1 min to boot (defined as the time between power-on and all the daemon processes are started). I need to cut down the time to boot. My guess is that the total time depends on kernel boot time and the time to start all the daemons.
Kernel doesn't seem to take much time (the following is from my kern.log) and it showed it didn't take about 14sec.
Is there any concensus out there about when Fedora will work out its problems and be ready for prime time?
If someone doesn't understand the question, then consider the following:
1. With the latest Fedora 17, Beefy Miracle, installed, the installation routine creates a a GRUB2 that has an error in the file, as flashed on the screen for a split second at every boot.
If you are having problem with the boot process which takes too long, you have to try this free software called Soluto. Soluto is a special software that will cut off the boot process extremely. With Soluto you can improve the computer’s start-up time by removing unnecessary applications from the system’s boot-up sequence.
I have made a clean install of Precise Pangolin on my desktop PC shortly after it was released in April and at some point after that I have started to experience an issue with the boot time being astounding 150 (sic!) seconds; in Oneiric the boot time was around ten seconds plus another ten GRUB waited before booting Ubuntu.
Visually, boot process seems go normally, though a BIOS logo stays on
I am trying to install Qubes from a USB stick. Unfortunately it seems that there's some hardcoding taking place in the boot process, so after i have put the ISO on the stick it still looks to mount /dev/sr0, and after it can't find it, the boot process freezes.
Is it possible to remap the usb stick as the sr0 with grub that is used by unetbootin?
We're having some issues with Windows 7 Roaming profiles and I was reading here that the login process can be monitored using process monitor.
"There are a couple of ways to configure Process Monitor to record
logon operations: one is to use Sysinternals PsExec to launch it in
the session 0 so that it survives the logoff and subsequent logon and
another is to use the boot logging feature