Drive getting full but wierd set up

[ICIT2LOL]

I knew my SanDisk SSD was getting a tad full and checked it only to find this in the the pics. I have no idea how the two small partition came about and was wondering if I could clear one and make a tad more space for myself (waiting on a new SSD -256GB) in the meantime.

The other thing is I know some space is lost in the drive control stuff or whatever but 8GB seems to be excessive??

Can anyone give me a few pointers please??

 

[Kaktussoft]

E and G have only "$recycle.bin" (recycle bin) and system volume information (restore points info). any other hidden folders/files on E and G? If not..... why not delete partition E and G? They are very small anyway and don't give you much extra space.

 

[ICIT2LOL]

Not that I am aware of K it just seemed odd I had two with exactly the same content and vastly different sized partitions - certainly sizes I would never have set then at anyway.
I know I won't gain much space my beef was with the 8GB that has bee used for ?something? like I said I know a small amount is used by the drive itself but that amount looks excessive unless the drive has a lot of control software on board.

 

[Kaktussoft]

the 8GB that has bee used for ?something?

Did you lost 8GB of drive space? I can't see any loss in the screenshots. Please explain

 

[ICIT2LOL]

Ok in the screenshot it shows in properties 119GB give or take and yet in the Partition Wizard partition pic it shows only 111GB and that partition is just about full.
I also pulled up DISKPART to see what if any there was a difference.

 

[Kaktussoft]

Diskpart screenshot doesn't show the free space on C.

 

[ICIT2LOL]

Yep that's what I mean just where is the 8GB or thereabouts gone to?? The only explanation is in my limited knowledge is that perhaps one of the chips that go to make up the SSD is dead and therefore not showing because it is odd it is very close to what space one would expect to be on a chip in one of these devices - what do you think?
IE 120GB divided by 8GB = 15 chips (thereabouts) maybe one is dead and it is operating on 14 chips or if the equation turns out to be 14 chips then it might be down to 13 chips??
I don't know of any test that could confirm that so I suppose I shall never know without some sort of specialized equipment.

 

[Kaktussoft]

Sorry... still don't understand. Why do you think there should be 8GB more?? Which screenshot shows 8GB less?

 

[whs]

This looks like a 120GB usable bytes drive. The 111GB in binary corresponds to 120GB in decimal. The SSDs always have space set aside to replace defective areas.

 

[TVeblen]

WHS is right. Hard drive manufacturers have always sold drives (Spinners and SSD) by taking the total number of bytes contained and dividing by a decimal number.
So your drive contains 120,000,000,000 bytes. They divide that by 1 billion to arrive at the Gigabytes slapped on the label.

But in binary a Gigabyte actually measures 1,073,741,824 bytes. So to the OS there are only (roughly) 120 divided by 1.074 or 111.7 GB on the drive.

When Windows initializes/partitions/formats a hard disk it always leaves a small amount of space, usually 7MB or so, at the front and sometimes the rear of the volume to use for it's own file purposes (like creating Dynamic Disks). Windows always ignores these spaces. You will not see them in any Windows based utility.

Linux (PW is a linux based program) always sees these small spaces left by Windows as unallocated space. But it does not normally see them as partitions with drive letters. That is weird.

And the 340MB "partition" it sees is odd in a couple of respects. A EFI System partition is normally 100MB. A Windows System Reserved partition is usually 100 - 200 MB. So even if PW was seeing one of these special partitions as a Drive it would not explain the size.

You might want to make an image of the entire drive using a Linux based program before you start deleting the partitions. If you don't know how they were created it is possible they were always there.