Question Partitioning an SSD for cloned copy install ?

[brucepascal]

OS: Windows 11

I am using Hasleo clone, and after any clean install, I make a copy on a small spare SSD. I know needed to install this clone on a large Samsung 850 512GB.
It works fine, except... it works only on 128 GB of the new disks where the clone is installed, and I have 346 GB of unallocated space. How can I connect this partition, or rather how do I join this partition to my Healthy Boot partition of only118 GB

It looks like this: https://ibb.co/zT1szPt8


(Disk 1, Volume D, is just for storage)

 

[USAFRet]

You need to Delete the 837MB partition in the middle.
Then, you can Extend the C partition into the remaining space.

But I'm a bit unclear on how you got here.

Clean install.
Then copy to the small SSD.
Then clone from that small SSD to the desired large target?

Why not just do the original clean install on the 512GB Samsung?

 

[USAFRet]

Or, use a different clone tool that lets you manipulate the partition sizes on the target drive.
Macrium Reflect does this.

 

[brucepascal]

You need to Delete the 837MB partition in the middle.
Then, you can Extend the C partition into the remaining space.

But I'm a bit unclear on how you got here.

Clean install.
Then copy to the small SSD.
Then clone from that small SSD to the desired large target?

Why not just do the original clean install on the 512GB Samsung?

You misunderstand a bit, but it does not matter . The 837MB is a recovery partition which I rally do not need,

HOW do I get rid off it?

 

[brucepascal]

Hey USAFRet...

You did it without doing a thing. I tried diskpart and cmd... and then there was only left to extend the partition... So, thanks !

 

[SkyNetRising]

I tried diskpart and cmd... and then there was only left to extend the partition... So, thanks !

BTW - your EFI System partition is way too small (35MB).
Recommended size is 350MB to 500MB.

Some future windows update may fail (and leave your pc unbootable) because of efi partition being so small.

 

[brucepascal]

BTW - your EFI System partition is way too small (35MB).
Recommended size is 350MB to 500MB.

Some future windows update may fail (and leave your pc unbootable) because of efi partition being so small.

Thank you I never noticed, so I checked and... no raction to either left or right-click, and Diskmanagement tells me it is empty!

 

[SkyNetRising]

so I checked and... no raction to either left or right-click, and Diskmanagement tells me it is empty!

It's not empty. It contains bootloader.
You simply can't view the contents.
And Disk Management is unable to see partition usage.

 

[brucepascal]

It's not empty. It contains bootloader.
You simply can't view the contents.
And Disk Management is unable to see partition usage.

Thank you.
It says zero content, but I hope you are correct, because then I would not have too much to worry about.
If I right-click or left-click on that partition, the context menu that opens has all options greyed out, except "Close". How can I make it bigger?

 

[SkyNetRising]

If I right-click or left-click on that partition, the context menu that opens has all options greyed out, except "Close". How can I make it bigger?

Currently it's not possible to make it bigger.
You'd have to boot from windows installation media into command prompt (press Shift+F10 , to open command prompt).
and use diskpart to:

delete old 35MB efi partition;​

shrink large OS partition (should be 465GB now after you extended it previously), shrink it by 500MB;​

create a new 500MB efi partition;​

format it to fat32;​

assign letter H: to new partition​

use bcdboot command to install bootloader files on it.

Commands would look like this:

diskpart​

list disk​

select disk x​

(select 465GB disk, x=0 or x=1, replace x with appropriate number)​

list partition​

select partition 1​

(select 35MB efi partition)​

delete partition override​

list partition​

select partition x​

(select large OS partition 456GB, x=2 or x=3, replace x with appropriate number)​

shrink desired=500​

create partition efi size=500​

format fs=fat32 quick​

assign letter=H​

list volume​

(note drive letter for large OS partition 465GB, it can be other than C: in installation environment)​

exit​

bcdboot C:\windows /s H: /f UEFI​

(replace C: with appropriate letter for windows OS 465GB partition)​

​

If you get any errors, then stop immediately and show screenshots.
(upload to imgur.com and post link)

Keep in mind - after old efi partition is deleted your system is unbootable
until you have executed all commands properly.

 

[Misgar]

It looks like this: https://ibb.co/zT1szPt8

