PS3 PS3 Missing Free Space after System Format

JSnakeRepair

Forum Noob
Now, I know what you are thinking and my problem is slightly different. I am aware of overprovisioning, max readable size, and System Reserved space.

I am running latest Evil Nat 4.92 on a CECH-2001A with a 1TB SSD. I am just trying to back up my disc library using MultiMan and whenever I try to delete an ISO after transferring it my system freezes, 'deletes' the files, and frees up some space. I am having to reformat my drive every time I want to delete the dumped ISO's, and noticed that my PS3 is showing only 808GB / 931GB. The usual starting point is closer to 828GB. Even after using the HDD Unlock Space Tool that number climbs to just 869GB / 931GB...still short of the typical 890GB metric.

I have nothing installed but this tiny HDD Tool and MultiMan...where could this other 20GB be going?
 
931GB = ~867GiB
And minus 10% of that space (or 2% if HDD Unlock will be used) is reserved in UFS2. Minus 256MiB for VFLASH region. Minus 2GiB for CACHE region. And then ultimately you will get what default free space for your case should be.

Like all operating systems, it counts by 1024, not 1000 but like many, displaying as for 1000. So while it shows GB, it is GiB in reality.

SSDs overprovisioning is something different than you thinking. That 931GB is after cutting of the space, not total space. As user, You never know how large SSD is in reality until you count all chips size together based on their model designation.

And BTW: your SSD it seems incompatible because it corrupting filesystem. Based on your description.
 
931GB = ~867GiB
And minus 10% of that space (or 2% if HDD Unlock will be used) is reserved in UFS2. Minus 256MiB for VFLASH region. Minus 2GiB for CACHE region. And then ultimately you will get what default free space for your case should be.

Like all operating systems, it counts by 1024, not 1000 but like many, displaying as for 1000. So while it shows GB, it is GiB in reality.

SSDs overprovisioning is something different than you thinking. That 931GB is after cutting of the space, not total space. As user, You never know how large SSD is in reality until you count all chips size together based on their model designation.

And BTW: your SSD it seems incompatible because it corrupting filesystem. Based on your description.
That's an interesting note on SSD. It's the 860 Evo; don't really think it is to blame, but something seems to be amiss.

Otherwise...my question was not really answered. Most people have 828GB free after installing a new 1TB SSD, and that number climbs to 890 after using the tool. I have about 20GB less than what others are getting in both scenarios...why is that?

Again...I am aware that I should not expect to see 1000GB or 1024GB of total space available, nor should my free space ever match my total space.
 
But I answered. I told you difference between units used by OS and by media advertising. And I told you what and how much taking space. So then you can just take target storage space exposed to user and do the math. ;)
 
But I answered. I told you difference between units used by OS and by media advertising. And I told you what and how much taking space. So then you can just take target storage space exposed to user and do the math. ;)
I feel I have been quite clear, yet apparently not clear enough. Let's use photos then...

Picture A: A different user with a newly formatted 1TB drive running CFW
TOTAL SPACE: 931GB
FREE SPACE: 827GB

Picture B: Myself with a newly formatted 1TB drive running CFW
TOTAL SPACE: 931GB
FREE SPACE: 808GB

Picture C: A basic Google AI response indicating 827GB - 837GB is typical for a fresh drive

827 - 808 = 19GB

Why might my PS3 be showing almost 20GB less free space than the average newly PS3-formatted 1TB drive with the same total space available?
 
We don't know the HDD model used on Picture A, so it can't be compared properly.

Also, Picture A uses CFW 4.88 while Picture B uses CFW 4.92.

All of this renders the comparison deceiving, erroneous and useless to make up conclusions.
 
We don't know if he not removed data via file manager or FTP before the screenshot making, and system did filesystem sync. Which is broken in all homebrew since fw ~4.4x+ and many ppl thinking that they deleted something but in reality, space wasn't freed yet.

Second: CellOS not supporting drives with 4K sectors without emulation level (so called 512e). In that case, it will count space wrong and sooner or later, user experience data loss due to damages made by writing to UFS partition.
 
Back
Top