PS3 [TUTORIAL] Unlock up to 8% extra total space on the PS3 internal hard drive

Update: picard (a.k.a. 3141card) has released a homebrew app (available here) that changes the reserved space from 8% to 1% automatically. Running the app again will revert the changes.

https://mega.nz/file/zdk1lKqZ#aj4WFdOeosH_ncIB5flNtUxPs341PSYaXdLF2DdA45A

PS3 Unlock HDD Space by picard (aka 3141card)
All credits to einsteinx2 on psx-place.com for his great tutorial:
https://www.psx-place.com/threads/t...l-space-on-the-ps3-internal-hard-drive.20773/

HOWTO:
  • Install the package on your custom firmware PS3 and run it. It finds the active superblock of the gameOS partition and do the necessary patches. Usually 8 percent of the memory is reserved, the app sets this value to 1 percent.
  • The optimization value is set to 1, for minimize disk fragmentation.
  • The changes are permanent. The changed active superblock is written to the HDD with the system fs umount of the gameOS partition.
  • Running the app again restores the original values, if desired.

You use this app at your own risk! I am not responsible for any damage caused to your PS3 system!​

If my PS3 app was useful to you, I would be very happy about a donation :)
https://www.paypal.com/paypalme/3141card

picard (aka 3141card)

-- (Original Post Continued Below) --

Need some extra space on your internal PS3 HDD, if so then perhaps @einsteinx2 may have a genius method for unlocking upto 8% of space on your Internal HDD, while the space is more then likely allocated for performance reasons by Sony (use this guide at your own risk), some of this saved space could be considered overkill, as the creator of this method makes a valid point that some of this saved space on larger HDDs is more then some of the early model PS3 complete HDD size, so its likely some of that space allocation is a bit overkill on the part of Sony. einsteinx21 has provided a great tutorial found below explaining in detail about this recent discovery

-STLcardsWS


depositphotos_10075144-stock-photo-protected-hdd-chain-and-lock.jpg

