[xubuntu-users] Boot Warning

[Petter Adsen]

Rob, you only sent your mail to me, so I'm Cc'ing to the mailing list
so everyone can see this.

On Sun, 03 May 2015 17:35:43 +1000
Rob Ward <rl.ward at bigpond.com> wrote:
> On 03/05/15 16:54, Petter Adsen wrote:
> > On Sun, 03 May 2015 10:14:04 +1000
> > Rob Ward <rl.ward at bigpond.com> wrote:
> >
> >> Nope, the fix was only temporary....
> >>
> >> rob at DesktopUbuntu:~$ sudo update-grub
> >> Generating grub configuration file ...
> >> Found linux image: /boot/vmlinuz-3.13.0-51-generic
> >> Found initrd image: /boot/initrd.img-3.13.0-51-generic
> >> Found linux image: /boot/vmlinuz-3.13.0-49-generic
> >> Found initrd image: /boot/initrd.img-3.13.0-49-generic
> >>
> >> .... 17 more images ....
> > Not that it should matter, but do you _need_ all these kernel
> > images?
> >
> I only realised I had them when I began to investigate this.  I have 
> found where to remove them.
> https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels
> There is long command there to remove all but the current one, but 
> apparently it says at least the last two should be retained.

Yes, keep your previous kernel when you do a kernel upgrade, but if you
do not specifically need any other kernel versions, then go ahead and
remove them. Run "sudo update-grub" afterwards.

> >> Found linux image: /boot/vmlinuz-3.11.0-12-generic
> >> Found initrd image: /boot/initrd.img-3.11.0-12-generic
> >> Found memtest86+ image: /boot/memtest86+.elf
> >> Found memtest86+ image: /boot/memtest86+.bin
> >> Found Microsoft Windows XP Home Edition on /dev/sda1
> >> done
> >>
> >> Could the XP be causing the problem?
> > I don't think so. Exactly when does the message appear? Is it
> > before or after the kernel is loaded? Is there anything interesting
> > in /var/log/boot.log?
> The message comes up immediately after the grub screen prompts close.
> 
> I have looked in boot.log and also ran "dmesg" cmd as well.
> They are attached.

They are not relevant, so I didn't forward them to the list.

> Most of the boot.log entries end with a clean OK so I am guessing
> they not the source of the problem.

This is correct.

> If anyone can quickly scan these for any clues I would appreciate it.
> I have inspected them line by line, but nothing has clicked with me.
> The more I see, the more I realise how little I understand.

This problem is well documented in bug 1311247 on Launchpad[1]. You
didn't say, but I assume you are running 14.04, which is affected. It
is fixed in grub2 2.02~beta2-21 which has been released for vivid. This
leaves you with the following options:

1) Ignore it. It's just cosmetic.
2) See if you can install the grub2 package from the vivid repos. I
   have no idea how safe or unsafe this is.
3) Convince someone to backport the fix to trusty.
4) Upgrade to vivid.

If I were you, I would go with option 1. When the prompt appears, the
system will continue booting after 5 seconds even if you do not press a
key. While annoying, that's all it really is.

In the future, when you get some kind of problem or error message and do
a web search, and one of the top hits you get is on
"bugs.launchpad.net", you really should read that page. This is the
authoritative source for all known Ubuntu bugs and possible
fixes/workarounds.

Petter

[1] https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1311247

-- 
"I'm ionized"
"Are you sure?"
"I'm positive."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 213 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/xubuntu-users/attachments/20150503/56c03f05/attachment.sig>