Syslinux - Jul 2013 - Chaining with chain.c32 from syslinux 6.01 error

?
In qemu (virtual machine) it is working ok.
?
On?a physsical machine syslinux does not boot at all :
?
? SYSLINUX 6.02 EDD 6.02-pre9 ...
? Boot error.


I attached the usb drive info.


________________________________
 From: Matt Fleming <matt at console-pimps.org>
To: Adrian Irimia <adixtx at yahoo.com> 
Cc: "syslinux at zytor.com" <syslinux at zytor.com> 
Sent: Monday, July 22, 2013 4:37 PM
Subject: Re: [syslinux] Chaining with chain.c32 from syslinux 6.01 error
  

On Mon, 22 Jul, at 12:07:34PM, Matt Fleming wrote:
> On Thu, 18 Jul, at 01:22:04PM, Adrian Irimia wrote:
> > Hi,
> > ?
> > ? I have a bootable usb with syslinux 5.10 on wich the following?code
is working ok.
> > ??? LABEL -
> > ?? MENU LABEL GRUB LEGACY
> > ?? MENU INDENT 1
> > ???? COM32 chain.c32
> >
 ???? APPEND boot fs grub=/boot/grub-legacy/stage2
grubcfg=/boot/grub-legacy/grub-legacy.cfg nohand nosect
> > ?
> > ?After upgrading to syslinux 6.01 (using bios) I receive the following
errors when selecting that menu option :
> > ?
> > ? ERR: Primary partition (in MBR) with invalid offset and/or length.
> > ? ERR: Cant't find myself on the drive I booted from.
> > ?
> > ?I mention that the errors are on a physsical machine (not a virtual
one - in a virtual qemu I receive only the 2nd error message).
>? 
> Thanks for the report, I can reproduce this bug. I'll take a look.
Adrian, could you try 6.02-pre9?

-- 
Matt Fleming, Intel Open Source Technology Center
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: USBInfo.Txt
URL:
<http://www.zytor.com/pipermail/syslinux/attachments/20130722/8043f3f4/attachment.ksh>

On Mon, 22 Jul, at 12:50:46PM, Adrian Irimia wrote:
> ?
> In qemu (virtual machine) it is working ok.
> ?
> On?a physsical machine syslinux does not boot at all :
> ?
> ? SYSLINUX 6.02 EDD 6.02-pre9 ...
> ? Boot error.
Presumably you were able to boot a previous version on this physical
machine? Does it now fail before even invoking chain.c32?

-- 
Matt Fleming, Intel Open Source Technology Center

Yes. Prior versions (all to 6.01 inclusive) are working very well.
?And yes it fail before invoking chain.c32 (as I said in qemu there is no
errors).
 

________________________________
 From: Matt Fleming <matt at console-pimps.org>
To: Adrian Irimia <adixtx at yahoo.com> 
Cc: "syslinux at zytor.com" <syslinux at zytor.com> 
Sent: Tuesday, July 23, 2013 5:16 PM
Subject: Re: [syslinux] Chaining with chain.c32 from syslinux 6.01 error
  

On Mon, 22 Jul, at 12:50:46PM, Adrian Irimia wrote:
> ?
> In qemu (virtual machine) it is working ok.
> ?
> On?a physsical machine syslinux does not boot at all :
> ?
> ? SYSLINUX 6.02 EDD 6.02-pre9 ...
> ? Boot error.
Presumably you were able to boot a previous version on this physical
machine? Does it now fail before even invoking chain.c32?

-- 
Matt Fleming, Intel Open Source Technology Center

> ?
> In qemu (virtual machine) it is working ok.
> ?
> On?a physsical machine syslinux does not boot at all :
> ?
> ? SYSLINUX 6.02 EDD 6.02-pre9 ...
> ? Boot error.
> 
> 
> I attached the usb drive info.
> 
 
The CHS values in the Partition Table are inconsistent with the LBA 
and fs size.

Partition Table:
Start CHS:    0 /   1 /  1
End   CHS:  888 / 254 / 63 (*)

Partition #1 (FAT32LBA, type: 0C):
Start LBA: 63
Size  LBA: 30736321 (*)
End   LBA: 30736383 (*)

If I'm not mistaken, the last 2 values should better be:
Size  LBA: 30732282
End   LBA: 30732345

leaving 4038 unpartitioned sectors at the end of the device.

Then the corrected values would be:
Start CHS:    0 /   1 /  1
End   CHS: 1023 / 254 / 63

(note the "1023" instead of "888")

and:

Partition #1 (FAT32LBA, type: 0C) (for cyl. alignment):
Start LBA: 63
Size  LBA: 30732282
End   LBA: 30732345
Size bytes: 15734928384

Partition #2 (free space, type: 00):
Start LBA: 30732345
Size  LBA: 4038
End   LBA: 30736383

Although, I could have missed some calculation.

Then format the new Partition #1.

Regards,
Ady.

> Partition #1 (FAT32LBA, type: 0C) (for cyl. alignment):
> Start LBA: 63
> Size  LBA: 30732282
> End   LBA: 30732345
> Size bytes: 15734928384
> 
> Partition #2 (free space, type: 00):
> Start LBA: 30732345
> Size  LBA: 4038
> End   LBA: 30736383
> 
> Although, I could have missed some calculation.
> 
 
And I did :(. Correction:

Partition #2 (free space, type: 00):
Start LBA: 30732346
Size  LBA: 4037
End   LBA: 30736383

Apologies.