[xubuntu-users] Boot Warning

[Rob Ward]

On 03/05/15 19:59, John Deakin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Rob,
>
> I had this earlier and on start-up the boot was looking at my second
> data disk and therefore not finding the necessary config files.
>
> Have a look in the BIOS to see which device it is reading first and make
> sure the BIOS is looking at your operating system disk first.
>
> regards,
> John
>
I have tried your advice John and it appears to be working. 
Though,caution dictates here,  I have been apparently overly optimistic 
before!
I have four hard drives on my computer, A legacy XP Home Edition 320Gb, 
a 14.04 XUbuntu 320Gb, an internal data drive 1Tb and and external USB2 
drive 1Tb.
I tried a few combinations of re-jigging the boot drive order and found 
that if the XUbuntu was first, followed by the XP, and then the data 
drive last, it removed the error.  I believe I had the XP drive third in 
line previously.  The XUbuntu drive was always first, (otherwise, as I 
found out, it booted to XP, or not all).
So probably Petter is right this is a problem/bug that GRUB, or the OS, 
should cope with automatically, but (fingers crossed) this strategy does 
appear to remove the problem.  So there maybe some sort of mis-match 
between the drives and a file that expects to synch' them to a list, and 
it is OS drives first, data drives after that. Or maybe the GRUB file 
was made that way when XUbuntu was installed, and I have changed them 
later on to cause the inconsistency?  The data drive was added last and 
I may have inserted it "electronically" between the others by the socket 
on the mother board I chose???

However it would appear John's suggestion has also borne fruit, and is a 
good work around?

Thanks to all those who spent time helping with this problem, cheers!!!

Rob

> On 03/05/15 09:49, Petter Adsen wrote:
>> Rob, you only sent your mail to me, so I'm Cc'ing to the mailing list
>> so everyone can see this.
>>
>>>> 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
>>
>>
>>