Unlock up to 8% extra total space on the PS3 internal hard drive


  • The What

    By default, even on custom firmware, the PS3 reserves 8% of your total internal hard drive space. From my searching online, I don't believe anyone has ever successfully unlocked that wasted space, so I decided to give it a shot. Turns out not only is it possible, but it's relatively easy thanks to some existing tools created by the community. This guide will explain how to reclaim that wasted space by manually modifying the metadata of the UFS2 formatted GameOS partition using Linux, as well as the potential cons (primarily performance, though I haven't experienced any performance issues yet myself).

    I believe the pros outweigh the cons though, and have been using this now without issue on my personal PS3 with a 1.5TB drive for a few days now, installing tons of games without a hitch.

    The Why


    While external drives used with the PS3 are all FAT32 formatted (or NTFS if you have CFW), the GameOS partition on the internal hard drive is formatted using the UFS2 filesystem with a layer of encryption on top.

    Like other *nix file systems such as Ext2/3/4, UFS2 can reserve part of the drive's space to only be used by the system or the root user. This is to reduce fragmentation and also prevent the drive from completely filling up, possibly freezing the computer.

    By default, UFS2 reserves 8% of any drive's free space, in this case meaning it can't be used by the PS3 for installing games. This is why when you first install that shiny new 1.5TB hard drive you will see that not only is it only actually 1.36 TB because hard drive manufacturers really love counting in base 10, but you also lose another 111.4 GB.

    Now generally having this reserved space is not a bad thing, however the problem is that as drives grow larger, the amount of wasted space becomes larger than some of the smaller PS3's entire hard drives! Clearly that much isn't needed to prevent fragmentation.

    The tunefs documentation mentions that "the file system's ability to avoid fragmentation will be reduced when the total free space, including the reserve, drops below 15%. As free space approaches zero, throughput can degrade by up to a factor of three over the performance obtained at a 10% threshold." Note that these numbers are already higher than the 8% default that all UFS tools as well as Sony use. Also note that it says as free space drops to 0%, performance may be up to 3 times slower than normal. However, it's unclear whether that only affects newly written--presumably more fragmented files--or all files. It seems like this is a worthy tradeoff, especially since if you do notice any performance issues you can simply delete some games or other data to free up the space. By changing the minimum free space, performance is not changed at all unless you choose to fill the drive completely...but at least you can now make that choice.

    UFS2 supports two write optimization modes: time and space. Time optimization is the default--and is used by the PS3--and allows for faster writes at the expense of potentially higher fragmentation (though generally only as the drive reaches capacity). Since we're allowing ourselves to fill almost the entire drive, these instructions also change the optimization mode to space. That means that the filesystem will spend more time during writes to ensure the files are less fragmented, insinuating that it will shuffle blocks around to make contiguous space.

    The tunefs documentation says that "the file system can either try to minimize the time spent allocating blocks, or it can attempt to minimize the space fragmentation on the disk. Optimization for space has much higher overhead for file writes. The kernel normally changes the preference automatically as the percent fragmentation changes on the filesystem." However, since the PS3 uses a custom operating system and this documentation is from FreeBSD, I think it's best to manually set the space option anyway. I have not noticed any performance degradation so far since making this change, though I still have plenty of free space on my drive at the moment.

    Photos
    Here are the before and after photos. They were taken immediately before removing the drives and immediately after reinserting them.
    BEFORE
    160GB_drive_before.jpg
    AFTER
    160GB_drive_after.jpg
    BEFORE
    1.5TB_drive_before.jpg
    AFTER
    1.5TB_drive_after.jpg


  • The How

    While it's possible to mount a PS3 hard drive in Linux and view its decrypted partitions, unfortunately the tunefs.ufs tool doesn't appear to work. It always complains that it can't find the superblock. However, the file command does work fine to show the UFS2 filesystem info when tested on a dump of the start of the partition.

    So instead of using the tunefs utility to change the minimum free space and optimization type, I wrote a script to manually scan and test single byte changes to a dump of the partition's superblock using the file command until I found the correct locations to change.

    I tested this on 2 hard drives of vastly different sizes: 160 GB and 1.5 TB. On both drives, I found that the superblock was located in the same location--the standard 128 block aka 65,536 byte offset. I also found that the locations to set the minimum free space percentage and optimization type were in the same place on both drives--byte 65,599 and 65,667 respectively. However, I highly recommend running the find_ps3_ufs2_byte_locations script anyway just to confirm before making any changes to your drive.

    Once you know the correct offsets, changing the values is simple. To adjust the minimum free space, simply write the percent in hex to byte 65,599--e.g. for 1% free space write 0x01 or for the default 8% write 0x08. To change the optimization type, write a hex 0x01 to byte 65,667--the default is 0x00 for time optimization.

    I think this should be possible to do as a PS3 homebrew app so that it can just be done directly on the device without even removing the drive. Unfortunately I have zero experience with writing PS3 homebrew, but maybe someone else with more experience can use this information to do it. I'd love to see this as an option in the REBUG custom firmware settings.

    Instructions

    1. Dump your eid root key using IrisMan/MultiMan/etc
    2. Setup a computer or virtual machine with Ubuntu 16.04. The rest of these steps are done on that machine. I tested using Parallels on a MacBook Pro, but it should work on just about anything as well as other distros.
    3. Clone my repository: git clone https://github.com/einsteinx2/PS3-Reclaim-HDD-Space.git
    4. Change to the new directory as we'll do all of the work there: cd PS3-Reclaim-HDD-Space
    5. Rename your eid root key file to eid_root_key.bin and place it in the PS3-Reclaim-HDD-Space directory
    6. Generate your hdd keys: ./ps3hdd_keygen.sh
    7. Become root since most of this requires it: sudo -s
    8. Find the device name: fdisk -l (In my case, using an external USB enclosure, it was /dev/sdb)
    9. Make virtual byte swapped encrypted device
      1. If you have a drive 1TB or less (not confirmed the exact limit): ./makedev bswap16.512 /dev/sdb
      2. If you have a drive larger than 1TB (or maybe it's 1TB and larger, I don't have a 1TB drive to test): ./makedev bswap16.1024 /dev/sdb
    10. Create decrypted device: cryptsetup create -c aes-xts-plain64 -d ./hdd_key.bin -s 256 ps3hdd_crypt /dev/nbd0
    11. Map decrypted partitions: ./kpartx -a /dev/mapper/ps3hdd_crypt
    12. View decrypted partitions (ps3hdd_crypt2 is the UFS2 GameOS partition): ls -la /dev/mapper/
    13. View current free space: [ -d /mnt/PS3GameOS ] || mkdir /mnt/PS3GameOS && mount -t ufs -o ufstype=ufs2,ro /dev/mapper/ps3hdd_crypt2 /mnt/PS3GameOS && df -h | grep "Avail\|ps3hdd_crypt2" && umount /mnt/PS3GameOS
    14. Dump the superblock of the GameOS partition: dd if=/dev/mapper/ps3hdd_crypt2 bs=512 count=256 of=GameOS_superblock.img
    15. Confirm the seek values for the next 2 commands: ./find_ps3_ufs2_byte_locations GameOS_superblock.img
    16. Set minimum free space to 1%: printf '\x01' | dd of=/dev/mapper/ps3hdd_crypt2 bs=1 seek=65599 count=1 conv=notrunc
    17. Set optimization type to "space": printf '\x01' | dd of=/dev/mapper/ps3hdd_crypt2 bs=1 seek=65667 count=1 conv=notrunc
    18. View the now larger free space: mount -t ufs -o ufstype=ufs2,ro /dev/mapper/ps3hdd_crypt2 /mnt/PS3GameOS && df -h | grep "Avail\|ps3hdd_crypt2 && umount /mnt/PS3GameOS
    19. Disconnect device: kpartx -d /dev/mapper/ps3hdd_crypt && cryptsetup remove ps3hdd_crypt && ./stop-nbd0
    20. Pop the drive back in your PS3 and enjoy the extra space! Note that I left 1% reserved space rather than going all the way to 0% to ensure that the drive never completely fills up, as I'm unsure what problems that would cause for the PS3's operating system.

  • Source code

    For ease of use, this repo contains precompiled binaries for Ubuntu 16.04 64bit. If you need or prefer to compile yourself, here are the tools used:

    bswap16: https://github.com/sguerrini97/nbdcpp (note that for >1TB drives you must change <unsigned BS=512> to <unsigned BS=1024>)

    kpartx: https://git.opensvc.com/multipath-tools/.git/

    ps3hdd_keygen.sh: http://www.psx-place.com/threads/hdd-keys-generating-scripts.10610/page-2#post-125197


  • Credits

    I would never have figured this out if it weren't for others' hard work.

    Huge thanks to Berion at PSX-Place for the hdd key generation script as well as pointing me to the information on mounting a PS3 HDD in Linux. His post here contains the script and the link: http://www.psx-place.com/threads/hdd-keys-generating-scripts.10610/page-2#post-125197

    Huge thanks to sguerrini97 at Playstation Hax for implemnenting PS3 hard drive mounting support for modern Linux kernels. Here's the post about it: https://playstationhax.xyz/forums/topic/4671-mounting-ps3-hdd-on-newer-linux-kernels and the GitHub repo: https://github.com/sguerrini97/nbdcpp.

    Thanks to dsroche for writing the original nbdcpp implementation that sguerrini97 forked, and thanks to Glevand for the original work on mounting the PS3 hard drive in OtherOS and for the great information here on the PS3 dev wiki: http://www.psdevwiki.com/ps3/Mounting_HDD_on_PC. Also thanks to anyone else that worked on PS3 hard drive mounting or anything else I'm not aware of.

 
Last edited by a moderator:
I thought this day would never come. Though I have done this myself on Linux this is still getting installed on my console "just in case" you know. Thanks a lot my dude, you are golden to this community. Godspeed @3141card

Can this tool be used if you have games/files etc already on the ps3 HDD?
 
https://mega.nz/file/zdk1lKqZ#aj4WFdOeosH_ncIB5flNtUxPs341PSYaXdLF2DdA45A

PS3 Unlock HDD Space by picard (aka 3141card)
All credits to einsteinx2 on psx-place.com for his great tutorial:
https://www.psx-place.com/threads/t...l-space-on-the-ps3-internal-hard-drive.20773/

HOWTO:
  • Install the package on your custom firmware PS3 and run it. It finds the active superblock of the gameOS partition and do the necessary patches. Usually 8 percent of the memory is reserved, the app sets this value to 1 percent.
  • The optimization value is set to 1, for minimize disk fragmentation.
  • The changes are permanent. The changed active superblock is written to the HDD with the system fs umount of the gameOS partition.
  • Running the app again restores the original values, if desired.

You use this app at your own risk! I am not responsible for any damage caused to your PS3 system!​

If my PS3 app was useful to you, I would be very happy about a donation :)
https://www.paypal.com/paypalme/3141card

