Cloned drive wrong size

[BO Terry]

I have a client computer that I upgraded to an SSD drive today. After cloning, I put the new SSD in the computer and it booted fine. No more disk running 100% etc. I uninstalled Office 365 since they don't use it and shut down the computer. When it came back up, it had a BSOD (error code: 0xc000000f / stop code: Memory management). I eventually got it going again using a W10 disc and running startup repair.

I was checking everything over and just noticed that the drive size is showing as the original size (1TB) instead of reflecting the SSD size of 480 GB. What should I do about this?

Computer: HP 24-g012 All in One running W10
Clone device: Kanguru 1-to-1 duplicator

 

[lcoughey]

So you did a sector by sector copy of 1/2 the source. I hope you still have it, because any data after the 480GB mark was left behind.

 

[glennd]

I have a client computer that I upgraded to an SSD drive today. After cloning, I put the new SSD in the computer and it booted fine. No more disk running 100% etc. I uninstalled Office 365 since they don't use it and shut down the computer. When it came back up, it had a BSOD (error code: 0xc000000f / stop code: Memory management). I eventually got it going again using a W10 disc and running startup repair.

I was checking everything over and just noticed that the drive size is showing as the original size (1TB) instead of reflecting the SSD size of 480 GB. What should I do about this?

Computer: HP 24-g012 All in One running W10
Clone device: Kanguru 1-to-1 duplicator

It would seem the Kanguru is not perfect at downsizing.

 

[BO Terry]

So you did a sector by sector copy of 1/2 the source. I hope you still have it, because any data after the 480GB mark was left behind.

The device manages the process and was done under "resize copy". With this solution, your only work is to connect the drives and select the function (full copy, resize copy etc). I have looked and it appears that all of the data is there, it just didn't manage the partition. I've never seen a drive show a partition size larger than it's actual capacity.

 

[BO Terry]

It would seem the Kanguru is not perfect at downsizing.

I have been using them for several years. Occasionally they just fail (because the source has issues) but this one is a first. Downsizing is probably 75% of what I use it for and that part has never failed before this one.

 

[BO Terry]

I have been using them for several years. Occasionally they just fail (because the source has issues) but this one is a first. Downsizing is probably 75% of what I use it for and that part has never failed before this one.

 

[frase]

I use Macrium Reflect for this purpose - trims the fat so to speak.

 

[backwoodsman]

I was checking everything over and just noticed that the drive size is showing as the original size (1TB) instead of reflecting the SSD size of 480 GB. What should I do about this?

I would fire up Gparted (or your favorite partition editor) and edit the partition size. That should take care of it, but you may have to run Startup Repair again if it doesn't boot.

 

[Alexey]

I would back it up, nuke, and then restore from backup. If I had an original, I would back up the original, and do a restore onto the target. In the current state, there is no guarantee (and no easy way to obtain a guarantee) that partition table is the only issue. There are plenty issues which are theoretically possible when a filesystem resize goes wrong.

 

[GTP]

I would back it up, nuke, and then restore from backup. If I had an original, I would back up the original, and do a restore onto the target. In the current state, there is no guarantee (and no easy way to obtain a guarantee) that partition table is the only issue. There are plenty issues which are theoretically possible when a filesystem resize goes wrong.

This ^^^^

Welcome back? @Alexey

 

[Alexey]

Welcome back? @Alexey

Yeah thanks.

 

[Big Jim]

We normally use macrium, but 2 days ago macrium failed due to cyclic redundancy error.
So I thought as the machine still boots, what the hell I'll try windows backup.
I backed up the drive and then used a W10 installation USB stick to enter recovery environment and then restored the machine to a new SSD using the backup image I had just taken.
And it worked.

I can't honestly remember if it was a smaller SSD than the original install though, worth a try at least if the machine is booting.