Skip to main content

[SOLVED] DD11 / OSS maps 5 partitions when booting into win7 ?!

Thread needs solution

i'm using ADD / OSS 11.0.2121 and i've discovered something weird.
i fear it will lead to severe errors and data loss.

i have the following partition layout (with AHCI enabled):

HD0:
 0.a primary (win7 64 boot)
 0.b primary (win7 64 system)
 0.c primary (data)

HD1:
 1.a primary (win xp 32)
 1.b primary (win7 64 boot)
 1.c primary (win7 64 system)
 1.d extended
   1.d.0 logical "storage"
   1.d.1 logical "data exchange" - shared between all 3 operating systems

[update: in reply #4 i have attached a screenshot ot outline my partitioning concept. it's much easier to look at the screenshot than reading the text]

and then i have installed OSS 11 from a bootable CD. my logical concept is as follows:
i'm putting a "*" where partitions shall be "hidden":

I) my "main" system is on HD0.
OSS configuration:

HD0:
 0.a primary (win7 64 boot)
 0.b primary (win7 64 system)
 0.c primary (data)

HD1:
*1.a primary (win xp 32)
*1.b primary (win7 64 boot)
*1.c primary (win7 64 system)
 1.d extended
   1.d.0 logical "storage"
   1.d.1 logical "data exchange"

II) my "test XP" system is on HD1.
OSS configuration:

swap boot device order = YES.

HD0:
*0.a primary (win7 64 boot)
*0.b primary (win7 64 system)
*0.c primary (data)

HD1:
 1.a primary (win xp 32)
*1.b primary (win7 64 boot)
*1.c primary (win7 64 system)
 1.d extended
* 1.d.0 logical "storage"
   1.d.1 logical "data exchange"

III) my "test win7" system is on HD1.
OSS configuration:

swap boot device order = YES.

HD0:
*0.a primary (win7 64 boot)
*0.b primary (win7 64 system)
*0.c primary (data)

HD1:
*1.a primary (win xp 32)
 1.b primary (win7 64 boot)
 1.c primary (win7 64 system)
 1.d extended
* 1.d.0 logical "storage"
   1.d.1 logical "data exchange"

PROBLEM DESCRIPTION:
boot options I and II are working fine. but there's a problem with option III:

when i'm booting into the "test win7" on the second HDD the "disk management" of windows 7 shows the following details for HD1:
*1.a primary (win xp 32)
 1.b primary (win7 64 boot)
 1.c primary (win7 64 system)
*1.d primary "storage"  <== look here
  1.e extended "data exhange<= look here

in other words: OSS made two primary partitions instead of one extended partition containing two logical drives.
so i'm ending up with 5 partitions ?!
as far as i know it's only allowed to have a maximum of 4 partitions per disk - either primary or extended. where insided an extended partition there can be as many logical drives as you want. but there can not be more than 4 partitions.

this looks like a serious bug to me and i fear to suffer from data loss.

 
note: when i boot into option II (win xp), everything is fine.
the "disk management" of windows xp is showing the HD1 as follows:
  1.a primary (win xp 32)
*1.b primary (win7 64 boot)
*1.c primary (win7 64 system)
 1.d extended
* 1.d.0 logical "storage"
   1.d.1 logical "data exchange"

can you confirm this is a bug?
is there any danger of data loss?

 thanks in advance, philipp

0 Users found this helpful

Using an MBR based system there are a maximum of 4 primary partitions, but within an extended partition your choice is limitless.

Whether OSS is showing the correct entries I don't know, I haven't used OSS for many a year, Mudcrab is the expert on what OSS should or shouldn't contain.

I suspect what you're seeing is just the difference between how Disk Management and DD/OSS display the partitions. If you posted a screenshot of each, I could tell for sure. If this is the case, there's nothing to worry about except don't use Disk Management to make partitioning changes on the drive. Instead, use DD since it sees them correctly.