picard (aka 3141card)

Thank you very much for this, it's working perfectly on my Super Slim.
 
I know this is the OP's idea, but this is really impressive as everything is done with just one pkg. @3141card should have his own thread with his job, so all people could see it right away, with sticker and everything. @Coro what do you think?

Thank you @3141, I'm gonna try it on this weekend.
 
I didn't notice you had to run the app after install pkg. thought just install pkg would do it then 'install pkg again' to undo. Didn't notice the app until later. Then I ran it. Beeped once and reloaded XMB and there it was :)
 
Sorry if someone mentioned it before
After doing this reduction of the free/wasted space from the factory 8% to 1%.... the firmware installations works normally ?... and the "restore filesystem" is completed normally too ?

Has anybody been forced to check the file system (via the BSOB) after running this app? The reason I ask is that in the last 4 months, my PS3 has completely froze on the XMB (had to hold down the power button), after not crashing on the XMB for the 10 years prior. Though I figured out why...

1. Once while the VSH menu was up. Not sure if I pressed anything, but I immediately disabled the menu.
2. Another when mounting a game via webman MOD. I had installed a new version but didn't run the app (which actually installs it) before mounting.
3. The last time I was browsing some MP3s on an old, slow card reader. This thing will randomly disconnect itself when copying, or sometimes even when it's idle. It's even made the USB port stop working until a reboot (did the same thing to my TV).

