Re: Problem after update with grub and --unrestricted on i386

[Jordan Uggla]

On Fri, Sep 5, 2014 at 3:06 PM, Michael D. Setzer II
<address@hidden> wrote:
> On 5 Sep 2014 at 14:58, Jordan Uggla wrote:
>
> From:                   Jordan Uggla <address@hidden>
> Date sent:              Fri, 5 Sep 2014 14:58:23 -0700
> Subject:                Re: Problem after update with grub and --unrestricted 
> on
> i386
> To:                     "Michael D. Setzer II" <address@hidden>
> Copies to:              help-grub <address@hidden>
>
>> On Thu, Sep 4, 2014 at 11:04 PM, Michael D. Setzer II
>> <address@hidden> wrote:
>> > I just rebooted the machine again, and problem is that it doesn't
>> > show what the file is: just get the message
>> >
>> > error: file not found
>> > error: file not found
>> > error: file not found
>> >
>> > Press any key to continue
>> >
>> > It does then continue after waiting a short time, so one doesn't
>> > have to press any key.
>> >
>> >
>> > I did just find the the grub had some insmod with efi and ieee which
>> > where not in the /boot/grub2 directory, so commented them out, and
>> > that elimanated the file not found messages.
>> >
>> > But still not sure about the --unrestricted issue.
>> >
>> > Another issue might be that the grub2 directory has lots more files
>> > than the machines that are running the 64bit versions, and they were
>> > clean installs while these were older machines that were upgraded to
>> > f20 from older versions, and it appears they may not had the space
>> > after the mbr.
>> >
>> > The grub2 is reported as 2.00-26
>>
>> Where are you seeing the version reported? At boot at the top of the
>> grub menu?
>
> rpm -q grub2
>
> grub2-2.00-26-fc20.i686

My strong suspicion is that while you may have grub 2.00 *utilities*
installed, Fedora hasn't properly run grub-install to install grub
2.00 as your bootloader, and thus you're left with some older version
of grub that was installed previously. Please check what version of
grub is reported at boot (if that is difficult for some reason, there
are ways to check while booted also).

-- 
Jordan Uggla (Jordan_U on irc.freenode.net)