Skip to main content

Re-sizing C drive

Thread needs solution

My desktop runs Windows 7 Home premium sp1, and it has several physical hard drives attached, all of them with some logical dives on them. One HDD supports the C drive, and a (logical) workspace drive. Originally, the space split between them was 50Gb for C, and 100Gb for the workspace. Because of the steady bloat of Windows (despite regular clean-ups), I decided to re-allocate the space to be 70Gb for C and 80Gb for the workspace using DD11 (Home update 2 build 11.0.2343).

Re-sizing the workspace - taking 20 Gb from the from of it (planned to add this to the rear of C) worked OK. The next step - re-sizing C - is a problem. Twice I have set this up as shown in the attached screen image (dd11 resize C), to increase the size of C to include the unallocated space between the end of C and the start of the workspace, and twice it fails, leaving the disk allocation unchanged as a result of the operation - see 2nd screen image (dd11 resize c unchanged).

The failure process follows thus
1. committing the action generates a screen that says as part of step 2 of 2, actions require a re-boot, OK. OK'd
2. the re-boot runs. No further DD11 display, no apparent windows messages, and eventually the boot cycle settles.
3. checking the space allocations with both windows explorer and DD11, shows the resize operation has changed nothing - the space allocated is as before the operation started - with 20gb of unallocated space between C and the workspace.

Why did the re-size operation fail?

David

Attachment Size
dd11_resize_c.jpg 311.56 KB
dd_11_resize_c_unchanged.jpg 284.33 KB
0 Users found this helpful

David:

When DiskDirector reboots the PC, Windows is not running and the PC reboots into a minimal Linux-based operating system. Apparently, there is no driver support for some of your hardware in this minimal OS, so nothing happens.

I never like doing operations that require a reboot this way because there is no feedback from the minimal OS to Windows, so it's like "flying blind". A preferred method is to use the Bootable Media Builder application to make a recovery CD or USB flash drive. Then boot the PC from the recovery tool, where you will have feedback and will be able to see what's going on.

In your particular case you may find that the boot environment doesn't see your hard disk. Potential solutions are:

1. Check your account on the Acronis web site to see if a newer bootable recovery version is available, then use that instead.

2. Or, much simpler, since you now have unallocated space following your C partition, use Windows Disk Management console to extend the C volume. That should complete your resize operation.

Hi Mark,

Thanks for the reply.

The windows disk management console in control panel worked just fine . . . click, click, blink and its done. Issue fixed.

On a related note, I had the notify me when new comments posted box ticked, but there was no notice: I was watching for it. I just checked the post by chance, and saw your reply.

Cheers,

David

David:

Glad that worked out for you.

I am faced, I think with a similar problem in Windows 10.  I'm in the process of moving to a new computer which came from the manufacturer with an @ 1TB hard drive, Disk0, partitioned into five (5) parts:  1st an @ 800MB "Recovery Partion" - no drive letter assigned; 2nd a 260MB "Healthy EFI System Partition; 3rd a 150 Gig "Windows (C:)" drive partion; 4th a 762Gig "Data (D:)" partition and last, an 18.47Gig (Recovery Partition) 

I am trying to enlarge the 150Gig C:\ partition by first "shrinking" D:\ by @ 100Gig's or so, but, . . .  when I do this, in Windows 10's Disk Manager, the now "unallocated" 100Gig area taken from D: comes from the area to the right of the disk partition Diagram, and is not contiguous to the active primary C: drive\partition that I'm trying to enlarge. 

800MB-Recovery ][ 260MB-EFISystem  ][  150Gig NTFS Windows C:\ Boot-PageFile etc.  ][ 761.88Gig NTFS Data (D:\)  ][ 18.47 GB Recovery becomes: 

800MB-Recovery ][ 260MB-EFISystem  ][  150Gig NTFS Windows C:\ Boot-PageFile etc.  ][ @600Gig NTFS Data (D:\)  ][ 150Gig Unallocated ?? ][ 18.47 GB Recovery  

and the Windows 10 Disk Manager is not able as far as I can tell to attached and expand C:\ to the non-contiguous unallocated 150Gig of space. 

I believe I recall from the past, say Acronis TI 2011 or 2010, there were disk tools included or abailable as part of an add-on pack to allow the movement and readjustment of non contiguous partitions?  Can this still be done with Acronis TI 2015 or 2016? 

I am faced, I think with a similar problem in Windows 10.  I'm in the process of moving to a new computer which came from the manufacturer with an @ 1TB hard drive, Disk0, partitioned into five (5) parts:  1st an @ 800MB "Recovery Partion" - no drive letter assigned; 2nd a 260MB "Healthy EFI System Partition; 3rd a 150 Gig "Windows (C:)" drive partion; 4th a 762Gig "Data (D:)" partition and last, an 18.47Gig (Recovery Partition) 

I am trying to enlarge the 150Gig C:\ partition by first "shrinking" D:\ by @ 100Gig's or so, but, . . .  when I do this, in Windows 10's Disk Manager, the now "unallocated" 100Gig area taken from D: comes from the area to the right of the disk partition Diagram, and is not contiguous to the active primary C: drive\partition that I'm trying to enlarge. 

800MB-Recovery ][ 260MB-EFISystem  ][  150Gig NTFS Windows C:\ Boot-PageFile etc.  ][ 761.88Gig NTFS Data (D:\)  ][ 18.47 GB Recovery becomes: 

800MB-Recovery ][ 260MB-EFISystem  ][  150Gig NTFS Windows C:\ Boot-PageFile etc.  ][ @600Gig NTFS Data (D:\)  ][ 150Gig Unallocated ?? ][ 18.47 GB Recovery  

and the Windows 10 Disk Manager is not able as far as I can tell to attached and expand C:\ to the non-contiguous unallocated 150Gig of space. 

I believe I recall from the past, say Acronis TI 2011 or 2010, there were disk tools included or abailable as part of an add-on pack to allow the movement and readjustment of non contiguous partitions?  Can this still be done with Acronis TI 2015 or 2016? 

Michael:

The built-in tools in TrueImage are insufficient to do what you need. However, if you have Acronis Disk Director 12 or other partitioning software you can do this as follows:

1. Resize D: by moving its contents to the right so that you end up with 600 GB at the end of the partition and 150 GB unallocated space to the left of the partition. This might take a while since all of the data on D: has to be moved.
2. Resize C: to incorporate the unallocated space into the C: partition. This operation will go quickly.

If you don't have Disk Director 12 then you can use Windows Disk Management to do this:

1. Copy all of your data on drive D: to an external disk.
2. Delete the D: partition, leaving a large block of unallocated space to the right of the C: partition.
3. Extend the C: partition by 150 GB.
4. Create a new D: partition from the remaining unallocated space and format it (quick format).
5. Copy your data back onto the D: partition.