Each time after a XMB freeze, the BSOD came after the reboot, scaring the crap out of me. Just wondering if this app would interfere with this.
 
Has anybody been forced to check the file system (via the BSOB) after running this app? The reason I ask is that in the last 4 months, my PS3 has completely froze on the XMB (had to hold down the power button), after not crashing on the XMB for the 10 years prior. Though I figured out why...

1. Once while the VSH menu was up. Not sure if I pressed anything, but I immediately disabled the menu.
2. Another when mounting a game via webman MOD. I had installed a new version but didn't run the app (which actually installs it) before mounting.
3. The last time I was browsing some MP3s on an old, slow card reader. This thing will randomly disconnect itself when copying, or sometimes even when it's idle. It's even made the USB port stop working until a reboot (did the same thing to my TV).

Each time after a XMB freeze, the BSOD came after the reboot, scaring the crap out of me. Just wondering if this app would interfere with this.
Hmmm, you are not telling me if you made this mod to reduce the 8% of reserved space to 1% (or any other amount smaller than 8%), so i should talk about both scenarios

My worry about the "restore filesystem" functions is because im sure sony decided to set up that 8% for some reason we ignore. I mean... is not like they thrown a dice an resulted in number 8% so they kept that 8% for the whole lifetime of the PS3 production
There must be some important reason why they did it, is just we dont know exactly why
The "retore filesystem" (and other hdd manteinance tasks that probably happens in the background when we are in main XMB) is one of them for sure
Is like in a PC, if you try to defragment an hdd that is 100% filled up with data the operative system is going to tell you that is imposible to defragment it (because is imposible to move around the data)

1. Once while the VSH menu was up. Not sure if I pressed anything, but I immediately disabled the menu.
This could happen because <whatever you did> required to load a new file, but the filesystem have some problem and the file was not loaded (it timed out and resulted in a internal reading error)
2. Another when mounting a game via webman MOD. I had installed a new version but didn't run the app (which actually installs it) before mounting.

3. The last time I was browsing some MP3s on an old, slow card reader. This thing will randomly disconnect itself when copying, or sometimes even when it's idle. It's even made the USB port stop working until a reboot (did the same thing to my TV).
If the game was located in the internal PS3 hdd then is the same stuff
If the game was in a external storage device connected by USB (or in the card reader of BC PS3 fats models that is USB too) is not so clear because his filesystem is something independent from the PS3... but the fact is the XMB uses databases to index the conetents of the external USB devices so im not sure, maybe it was a problem while trying to load data from the database

The first thing i would do is to try to use the PS3 normally for some days/weeks WITHOUT any external USB device connected... you know... if you are going to play a game be sure the game is located in dev_hdd0
 
Hmmm, you are not telling me if you made this mod to reduce the 8% of reserved space to 1% (or any other amount smaller than 8%), so i should talk about both scenarios

