[Bug 1050774] Re: grub-script-check assert failure: *** glibc detected *** /usr/bin/grub-script-check: double free or corruption (!prev): 0x08210b38 ***

[Colin Watson]

I would really appreciate it if we could keep bugs to a single problem
each.  The more you all follow up to this with multiple different
problems, the harder it becomes for me to keep track, and the lower the
probability of me being able to keep track well enough to fix anything.

I'll answer a couple of specific points here, but I won't follow up on
them further; if you want to record these as things we need to fix,
please file separate bugs.

  /usr/sbin/grub-bios-setup: warning: file system 'ext2' doesn't support
embedding.

Unlike Linux, GRUB has a single filesystem driver for all of ext2, ext3,
and ext4, which is simply called "ext2".  The above message does NOT
indicate that it has incorrectly recognised ext4 as ext2.  It's just its
name for its driver for all such filesystems.

The reports of alloc magic being broken might be a consequence of the
overly-long menu entry strings here, but they might also be a
consequence of confusion induced by different versions of GRUB in your
multiple-disk setup.  This is similar to the basic problem outlined
here:

http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/debian/2010-06-21-grub2
-boot-problems.html

In short, if the core image installed on the MBR or a partition boot
record does not match the modules in /boot/grub, you're going to have
problems.  Try to avoid setups that could lead to this.  Running 'sudo
dpkg-reconfigure grub-pc' and selecting the MBRs of all non-removable
disks can help, but in general if you have multi-disk and multi-OS
setups then you need to be very clear about which one owns the boot
process.  Based on my experience with many such upgrades, there is a
good chance that this is not a regression from 1.99 at all; it's simply
been exposed by any non-trivial change to the version of GRUB.

>From here on in, I am not going to address these problems any further in
this bug; I'm focusing solely on the incorrect menu entry generation,
which is the same as arpanaut's report in bug 1051624.

-- 
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/1050774

Title:
  grub-script-check assert failure: *** glibc detected *** /usr/bin
  /grub-script-check: double free or corruption (!prev): 0x08210b38 ***

Status in “grub2” package in Ubuntu:
  Triaged

Bug description:
  Lubuntu Quantal i386

  Yesterday i've tested grub 2.0 fromm the cjwatson ppa without issue.
  Then i've ran vbeinfo on next boot to fill custom values :
  GRUB_GFXMODE=1024x768,800x600

   Today the new 2.00-3ubuntu1 is upgraded and get that problem. Note
  that ubuntu quantal i386 have been previously upgraded with this
  latest grub 2.0 without that issue.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: grub-common 2.00-3ubuntu1
  Uname: Linux 3.6.0-030600rc5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: i386
  AssertionMessage: *** glibc detected *** /usr/bin/grub-script-check: double free or corruption (!prev): 0x08210b38 ***
  Date: Fri Sep 14 09:06:51 2012
  ExecutablePath: /usr/bin/grub-script-check
  ProcCmdline: /usr/bin/grub-script-check /boot/grub/grub.cfg.new
  Signal: 6
  SourcePackage: grub2
  StacktraceTop:
   __libc_message (do_abort=2, fmt=0xb77271dc "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
   malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0x8210b38) at malloc.c:5007
   ?? ()
   ?? ()
   ?? ()
  Title: grub-script-check assert failure: *** glibc detected *** /usr/bin/grub-script-check: double free or corruption (!prev): 0x08210b38 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1050774/+subscriptions