Bug 1156051 - Fedora don't boot after unrestricted option added to menuentry in grub2.cfg
Summary: Fedora don't boot after unrestricted option added to menuentry in grub2.cfg
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 20
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-23 13:24 UTC by Nuno Dias
Modified: 2016-02-25 14:23 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-29 14:21:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
grub2.cfg (4.36 KB, text/plain)
2014-10-24 10:01 UTC, Nuno Dias
no flags Details

Description Nuno Dias 2014-10-23 13:24:43 UTC
Description of problem:
Fedora don't boot after unrestricted option added to menuentry in grub2.cfg, the error i get is 
error: unknown argument "--unrestricted"

Version-Release number of selected component (if applicable):
grub2-2.00-26.fc20.x86_64
grub2-tools-2.00-26.fc20.x86_64


How reproducible:


Steps to Reproduce:
1. create a grub2.cfg with grub2-mkconfig
2.
3.

Actual results:
--unrestricted is added to menuentry in grub2.cfg and unless I delete that option, the system won't boot

Expected results:


Additional info:

Comment 1 Brian Lane 2014-10-23 18:08:26 UTC
Please include the non-working config file.

Comment 2 Nuno Dias 2014-10-24 10:01:25 UTC
Created attachment 950299 [details]
grub2.cfg

As requested the grub2.cfg

Comment 3 Brian Lane 2014-10-28 22:23:10 UTC
I am unable to reproduce this. I installed from a F20 DVD which has grub2-2.00-25 on it, added --unrestricted by hand and rebooted just fine. Upgraded to -26 and ran grub2-mkconfig (which now includes --unrestricted) and was still able to reboot.

The only thing I can think of is the grub2 version in your mbr may not support --unrestricted. You could try rerunning grub2-install --no-floppy <boot device> to make sure the current version is installed.

Comment 4 Nuno Dias 2014-10-29 14:21:30 UTC
It seeems the problem is gone, I don't know if was the grub2-install or un update of some package, but I don't have the error anymore.

Thanks

Comment 5 Adam Pribyl 2016-02-25 14:23:57 UTC
This is caused by incompatible version of grub2 installed in bootloader on the disk and the one that is generated by newer grub2-tools.


Note You need to log in before you can comment on or make changes to this bug.