Make sure you have the bootchart package installed. Remove the ureadahead pack files, and move the /etc/init/ureadahead.conf file to something like ureadahead.disabled. Reboot, login, etc. and wait for the bootchart to appear (“watch status bootchart” until stop/waiting).
Now put the ureadahead conf file back, reboot and login again and wait for bootchart to appear.
Finally reboot and login once more, and wait for bootchart to appear.
You’ll now have three bootcharts. One is without ureadahead, one is when ureadahead is profiling, and the final one is with ureadahead behaving normally.
File a bug report on ureadahead (ubuntu-bug ureadahead) and attach these three files along with the output of “sudo ureadahead –dump” (this is quite a bit, so capture it in a file).
I’ll take a look, and we’ll see if we can fix that bug for you!
ureadahead exits with status 4!
This isn’t actually a bug
Status 4 (usually ureadahead-other exits with this) means that you had a mountpoint in your fstab that didn’t have any files on it needed during boot. Probably that drive with all those MP3s and movie files on it.
It still reads everything needed during boot, the status is just there for me to debug other issues.
The real bug here is that Upstart spams the console with that message, even though the ureadahead-other.conf file has “normal exit 4″ in it!
(In other words, If your boot fails, this message is completely unrelated to that! It’s more likely that there is an issue with the X server starting, or an issue with init scripts not being run — a good clue might be whether you see a login: screen after pressing Alt+F2)
Last edited by keybuk; March 22nd, 2010 at 08:23 AM..