Question SSD size issue after -k1 option Clonezilla

Nov 7, 2021
3
0
10
I am trying to migrate my Windows 10 old 2To 5400rpm to a new 4To SSD. I tried multiple solutions in order to finally get only one 4To part on the new SSD (and not 2To + 2To, due to cloning method). I ended up by :
  1. Converting my MBR partition to GPT using MBR2GPT tool. Succeeded.
  2. Cloning the disk with Clonezilla, with -k1 and -r options, as they should do the trick, following the documentation.
When finally booting on the SSD, here is what happens :
  • Disk manager sees a 4To partition, which is great
  • Diskpart also recognizes a 4To partition, cool
  • But Windows 10 (i.e.: When right clicking on the disk, and choosing properties) only recognizes a 2To partition.
So...it seems something is wrong with disk offsets, cluster sizes or something. I already tried to process a chkdsk /f /r on it. It did not have any effects. Any idea about how to fix it? (except recloning with another SW, of course). Thanks in advance!
 
Welcome to the forums, newcomer!

Why not just reinstall the OS anew on the SSD? You can easily create you bootable USB installer using Windows Media Creation Tools and once your OS has finished installation, you can migrate your critical data onto the new SSD.
 
Hi and thanks! As this Windows install has tons of software already installed since many years, I'm afraid if making a new W10 install, I'll have to reinstall everything 🙁 As I am not sure I even kept installer files, and as it would take some weeks, I'd prefer to avoid that!
 
I found a solution : ran Diskpart, selected the volume, and executed the command "extend filesystem" (The "extend" function returned an incorrect parameter error). Have no precision about what this command exactly does...