BUG: Partition created as primary still showing up "Logical" within extended partition in Disk Manager
Hi there,
I can see there's already a LOT of riot going on about still virgin ADD 11.
First of all, I'm SOOOO happy that we finally have Windows 7 support!
That was the polite way. The impolite way is:
"´Bout time, dammit!" :P
Seriously though, there is a bit of a bug in the latest 11 version.
Preconditions:
- 160 GB HDD (basic)
- P0 @ 160 GB, extended;
- P2 @ 70 GB, logical;
P3 @ 90 GB, logical.
That's the OLD setup, w/P1 absent. But now I needed to boot into XP SP2 for a customer, that's why I needed 10 GB free PRIMARY on this HDD.
So I thought that Acronis DD is intelligent...(well I THOUGHT)
- Resized P2 to a mere 60 GB
- Gained 10 GB free space at the beginning
- Saw that ADD preselected the "Logical Partition", but "Primary Partition" was available, so I selected the latter
- Created P1, PRIMARY (!), 10 GB
After all...
- ALL GREAT in DiskDirector, but in Disk Management (Windows 7) P1 still shows up as logical, with the extended partition starting at the first sector of the HD!!
That actually means:
Since ADD does not let me resize an extended partition manually, I need to BACKUP everything on the whole HDD, create all partitions anew so that the E. P. will start on offset +10.000001 GB this time!!
Yeah right, that's why I have a "professional" partitioning tool to be on my own after all, copying it all by hand, using diskpart to create new partitions ;)
MUAHAHAHA...
I *MUST* see this partition on my Disk Management in Windows as primary too, since other tools would report it the incorrect way too.
It would really be better leaving the decision to the (advanced) user whether we want Acronis DD to "handle" (haha) the extended partition stuff or do it all ourselves.
Since if ADD operates incorrectly, we'd have a sane (!!) way out. The non-sane way is the copying method described above.
related thread: http://forum.acronis.com/forum/3238

- Log in to post comments

YAY, that did it!!
Thanks a bunch, I would never have thought of that "trick" myself :D
Come to think of it: Maybe it was me who "broke" it because I chose the 1MB gap to be at the beginning of the physical hard disk instead of (as I have it now) BEHIND the primary partition.
However, my point stays!
Once the user can choose whether he wants to handle the Extended Partition stuff himself, surprises like this would no longer occur! Since one can actively see what's going on.
But at any rate: thanks again.
- Log in to post comments