In this situation, I use EaseUS Partition Master to move the Recovery partition to the end of the disk (without changing its size). After actioning the move, I close EaseUS, open Microsoft Disk Management and extend the C: drive into the new empty space, revealed by moving the Recovery partition. The whole process takes less than 3 minutes.
https://www.easeus.com/partition-manager/

As usual, it's a good idea to backup all important data to another system, in case you make a complete mess of things.

As @USAFRet suggests, I use Macrium Reflect to clone disks using "drag and drop" to place each partition in turn on the destination drive, then "move and resize" to push partitions to the end of the disk and increase/reduce partition sizes, as dictated by the new drive's capacity. This avoids having to use EaseUS Partition Master after cloning.


The other good thing about EaseUS is you can see (and delete) the hidden 16MB GPT partition on some (non MBR) disks that Microsoft Disk Management might not reveal.

 

[brucepascal]

This is what EaseUs finds now.... How can this work without any problem at all, if these two pictures show, there is nothing there?


https://ibb.co/1tW93zBc

EFI-2 hosted at ImgBB

Image EFI-2 hosted in ImgBB

ibb.co

 

[USAFRet]

This is what EaseUs finds now.... How can this work without any problem at all, if these two pictures show, there is nothing there?

Show us Disk Management instead.

 

[brucepascal]

You already saw it, it is in the first post...
But as this is a big mess, I think it is better I repeat the cloning process, and FIRST find out exactly how do it properly...

This is the Diskmgmt of this SSD which want to clone to the Samsung SSD which is twice as big.

https://ibb.co/Rx407gD

How do I prepare the Samsung, so the partitions will be as they should be?

Thank you all...

 

[SkyNetRising]

How do I prepare the Samsung, so the partitions will be as they should be?

So your clone source has an 100MB EFI system partition.
Resulting clone has 35MB EFI system partition.
Obviously - cloning software allowed you to change partition sizes.

Just redo clone and adjust clone target partition sizes in cloning software.
Set EFI system partition to 350MB-500MB, set OS partition to 465GB.

 

[USAFRet]

You already saw it, it is in the first post...
But as this is a big mess, I think it is better I repeat the cloning process, and FIRST find out exactly how do it properly...

This is the Diskmgmt of this SSD which want to clone to the Samsung SSD which is twice as big.

https://ibb.co/Rx407gD

How do I prepare the Samsung, so the partitions will be as they should be?

Thank you all...

To redo the clone....

-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Both drives must be the same partitioning scheme, either MBR or GPT
Download and install Macrium Reflect (or Samsung Magician (which includes Data Migration), if a Samsung target SSD)
If you are cloning from a SATA drive to PCIe/NVMe, you may need to install the relevant driver for this new NVMe/PCIe drive.
Power off
Disconnect ALL drives except the current C and the new SSD
Power up

Verify the system boots with ONLY the current "C drive" connected.
If not, we have to fix that first.

Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive

[Ignore this section if using the SDM. It does this automatically]
If you are going from a smaller drive to a larger, by default, the target partition size will be the same as the Source. You probably don't want that
You can manipulate the size of the partitions on the target (larger)drive
Click on "Cloned Partition Properties", and you can specify the resulting partition size, to even include the whole thing
[/end ignore]

Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD. This is not optional.
This is to allow the system to try to boot from ONLY the SSD

(swapping cables is irrelevant with NVMe drives, but DO disconnect the old drive for this next part)
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe all partitions on it.
This will probably require the commandline diskpart function, and the clean command.

Ask questions if anything is unclear.
-----------------------------

 

[brucepascal]

So your clone source has an 100MB EFI system partition.
Resulting clone has 35MB EFI system partition.
Obviously - cloning software allowed you to change partition sizes.

Just redo clone and adjust clone target partition sizes in cloning software.
Set EFI system partition to 350MB-500MB, set OS partition to 465GB.

Thank you, but the point is:
"Obviously - cloning software allowed you to change partition sizes."

It did not allow me, it DID it. I may not have done something I should have....
And so my question is why did Hasleo do that in the first place, and, the real question how do get to the correct partition on the new disk installation?

 

[USAFRet]

and, the real question how do get to the correct partition on the new disk installation?

As noted above, Macrium Reflect lets you manage the resulting partition sizes on the target drive.

 

[brucepascal]

To redo the clone....

-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Both drives must be the same partitioning scheme, either MBR or GPT
Download and install Macrium Reflect (or Samsung Magician (which includes Data Migration), if a Samsung target SSD)
If you are cloning from a SATA drive to PCIe/NVMe, you may need to install the relevant driver for this new NVMe/PCIe drive.
Power off
Disconnect ALL drives except the current C and the new SSD
Power up

