Easeus partition master is taking ages to allocate space

Quvonchbek

I have Aspire 3 A315-55G-50YV. I wanted to allocate 100gb space from D to C and I used Easeus partition master. Everything seemed to be completed in the beginning but the following has been on the screen for more than 26 hours!: "EaseUs partition master boot mode operation
The batch operations are processed completely!
Wait a second please, Rebooting system..."
Is allocating 100gb space that hard or is there something else?

aphanic

I think this would be better suited for the EaseUS forums maybe? If they have such a thing that is. Mostly because people over here may not have any idea of how that program works (I'd be included in that group), so you wouldn't get an appropriate reply.

But! I do know something about resizing partitions and it involves quite some steps:

1. You (or the program you use rather) have to make sure the data that is currently in the partition will still fit after you shrink it, otherwise it's a no-no right off the bat.
2. Then you need to know where you want to get the free space from, i.e. at the front or at the back of the partition.
3. Let's follow your example and say you want to take 100 GB from the beginning of D, so we're to shrink D by 100 GB first to get the free space. Now you'd need to move any data that is located at those first 100 GB of D out of there and to a different location, handling the metadata of the filesystem appropriately. This operation can be costly (in time), specially if the disk in question employs SMR you'll bring it to a crawl speed with all that copying. I bet here is where that program was stuck most of the time.
4. Once that is done you'd have [ C ] [ 100 GB unallocated ] [ D ], the next step is resize that C partition to use those 100 GB of unallocated space which is rather easy.

So yep, changing partition tables in mechanical hard drives isn't trivial and can take quite some time.

It's easier if you want to shrink a partition taking space from its end, because it's far more likely to find that area without data (or important structures like the $MFT mirror of NTFS partitions) so maybe you find yourself in a situation where you don't even need to move data around in the disk. I'm surprised it took that long, but I have no idea the kind of this it was, if it was damaged or not, nor how EaseUS does things.

aphanic

I think this would be better suited for the EaseUS forums maybe? If they have such a thing that is. Mostly because people over here may not have any idea of how that program works (I'd be included in that group), so you wouldn't get an appropriate reply.

But! I do know something about resizing partitions and it involves quite some steps:

1. You (or the program you use rather) have to make sure the data that is currently in the partition will still fit after you shrink it, otherwise it's a no-no right off the bat.
2. Then you need to know where you want to get the free space from, i.e. at the front or at the back of the partition.
3. Let's follow your example and say you want to take 100 GB from the beginning of D, so we're to shrink D by 100 GB first to get the free space. Now you'd need to move any data that is located at those first 100 GB of D out of there and to a different location, handling the metadata of the filesystem appropriately. This operation can be costly (in time), specially if the disk in question employs SMR you'll bring it to a crawl speed with all that copying. I bet here is where that program was stuck most of the time.
4. Once that is done you'd have [ C ] [ 100 GB unallocated ] [ D ], the next step is resize that C partition to use those 100 GB of unallocated space which is rather easy.

So yep, changing partition tables in mechanical hard drives isn't trivial and can take quite some time.

It's easier if you want to shrink a partition taking space from its end, because it's far more likely to find that area without data (or important structures like the $MFT mirror of NTFS partitions) so maybe you find yourself in a situation where you don't even need to move data around in the disk. I'm surprised it took that long, but I have no idea the kind of this it was, if it was damaged or not, nor how EaseUS does things.