FYI, I have seen this same behavior with the Disk Management function of Win7x64 and believe it is a bug that is expressed when there's a hidden partition on a drive. I have a multi-boot system and have attached both a WinXP Pro and a Win7x64 view of my disks from Disk Management.

The first attachment is from within WinXP Pro and correctly shows all partitions. I have 4 bootable partitions on Disk 0, all independent of each other, the last 2 of which are in logical partitions. [For the record, I have BootIt Next Generation, which is loaded on the first Primary and is set to limit my Primaries to 4.] My DD10 on BartPE view is consistent with the WinXP Pro view (as is BING; I do not have DD11). I hide all the other partitions on Disk 0 when booting to each one.

The second attachment shows the Disk Management view from within Win7x64, this one from the Win7x64 instance on the primary partition of Disk 0. You can see that the two logical partitions shown in the WinXP view are now erroneously shown as primary in the Win7x64 view, leading to 5 primaries shown here. The extended partition envelope is also erroneously shown. I also have a hidden logical partition at the end of Disk 1 that shows correctly in WinXP's Disk Management view but also shows erroneously in Win7's Disk Management view as a primary, and the extended partition definition is consequently also in error in the latter view. The same erroneous views are seen no matter which Win7x64 instance is booted (with minor differences due to which partition is booted / unhidden). Disk 2 has no hidden partitions and shows correctly from both OS's Disk Management views. Also note that WinXP shows the volume label and file system of the hidden partitions, whereas Win7 does not.

It's been a while since I diagnosed this problem, so memory has faded a bit, but the problem did seem to track with hidden partitions based on the testing I did at the time. For example, when I unhid the last Disk 1 partition, both OS's Disk Management views were correct / in agreement for Disk 1. As this is a recently built PC, I was meaning to temporarily load Win7 on my older PC just to confirm the same behavior on different hardware but have not gotten around to this as of yet.

Doug

Attachment Size
49491-92686.jpg 132.3 KB
49491-92689.jpg 158.07 KB

thanks for the replies so far!

well, screenshots. i had not thought of that option.
so i'm now attaching the screenshots for all three operating systems booted into:

I) main win7
everything fine

II) win xp 32
i just noticed it's setting the wrong partition as "active"?
even though in OSS configuration i have set the "xp" partition to be set active.

III) test win7
this is my initial concern. it's showing as 4 primaries + 1 extended = 5 in total!

i've also attached a screenshot to outline my partition and boot concept.

thanks in advance, philipp

Attachment Size
49504-92692.png 5.69 KB
49504-92695.png 19.69 KB
49504-92698.png 17.85 KB
49504-92701.png 19.76 KB

Windows 7 Disk Management does not correctly show hidden Logical partitions as Logical. Instead, it shows them as Primary. This shouldn't cause any problems with using the partitions normally. Just don't change those partitions with Disk Management (use DD).

For the XP Active partition problem, it looks okay to me. XP's Disk Management does not display "Active" for the booting partition, just "System". In addition, the 100MB partition you indicate is on a different drive and it's normal for that partition to be Active.

thanks, mudcrab!

so i'm happy to hear that it's no bug with ADD / OSS.

instead, it's rather a bug in the diskmanagement of windows 7.

i've just booted into that suspicuous "test win7" system once more and invoked "diskpart.exe" - http://support.microsoft.com/kb/300415/en-us

 - diskpart.exe

 - select disk 1

 - list partition

and it's properly listing my extended partition as containing two logical drives :)

and i've also found some details on http://www.multibooters.co.uk/quirks.html

You may see several primary partitions on a drive.
Logical partitions that are either hidden or of an unsupported file system will show up in Vista’s Disk Management utility as primary partitions. Not only that but the extended partition can appear to not include these logicals. It can be confusing the first time you see it and can make you think you have a corrupted partition table.
[...]
note: Vista SP1-2, 2008 and Windows 7 have not rectified this issue, yet.

.

thanks, philipp