Bug#662787: Error: core.img unusually large after upgrade

[richie]

I still have the same issue after upgrading to grub2 1.99-17 (debian 
testing). Setup is mdraid+lvm.  I am adding in some comparison 
information against an older box.  The second chunk applies to the PC in 
question.

another pc w/same 63 sector start position for first partition  on 
ubuntu lucid and no core.img issue) grub-pc ver is 1.98+20100722-1ubuntu1
$ ls -l raid.mod mdraid.mod lvm.mod ext2.mod core.img
-rw-r--r-- 1 root root 5504 2010-09-26 17:52 ext2.mod
-rw-r--r-- 1 root root 6060 2010-09-26 17:52 lvm.mod
-rw-r--r-- 1 root root 2652 2010-09-26 17:52 mdraid.mod
-rw-r--r-- 1 root root 6096 2010-09-26 17:52 raid.mod
-rw-r--r-- 1 root root 29326 2010-09-26 17:52 core.img

(current pc debian wheezy w/the issue) grub-pc ver is 1.99-17
$ ls -l raid.mod mdraid*.mod lvm.mod ext2.mod
-rw-r--r-- 1 root root 5892 Apr  1 21:49 ext2.mod
-rw-r--r-- 1 root root 7216 Apr  1 21:49 lvm.mod
-rw-r--r-- 1 root root 1976 Apr  1 21:49 mdraid09.mod + (this one would 
get used in my setup)
-rw-r--r-- 1 root root 2388 Apr  1 21:49 mdraid1x.mod -
-rw-r--r-- 1 root root 6548 Apr  1 21:49 raid.mod
-rw-r--r-- 1 root root 31417 Apr  1 21:49 core.img


(62x512)-512 for MBR = 31232 <-- is this the max area to write the core.img?

I realize the long term solution is to start first partition at around 
sector 2048 or use GPT, but the bug update made it seem like we should 
be able to fit a core.img when mdraid/lvm is involved  ??