Verify the system boots with ONLY the current "C drive" connected.
If not, we have to fix that first.

Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive

[Ignore this section if using the SDM. It does this automatically]
If you are going from a smaller drive to a larger, by default, the target partition size will be the same as the Source. You probably don't want that
You can manipulate the size of the partitions on the target (larger)drive
Click on "Cloned Partition Properties", and you can specify the resulting partition size, to even include the whole thing
[/end ignore]

Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD. This is not optional.
This is to allow the system to try to boot from ONLY the SSD

(swapping cables is irrelevant with NVMe drives, but DO disconnect the old drive for this next part)
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe all partitions on it.
This will probably require the commandline diskpart function, and the clean command.

Ask questions if anything is unclear.
-----------------------------

Thank you, but the only thing I did not already know, and did do, is that Samsung Magician is also for cloning? that would be perfect.
Why did Hasleo, which has worked fine a few times, has chnaged the partitions this time?

 

[brucepascal]

As noted above, Macrium Reflect lets you manage the resulting partition sizes on the target drive.

Thank you again, but how will I know what the right sizes are?

 

[USAFRet]

Thank you, but the only thing I did not already know, and did do, is that Samsung Magician is also for cloning? that would be perfect.
Why did Hasleo, which has worked fine a few times, has chnaged the partitions this time?

In Samsung Magician, there is a "Data Migration" function.
That used to be a separate tool, but has been incorporated into Magician.

But....MAcrium Reflect gives you much more granular control over the resulting partition sizes.
In this case, that is what I would use.

Why did Hasleo do what it did? No idea...I've never used it.

Thank you again, but how will I know what the right sizes are?

For the tiny 35MB EFI partition you have, expand that to 350-500MB.

 

[brucepascal]

In Samsung Magician, there is a "Data Migration" function.
That used to be a separate tool, but has been incorporated into Magician.

But....MAcrium Reflect gives you much more granular control over the resulting partition sizes.
In this case, that is what I would use.

Why did Hasleo do what it did? No idea...I've never used it.


For the tiny 35MB EFI partition you have, expand that to 350-500MB.

My problem is, that I do not want to have control over the partitions, because I have no idea what size they need to be, and where they have to be. I am looking a software that does that for me. When Macrium was free, i used that and the I used Hasleo which both worked perfectly. This is the first time it did not....
On the Samsung, is the "Data Migration" function cloning the WHOLE disk to the new. and empty disk? Both SSDs are Samsung, the source 128GB the receiving on 512GB
Cloning is a lot less work, than expanding the EFI partition, and as far as I found out, a lot of things can go wrong....

 

[USAFRet]

My problem is, that I do not want to have control over the partitions, because I have no idea what size they need to be, and where they have to be. I am looking a software that does that for me. When Macrium was free, i used that and the I used Hasleo which both worked perfectly. This is the first time it did not....
On the Samsung, is the "Data Migration" function cloning the WHOLE disk to the new. and empty disk? Both SSDs are Samsung, the source 128GB the receiving on 512GB
Cloning is a lot less work, than expanding the EFI partition, and as far as I found out, a lot of things can go wrong....

Yes, the Samsung tool does the whole drive to the new target drive.

Try it, see what happens.

If it does not properly expand the EFI partition to a usable size (350MB)...then go with Macrium Reflect, and manage it manually.

 

[brucepascal]

My problem is, that I do not want to have control over the partitions, because I have no idea what size they need to be, and where they have to be. I am looking a software that does that for me. When Macrium was free, i used that and the I used Hasleo which both worked perfectly. This is the first time it did not....
On the Samsung, is the "Data Migration" function cloning the WHOLE disk to the new. and empty disk? Both SSDs are Samsung, the source 128GB the receiving on 512GB
Cloning is a lot less work, than expanding the EFI partition, and as far as I found out, a lot of things can go wrong....

Thank you, I will try. I need to save all my personal data to a storage disk. I will post again, when I am finished with it.

 

[USAFRet]

Thank you, I will try. I need to save all my personal data to a storage disk. I will post again, when I am finished with it.

And you absolutely NEED to do that, before any major operation like cloning to a different drive.
Even with a perfect set of instructions, things can happen.