Question SSD capacity too small ?

dani56

Distinguished
Jun 18, 2012
10
0
18,510
I have an internal M2 SSD, Kingston KC3000 with 1TB rated capacity.
In Gparted the device shows only size of 954GB .
Is this normal? should be 1024GB or am I wrong ?
 
I have an internal M2 SSD, Kingston KC3000 with 1TB rated capacity.
In Gparted the device shows only size of 954GB .
Is this normal? should be 1024GB or am I wrong ?
That is correct.

You're seeing the difference between marketing and computer.

Binary vs human
Base 2 vs Base 10.
Gigbibytes vs gigabytes.

There is no space lost, nothing is missing.
Just different reporting units.
 
Some other 1TB devices show only 931GB of real space. so If I want to clone the KC3000 into a backup device it will not work with a 931GB 1TB device, right ?
 
Some other 1TB devices show only 931GB of real space. so If I want to clone the KC3000 into a backup device it will not work with a 931GB 1TB device, right ?
Incorrect.

Current clone tools only consider the actual consumed space. Not the full physical drive.

For instance...
A 1TB drive with 350GB consumed, will easily clone into a 500GB drive.

My default clone and backup tool is Macrium Reflect.
 
  • Like
Reactions: CountMike
Let me understand this. The KC3000 shows 953GB of consumed space. so any cloning tool will requires 953GB of free space on the target device. how is this going to succeed if the target device only has 931GB of space ?
 
Let me understand this. The KC3000 shows 953GB of consumed space. so any cloning tool will requires 953GB of free space on the target device. how is this going to succeed if the target device only has 931GB of space ?
No.
As said....the current cloning/imaging tools only consider the actual consumed space.

If your drive had 800GB consumed space, it will happily clone in to some other 1TB/931GB drive.


Older tools like CloneZilla....that physical drive space IS an issue.
It would only clone into same size or larger.
That is long outdated.


Also, "cloning" is not a proper backup procedure.
Cloning is for swapping the physical drive, right now. Not to sore away for later use.
Read into "imaging" instead.

We can go into details on this if you wish.
 
The original KC3000 has the entire space taken up by a ZFS pool. it is ZFS who is managing the free space inside the pool but from the cloning stand point the KC3000 is at 100% utilization.
Seems to me the ZFS pool will not fit into a 931GB drive. So to be on the safe side I should probably get a larger capacity target drive.