On Sun, May 04, 2008 at 05:01:32PM +0300, Török Edwin wrote:
> >>
> >> Device Boot Start End Blocks Id System
> >> /dev/sda1 * 1 1275 10241406 7 HPFS/NTFS
> >> /dev/sda2 1276 2248 7815622+ a6 OpenBSD
> >> /dev/sda3 2249 5289 24426832+ f W95 Ext'd (LBA)
> >> /dev/sda4 6080 7296 9775552+ bf Solaris
> >> /dev/sda5 2249 2371 987966 82 Linux swap /
> >> Solaris
> >> /dev/sda6 2372 3587 9767488+ 83 Linux
> >> /dev/sda7 3588 3600 104391 83 Linux
> >> /dev/sda8 3601 4863 10145016 8e Linux LVM
> >> /dev/sda9 4864 5228 2931831 a6 OpenBSD
> >> /dev/sda10 5229 5289 489951 83 Linux
> [...]
> grub> ls (hd0,10)
> error: unknown device
> grub> ls (hd0,11)
> error: unknown device
> grub>
I tried reproducing your setup, but I can't hit the same bug. This starts to
look really nasty. Just spotted this:
/build/buildd/grub2-1.96+20080426/partmap/pc.c:141: partition 0: flag 0x80,
type 0x7, start 0x3f, len 0x1388afc
[...]
/build/buildd/grub2-1.96+20080426/partmap/pc.c:141: partition 0: flag 0x0,
type 0x82, start 0x2270f07, len 0x1e267c
for which I can't find any explanation other than memory corruption. Also,
due to a missing fflush() call the output is somewhat scrambled, which makes
it harder to track (I fixed this already in upstream).
Could you:
- Apply the attached patch & run grub-probe again (this time output
will be a bit more readable)
- Send it to [EMAIL PROTECTED]
?
Maybe someone there has an idea, but if it's memory corruption and we can't
reproduce it, tracing the problem remotely isn't going to work very well.
Thank you
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
