Bug#523763: grub-common: floating point exception in grub-probe

[Felix Zielcke]

Am Sonntag, den 12.04.2009, 14:27 +0200 schrieb Felix Koop:
> Here is the backtrace:
> 
> (gdb) file grub-probe
> Reading symbols from /usr/src/grub2-1.96
> +20090317/build/grub-common/grub-probe...done.
> (gdb) run --target=device /
> Starting program: /usr/src/grub2-1.96
> +20090317/build/grub-common/grub-probe --target=device /
> /dev/mapper/jupisdd-root
> 
> Program received signal SIGFPE, Arithmetic exception.
> 0x0000000000406cf4 in grub_divmod64 (n=11784322, d=0, r=0x7fff240cb6bc)
>     at /usr/src/grub2-1.96+20090317/kern/misc.c:609
> 609		*r = ((grub_uint32_t) n) % d;
> (gdb) backtrace
> #0  0x0000000000406cf4 in grub_divmod64 (n=11784322, d=0,
> r=0x7fff240cb6bc)
>     at /usr/src/grub2-1.96+20090317/kern/misc.c:609
> #1  0x0000000000420f05 in grub_raid_read (disk=0x241a0f0,
> sector=1508393216, 
>     size=8, buf=0x24d3eb0 "") at /usr/src/grub2-1.96
> +20090317/disk/raid.c:228

Weird. That would mean array->total_devs is 0
Beetween lenny and sid/squeeze version it hasn't changed that it's taken
from the mdraid superblock. But the RAID code itself has.
How does your RAID arrays look like? (`mdadm -Q --detail /dev/md0' etc.)
Maybe there's somewhere a mdraid superblock lying around which you
should `mdadm --zero-superblock'
-- 
Felix Zielcke