How to capture console messages during boot

Asked by Mike H

Is there any way to capture the FULL range of messages that scroll up the console during boot?

I'm running Feisty Fawn 7.04 64-bit workstation with raid 1. Due to the race condition with mdadm not having the arrays assembled before attempts are made to mount the array devices, I have quiet=n and break=mount set in my menu.lst to force the system to pause so that the array assembly can complete. Consequently I can see the boot process messages on the console. The other day, following recovery from a backup, I noticed some errors among the boot messages but was unable to read them fully because they scrolled off the screen too quickly.

None of these messages appear in any of the log files in /var/log.

I tried enabling bootlogd so that these messages would be recorded in /var/log/boot, but it wouldn't work. Further researches showed that this no longer works in Feisty and has intentionally been disabled.

In the end I had to film the boot process with a digital camera in order to be able to read these error messages and fix the underlying problem!!!

This is hardly the kind of thing you expect to have to do in the world of Linux, is it? Surely there must be a better way to capture these boot-time messages?

I have searched the forums, but have been unable to find a solution. Lots of folk suggest enabling /etc/default/bootlogd, (examples in http://ubuntuforums.org/showthread.php?t=49925), but it doesn't work on Feisty due to this bug https://bugs.launchpad.net/upstart/+bug/98955

Just to be completely clear, these messages DO NOT appear in /var/log/dmesg or in any of the other files in /var/log.

So, until there's a proper fix, how do I capture these messages without having to use a digital camera?

Surely, there must be a way.... Even Bill Gates would do better than this.

Mike

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Bogdan Butnaru
Solved:
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Mike H (mike-heden) said :
#2

Does anyone have an answer to this?

Revision history for this message
Launchpad Janitor (janitor) said :
#3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Mike H (mike-heden) said :
#4

From the deafening silence I conclude there must be no solution at all to this problem....

Revision history for this message
Best Bogdan Butnaru (bogdanb) said :
#5

Apparently not. There's also https://bugs.edge.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/137254 --- you might want to subscribe to it, maybe eventually someone will do something.

Revision history for this message
Mike H (mike-heden) said :
#6

Thanks - I've just subscribed to it. And I had assumed that this was just a Feisty problem.... :-(

Well, I guess I'll click the 'problem solved' button now, although it's not entirely appropriate, is it. How about a "my problem isn't solved, but I'll go away" option?

Thanks for your help. Maybe it will be eventually fixed in Gutsy.

But seeing that there's clearly no way this is going to get fixed in Feisty...... <click>

Revision history for this message
Mike H (mike-heden) said :
#7

Thanks Bogdan Butnaru, that solved my question.