My worry about the "restore filesystem" functions is because im sure sony decided to set up that 8% for some reason we ignore. I mean... is not like they thrown a dice an resulted in number 8% so they kept that 8% for the whole lifetime of the PS3 production
There must be some important reason why they did it, is just we dont know exactly why
The "retore filesystem" (and other hdd manteinance tasks that probably happens in the background when we are in main XMB) is one of them for sure
Is like in a PC, if you try to defragment an hdd that is 100% filled up with data the operative system is going to tell you that is imposible to defragment it (because is imposible to move around the data)


This could happen because <whatever you did> required to load a new file, but the filesystem have some problem and the file was not loaded (it timed out and resulted in a internal reading error)

If the game was located in the internal PS3 hdd then is the same stuff
If the game was in a external storage device connected by USB (or in the card reader of BC PS3 fats models that is USB too) is not so clear because his filesystem is something independent from the PS3... but the fact is the XMB uses databases to index the conetents of the external USB devices so im not sure, maybe it was a problem while trying to load data from the database

The first thing i would do is to try to use the PS3 normally for some days/weeks WITHOUT any external USB device connected... you know... if you are going to play a game be sure the game is located in dev_hdd0

I have never had any problem with any USB drive until this card reader. I need a new one, but the last one I bought the PS3 didn't recognize. (All my games are on the HDD, I just use the USB for other stuff.). I am getting real low on space, and when I saw this app I thought my prayers were answered, but then I remembered those BSODs...
 
I have never had any problem with any USB drive until this card reader. I need a new one, but the last one I bought the PS3 didn't recognize. (All my games are on the HDD, I just use the USB for other stuff.). I am getting real low on space, and when I saw this app I thought my prayers were answered, but then I remembered those BSODs...
The only way to do some manteinance to dev_hdd0 filesystem is in your PS3 with the "restore filesystem" option. Incase this function doesnt works then is imposible and the filesystem will cummulate errors exponentially the most time you use it... up to the point where the PS3 forces you to format the hdd

If you made this tutorial to reduce the reserved space from the original 8% to a lower value then there is not an easy/clean way to return back
The problem is, when you recovered that space you made availables some sectors that are located in lower positions of the hdd. After that when you started creating new files they was written in that low sectors, so... if at some point you want to step back to the 8% you will need to identify that files and delete or move them before increasing the reserved space to 8%
Or well... maybe you can just increase the sace to 8% without doing a cleanup of that area, but then you are not goiing to know which files are going to be lost (most probably are a lot of small files, saves, trophies, etc...)

I dont know any solution for your problem to be honest, and im not completly sure if your dev_hdd0 filesystem have problems, but the symthoms you described smells fishy
As said... the first tests i would do is to use the PS3 normally WITHOUT ANY USB connected... if you still have problems like that then yeah.. you can start the DEF CON 1 procedures
 
Last edited:
Has anybody been forced to check the file system (via the BSOB) after running this app? The reason I ask is that in the last 4 months, my PS3 has completely froze on the XMB (had to hold down the power button), after not crashing on the XMB for the 10 years prior. Though I figured out why...

1. Once while the VSH menu was up. Not sure if I pressed anything, but I immediately disabled the menu.
2. Another when mounting a game via webman MOD. I had installed a new version but didn't run the app (which actually installs it) before mounting.
3. The last time I was browsing some MP3s on an old, slow card reader. This thing will randomly disconnect itself when copying, or sometimes even when it's idle. It's even made the USB port stop working until a reboot (did the same thing to my TV).

Each time after a XMB freeze, the BSOD came after the reboot, scaring the crap out of me. Just wondering if this app would interfere with this.

Hey, how soon after running the app did the freezing start? Could it just be an old HDD dying after 10 years?
 
Could be due to damages in super block. Yet also worth to check S.M.A.R.T of this HDD, which can tell You if it is in dying condition or not.
 
My worry about the "restore filesystem" functions is because im sure sony decided to set up that 8% for some reason we ignore. I mean... is not like they thrown a dice an resulted in number 8% so they kept that 8% for the whole lifetime of the PS3 production
There must be some important reason why they did it, is just we dont know exactly why
Quite easy to be honest: to keep the console from using the slowest part of the hard drive.
Because of the physical form factor of any hard drive, the first sectors are faster and the last ones are slower to access. They didnt want the possibility of games being unstable because the data is being acessed on a slower portion of the hard drive and as mentioned on the first page, to keep the user from stuffing the hard drive with data and making it impossible to defragment later.
 
Back
Top