grub-setup crashed with SW RAID 0

[jmp7]

Binary package hint: grub2

Grub2 seems impossible to install on an md (S/W RAID0) to me. grub-setup crashes.

Hard-disks partition tables are msdos; RAID0 made for the whole disks, and two partitions are made: md0p1 EXT4 and md0p2 SWAP. A 500MB space is left at the beginning of the RAID for grub install.

ProblemType: Crash
Architecture: amd64
Date: Thu Mar 25 01:03:19 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/grub-setup
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Package: grub-pc 1.98-1ubuntu1
ProcCmdline: grub-setup /dev/md0 --verbose
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x405e90: repz cmpsb %es:(%rdi),%ds:(%rsi)
 PC (0x00405e90) ok
 source "%es:(%rdi)" (0x004233a2) ok
 destination "%ds:(%rsi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: grub2
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
Title: grub-setup crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 grub_util_load_image (path=0x0, buf=0x0)
 __libc_csu_init ()
 ?? ()
ThreadStacktrace:

[jmp7 (jacobopantoja-yahoo)]

With official Ubuntu 10.04 (the bug was written with beta1, i think) the problem is gone; grub2 installs and now it is possible to boot s/w raid partitions from grub2

[Colin Watson (cjwatson)]

Thanks for re-testing. Closing.