[Bug 1311247] Re: [Grubenv] error: malformed file, press any key to continue

Michael Rösch ubuntuusersde at dobiwe.de
Sun Nov 16 10:24:04 UTC 2014


Same Problem here on ubuntu14.04 recently upgraded from 13.10.
The workarounds setting the grub default option is not possible for me, because I am using the system with vdr.
The vdr sets a wakeup-time which is programmed in the BIOS with nvram.
My mainboard requires a reboot for making this setting effective which is achieved by turning the system-shutdown into a reboot and choose the last menu-entry "PowerOff".
However, it turned out that this is not happening when I switch of the system with the halt-command in the grub menu entry I call after reboot.
To clearify this is the content of my 40_custom:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry "PowerOff" {
        saved_entry=0
        save_env saved_entry
	sleep 4
        halt
}

When I switched off the system by power key, it worked.
The only way to make it work again was downgrading to the previously used version
2.00-19ubuntu2.1
and set the packages on hold in aptitude.

Why are we using beta-versions in a LTS-distribution?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1311247

Title:
  [Grubenv] error: malformed file, press any key to continue

Status in GRand Unified Bootloader:
  Unknown
Status in “grub2” package in Ubuntu:
  Triaged

Bug description:
  I have just upgraded from 12.04 to 14.04

  Since the upgrade, when I boot up, the process stops and the normal
  grub screen is replaced after a short while by a message saying

  "error: malformed file, press any key to continue"

  Pressing a key allows booting to continue.

  Someone else who experienced this found that the problem went away
  after having re-installed grub.  I tried this but this did not resolve
  the problem for me.

  synaptic reports the grub package as 2.02~beta2-9

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1311247/+subscriptions



More information about the foundations-bugs mailing list