Broken EPBR chaining?

This is little lengthy...
I have been using disk director to snoop my disk and in specific to take a closer look at the partition records. I have the following setup (can provide further specific details of the partition records if anyone is interested):

Three (3) Primary partitions:[/B ]
Windows XP NTFS (C: )
Windows XP FAT32 (D: )
Linux Ext3 (/)

One (1) Extended partition record:
This is the start of an EPBR chain that "should" locate a total of three (3) extended partittions.

The three primary partition start/end sectors are identified correctly .

The extended partition pointer in the MBR points to a valid EPBR and this first EPBR contains a valid pointer to an extended partition and a valid pointer to the next EPBR in the chain .

Okay... So now we're at the second EPBR and it contains a valid pointer to an extended partition but the the EPBR pointer points to a sector which is contained within an extended partition . Now the chain is broken and the remaining two extended partitions should be considered lost... right?

Well it seems that the EPBR chaining really does not matter because Disk Director is locating the remaining partitions by analyzing the EPBR that is located in the first sector following each valid partition found . At least that is what I think Disk Director is doing.

So what's my issue? I used Disk Director to partition this disk and based on common practice the EPBR chaining should be intact/valid. Can anyone provide some insight into why the EPBR chain created by Disk Director might be broken? Any insight that could be provided would be much appreciated.

 

Hello cws,

Thank you for choosing Acronis Partition and Disk Managing Software.

Could you please create Acronis Report as it is described in Acronis Help Post? This would provide us with detailed information on the hard disk partition structure.

Please submit a request for technical support. Attach the collected report file to your request along with the link to this thread. We will investigate the problem and try to provide you with the solution.

Thank you.
--
Kirill Omelchenko