Bug 1074164 - 'env_save' command not found
Summary: 'env_save' command not found
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 20
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-08 12:47 UTC by Steven Haigh
Modified: 2015-06-29 19:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:21:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Steven Haigh 2014-03-08 12:47:38 UTC
When trying to save the last selected grub2 option as the default for the next boot, grub gives an error "env_save command not found' while booting.

# cat /etc/default/grub 
GRUB_TIMEOUT=1
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="vconsole.font=latarcyrheb-sun16 rd.luks.uuid=luks-e769e82d-df73-473b-9783-06997c4ce259 $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rhgb quiet video.use_native_backlight=1 i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.lvds_downclock=1"
GRUB_DISABLE_RECOVERY="true"
GRUB_GFXMODE=text

# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg 
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.13.5-202.fc20.x86_64
Found initrd image: /boot/initramfs-3.13.5-202.fc20.x86_64.img
Found linux image: /boot/vmlinuz-3.13.5-200.fc20.x86_64
Found initrd image: /boot/initramfs-3.13.5-200.fc20.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-3f204f4d3fde4532ad1b173c590e65e3
Found initrd image: /boot/initramfs-0-rescue-3f204f4d3fde4532ad1b173c590e65e3.img
done

No matter which option I boot with, I get the error. Upon next reboot, the first entry in the list is automatically selected.

As above, the system is EFI enabled. I'm not sure if this is part of the bug or just extra information.

Comment 1 c.m.western 2014-04-28 19:56:28 UTC
I am having the same problem, with a similar configuration. It seems the efi grub install puts most of the files in the wrong place. I was able to make my set-up work with the following:

cd /boot
mv grub2/* efi/EFI/fedora/
rmdir grub2
ln -s efi/EFI/fedora grub2

cd /boot/efi/EFI/fedora/
mv /usr/lib/grub/x86_64-efi .
cd /usr/lib/grub/
ln -s /boot/efi/EFI/fedora/x86_64-efi

Comment 2 c.m.western 2014-06-28 09:58:26 UTC
The recent upgrade to grub2-efi.x86_64 1:2.00-26.fc20 has removed the files in /usr/lib/grub/x86_64-efi that were required for the above fix to work.

Comment 3 Fedora End Of Life 2015-05-29 11:11:43 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-29 19:21:21 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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