TI restores partition to different block of unallocated space?!
Confused...
W7 64 bit.
Partitions in order:
System (primary)
OS (primary)
Extended partition next with 3 logical partitions and a large block of unallocated space at the end
I made a full disk backup (TI2011 latest build as of yesterday).
I tried to restore the OS partition. After it started, I cancelled. This left an unallocated block between the System and Extended partitions.
I started to restore the OS partition again. I selected the unallocated space between the System and Extended partition.
Surprise: TI shrunk the Extended partition so that the unallocated space was now OUTSIDE of the extended partition. The restored partition was placed AFTER the end of the extended partition:
System
Unallocated (where OS used to be)
Extended with 3 logical partitions and NO unallocated space
OS (primary)
Unallocated
I tried it again - selecting the ORIGINAL unallocated space... but TI used more of the unallocated space at the end of the drive. And I tried it again trying to figure out what was going on, resulting in:
System (primary)
Unallocated (where OS used to be)
Extended with 3 logical partitions and NO unallocated space
OS (primary)
OS (primary)
OS (primary)
Unallocated
Booting into W7 (I needed to repair first), Disk Management shows me that there are now 4 primary partitions AND and an extended partition - which is surprising to me since the drive is using MBR and formatted with simple/Basic partitions (i.e. maximum should be 3 primary and 1 extended in my case)!!
OK - now the remaining unallocated space at the end of the drive is LESS than the size of the OS partition. SO I tried again to restore. I saw that TI wanted to restore as a logical partition, so I selected "Primary" as the type instead. However, when I went back into W7 after the restore, I see that the Extended partition now included the OS partition that was just restored?! (i.e. the extended partition had grown to include the unallocated space to the LEFT of the extended partition)
System (primary)
Extended with 4 logical partitions and NO unallocated space; the 1st of the logical partitions is the most recent OS restore.
OS (primary)
OS (primary)
OS (primary)
Unallocated
HOW do I control what TI does with the partitions?
e.g.
1) How do I get TI to use the unallocated block that I CHOSE instead of using another unallocated block without even advising me?
2) How do I prevent TI from shrinking an extended partition?
3) How do I prevent TI from GROWING the extended partition to include unallocated space? How do I get TI to restore a partition as PRIMARY instead of logical when I tell it to do so.
4) How do I get TI to do the things it did when I WANT it to do it (e.g. to shrink or grow an extended partition)
In addition to TI doing something I found unexpected, I am distressed that there was no ACKNOWLEDGMENT that TI was doing any of these things.
I sure hope someone can help me understand this - I don't seem to be finding posts / articles that address what I just experienced.
Thanks -
- Accedi per poter commentare
Thanks for your suggestion. I have recovered the disk as you suggested.
I am still curious as to why TI behaved in the manner I described.
I would appreciate if anyone can help answer my original questions.
Thanks-
- Accedi per poter commentare
I found this link that suggests I cannot rely upon W7 Disk Management as always reporting CORRECTLY, e.g. how I could have more than 3 primary partitions with 1 extended partition: http://www.multibooters.co.uk/quirks.html#several_primaries
Any confirmations on this? Anyone else have thoughts on my questions?
- Accedi per poter commentare
Sam,
Once you cancelled the restore, everything normal changed. Normally, the first thing TrueImage does when restoring is to delete the partition being replaced. So after the cancellation, the program has no clue as to what you want to do and totally relies on the user to make the proper choices as to where to put what and user makes the choice as to logical or primary, etc.
There is probably an explanation as to what happened if there were a snapshot in time at that particular moment--so we can only surmise.
As you found out, once a restore or clone begins, there is no cancellation possible and retain anything normal.
The chances of Windows Disk Management showing wrong type partitions is possible but highly unlikely in this situation. It is possible to have multiple logical partitions inside an extended partition but this is usually by an experienced individual with multi boot situations--not the average user.
I don't know whether my explanation has made the situation any clearer but once the procedure was interrupted, recovery procedure is totally in the hands of the user. The best chance for a successful recovery is to start over--which you did. Because the disk was messed up, it is best to clear the disk of partitions and start with a completely unallocated disk--which can be accomplished using the TrueImage Add disk option. TrueImage can handle a restore overtop an existing identical disk and can also handle a restore to a blank unallocated disk.
I am no expert in this situation but the cancellation of restore made your situation totally abnormal.
- Accedi per poter commentare
Thanks - much appreciated. I think I will try the steps again by first deleting the OS partition and then restore to the unallocated space released by the OS delete; if everything works fine this time, this will confirm that it was the cancelled restore that left my disk in an abnormal state resulting in future abnormal results.
Me, I would expect that since TI gives me the option to cancel that it will "clean up" after itself and not leave my partition info in an abnormal state. I would expect this type of "abnormality" if I did a hard boot during the restore process; I would NOT expect it from an orderly "cancel" where TI has the opportunity to return the sectors occupied by the original partition back to unallocated space (as it SEEMED to have done).
If my expectation is unreasonable, I would be grateful for an explanation of why. Thanks again.
- Accedi per poter commentare