Windows 10 1809 partitions (mbr)

Discussion in 'backup, imaging & disk mgmt' started by taotoo, Mar 6, 2019.

  1. taotoo

    taotoo Registered Member

    Joined:
    Mar 13, 2013
    Posts:
    450
  2. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    4,004
    Location:
    The Pond - USA
    As far as imaging is concerned, you need the OS partition, the new 839mB (probably a new RECOVERY PARTITION), and your original System Reserved partition (this is the partition that the SYstem BOOTs through to get to the OS). That previous 400+mB partition with only 11mB in use is pretty much useless at this stage. It looks like you'll need to redirect REFLECT to "gather the new 800+mB partition, dump the 463mB one and re-Add the System Reserved one. Your edited DEFINITION file will most likely start with a new FULL at this point.
     
  3. taotoo

    taotoo Registered Member

    Joined:
    Mar 13, 2013
    Posts:
    450
    Thanks - yes Macrium insisted on a new full, and I wanted to avoid this. I was hoping I could delete the new 839mb partition and have it use the old one (then extend the C partition back to it's old size). But according to Macrium the new 839mb has 482mb of data in it, so that obviously won't fit in the old 463mb one (though Disk Manager shows the new 839mb partition as being empty for some reason.
     
  4. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    4,004
    Location:
    The Pond - USA
    As soon as those partitions (C ) change size, their partition ID changes and that causes any imaging System to re-image... after all, it thinks it's a different partition now.

    Windows 10 will do this to you from time to time... it's a real PITA. It carved that new 800+mB Recovery Partition off of the end of your previous OS partition as you noticed. You can probably extend your new Recovery Partition to maybe a coupla gigabytes, that way W10 won't be in such a hurry to create a new one that's big enough for everything it wants the Recovery Partition to do. The whole W10 thing is a crapshoot at times.
     
  5. taotoo

    taotoo Registered Member

    Joined:
    Mar 13, 2013
    Posts:
    450


    Thanks - I guess that means that even if I managed to get the partition layout/sizes back to how they were, Reflect would insist on doing a new full anyway.

    I suppose I could delete the old 463mb partition and extend the new 839mb to the right from the command line, and avoid having to use third party software.
     
  6. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    4,004
    Location:
    The Pond - USA
    Correct on your 1st assumption.

    At 1/4 of 1% gain for that partition... hardly worth the effort, I'd say :)
     
  7. taotoo

    taotoo Registered Member

    Joined:
    Mar 13, 2013
    Posts:
    450
    Actually I was thinking of extending it for the reason you suggested - it looks like it would be about 1.2gb.

    That said I don't even know why it created a new partition in the first place - as I understand it, theoretically it should have just extended the existing one to the left. So maybe next time around it will create another new one anyway...
     
  8. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    4,004
    Location:
    The Pond - USA
    The algorithm it uses is always the same. Rather than decide where the existing Recovery Partition lives and what might be doable in creating a new one of additional size, the easy way out (since it has total control of the OS partition and partition creation while running UNDER the OS) is to just shrink the existing OS partition and carve a new one from the freed up space... a simple decision, really, on the OS's part.

    This whole Recovery Partition re-do since the intro of Win10 has wreaked havoc with any app that manages partitions... the most prominent ones being imaging apps and snapshot apps (Rollback RX and EazFix). Since we have no idea what MicroSloth has planned for the future of Win10 and its "recovery" requirements... be ready :eek:
     
  9. taotoo

    taotoo Registered Member

    Joined:
    Mar 13, 2013
    Posts:
    450
    Ah - I found an old web page with the logic for extending/creating the partitions but it might have been out of date.

    Anyway, Diskpart apparently won't extend recovery partitions which is annoying.
     
  10. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    10,095
    Location:
    NSW, Australia
    taotoo,

    Some suggestions to better use your disk space.

    Slide the System Reserved partition to the end of the Unallocated Free Space
    Delete the 463 MB partition
    Slide the 839 MB partition to the end of the Unallocated Free Space
    Resize the C: partition to remove the Unallocated Free Space

    Your Backup E: partition is almost "full".
    Your Data D: partition only contains 20 GB of files/folders
    Resize the D: partition to 50 GB
    Create a second Backup partition in the roughly 60 GB of Unallocated Free Space on Disk 2
    Move about 50 GB of files/folders from the E: partition to this second Backup partition
     
Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.