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 ​

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

About The How + Instructions Source Code Credits

• 
  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	AFTER
  BEFORE	AFTER

• 
  
  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.
  

​

 

Maybe Unlock HDD Space has nothing to do with freezing of my console

I've seen several posts with people having problems with the latest evilnat, that's why I'm staying with Rebug.

 

Been using EvilNat since his first beta and HDD unlock. Using only webMAN for fan control I have been issue free. Trying to use the built in fan management conflicted with webMAN mods fan settings. Did a fresh install and haven't touched the built in fan settings and it's been just as solid at Rebug, Habib or joonies firmwares.

 

In regards to the "PS3 Unlock HDD Space by picard".
If I have the program activated. What if I fill up my HDD and then accidentally press the x button on the program?
Will it delete stuff on my HDD?

Also, how do I move the icons around on the XMB screen to avoid accidentally pressing anything? I would like to put certain programs in folders to make the XMB screen un-cluttered and to avoid pressing anything by accident.

Thanks in advance.

 

The You will loose data because of "shrink" UFS2 partition on which You already have some data. If sectors already in use be used in future for UFS operations, they will be overwritten and You will not know that until check byte by byte those files (or if corruption affect in game by game freezing etc.). That's hypothesis, no one was brave enough to check it.

Uninstall the app and You will not click on it by accident. :P If for some reason You want keep it on HDD, keep it in package form under "dev_hdd0/packages/*.pkg".

 

The You will loose data because of "shrink" UFS2 partition on which You already have some data. If sectors already in use be used in future for UFS operations, they will be overwritten and You will not know that until check byte by byte those files (or if corruption affect in game by game freezing etc.). That's hypothesis, no one was brave enough to check it.

Uninstall the app and You will not click on it by accident. :P If for some reason You want keep it on HDD, keep it in package form under "dev_hdd0/packages/*.pkg".

OK, I will uninstall it. But if I do will I lose the HDD space?
If I don't lose the HDD space after uninstall, if I ever change my mind and want to revert back to not using the program, at a later date, can I just reinstall it and revert back to my original HDD settings?

Thanks

EDIT: Nevermind, I freed up some space and experimented and uninstalling the 8% program does not revert the changes it made.

 

To revert changes, You must run it again.

*.pkg alone is like *.zip but for PS3. It is only handy archive which tells PS3 where to put contents and register it in database as what exactly content. Nothing more.

Unpacked archives are not self aware so they do nothing on their own. User must run executable or they will not do what they doing.

 

One question, does it work for an SSD drive on PS3?

 

One question, does it work for an SSD drive on PS3?

It does, I have a 2TB SSD (downscaled to 1.525TB) with the PS3 Unlock HDD Space working.

 

One question, does it work for an SSD drive on PS3?

Storage type doesn't matter. Logic structure on all is the same, also for those which not exist today.

 

Hi all,

I bought sdd 2TB of Crucial but it seem that for my model can't be changed the max LBA to 1.5TB
I tried to copy from old to new using tool HDD from Debug Setting of PS3 but at the end of the process PS3 frozen
And tried to clone original HDD to SSD using application "Lazesoft Disk Image & Clone Home" from PC, this way PS3 detects ssd 2TB but it doesnt show all free space in this

So the question is, there is some posibility to resize partition ssd to 1.5TB?

Thanks and regards

 

I bought sdd 2TB of Crucial but it seem that for my model can't be changed the max LBA to 1.5TB

Why?

If You have problems with syntax of hdparm, use this:
https://www.psx-place.com/resources/ps3-hdd-decryption-helper.1293/

You don't need ERK, because You don't need decrypting anything. Just run "PS3 HDD Tasker.sh" and choose to change maximum size of disk (option no.3). SSD must be connected to SATA port on motherboard, in most USB controllers I tried, this ata command is not supported so high probability You will cannot set HPA by that way. That's why SATA is needed.

Also take in mind that 1.5 not works for everyone. Safe is 1TiB. And not all SSD can works fine with PS3.

So the question is, there is some posibility to resize partition ssd to 1.5TB?

No, because there is no tools for manipulating PS3 partition table and UFS2 filesystem, and on PS3 HDD/SSD/SHDD there is no just one partition anyway.

 

Why?

If You have problems with syntax of hdparm, use this:
https...

You don't need ERK, because You don't need decrypting anything. Just run "PS3 HDD Tasker.sh" and choose to change maximum size of disk (option no.3). SSD must be connected to SATA port on motherboard, in most USB controllers I tried, this ata command is not supported so high probability You will cannot set HPA by that way. That's why SATA is needed.

Also take in mind that 1.5 not works for everyone. Safe is 1TiB. And not all SSD can works fine with PS3.


No, because there is no tools for manipulating PS3 partition table and UFS2 filesystem, and on PS3 HDD/SSD/SHDD there is no just one partition anyway.

Thanks Berion,

I followed your steps but it didn't work
Is there some way to do work this ssd in PS3 or nothing to do?
I have in my mind to try take a old HDD 3TB over here to change Max LBA to 1.5TB, format from PS3 and clone to SSD 2TB

Regards

 

@macamba You wrongly run the script (judging by turned off echo -e from output). You should just double click on it like any executable. But if You want do that from Terminal, then do this (from default script location, but I see you have changed file name and put in different dir; anyway, place is free for this specific task, just like the name, but for a refference I left below syntax, important here is using bash name):

bash "${HOME}/ps3/PS3 HDD Tasker.sh"

I don't know if this is the reason, of error kind displayed in the attachment. Maybe this messed the syntax, so try do it properly.

If You want do that manually without my script help, then this is the syntax:

sudo hdparm -N p3221225472 --yes-i-know-what-i-am-doing /dev/sdx

Where sdx is Your target PS3 HDD, e.g sda, sdb, sdc etc.

Eventually there is another factor. Above is for sector size 512. For 4096 sector size, You need different value (402653184) because above (3221225472) will exceed Your real capacity.

This is how to calculate size in LBA if You want to experiment:
Put desired size: https://calcuworld.com/business-calculators/bytes-calculator/
Copy bytes number and use in terminal calculator:

calc 1649267441664/512
calc 1649267441664/4096

"512" dividing for 512 and 512e sector size HDD/SSD/SHDD, and "4096" for 4K sector size.

Is there some way to do work this ssd in PS3 or nothing to do?

If Your SSD turned to be incompatible (PS3 not booting properly every time, sometimes fschk occurrence, data loss etc.), You can do nothing about it.

 

@macamba You wrongly run the script (judging by turned off echo -e from output). You should just double click on it like any executable. But if You want do that from Terminal, then do this (from default script location, but I see you have changed file name and put in different dir; anyway, place is free for this specific task, just like the name, but for a refference I left below syntax, important here is using bash name):

bash "${HOME}/ps3/PS3 HDD Tasker.sh"

I don't know if this is the reason, of error kind displayed in the attachment. Maybe this messed the syntax, so try do it properly.

If You want do that manually without my script help, then this is the syntax:

sudo hdparm -N p3221225472 --yes-i-know-what-i-am-doing /dev/sdx

Where sdx is Your target PS3 HDD, e.g sda, sdb, sdc etc.

Eventually there is another factor. Above is for sector size 512. For 4096 sector size, You need different value (402653184) because above (3221225472) will exceed Your real capacity.

This is how to calculate size in LBA if You want to experiment:
Put desired size: https://calcuworld.com/business-calculators/bytes-calculator/
Copy bytes number and use in terminal calculator:

calc 1649267441664/512
calc 1649267441664/4096

"512" dividing for 512 and 512e sector size HDD/SSD/SHDD, and "4096" for 4K sector size.


If Your SSD turned to be incompatible (PS3 not booting properly every time, sometimes fschk occurrence, data loss etc.), You can do nothing about it.

Hi Berion,
I tried all ways to execute command and script but the problem is that my SSD 2TB can't be change max LBA, it's locked by Crucial for SSD

Anyway thank you for help
Regards

 

How do You know that? Who or what tells You that? Never heard of any producer which blocking setting HPA or DCO in fw.

What about checking if SSD is in frozen state? It must be unfrozen to set HPA. The easiest way to change that is to hibernate computer and wake him up. ;]

 

How do You know that? Who or what tells You that? Never heard of any producer which blocking setting HPA or DCO in fw.

What about checking if SSD is in frozen state? It must be unfrozen to set HPA. The easiest way to change that is to hibernate computer and wake him up. ;]

Well, I checked if the SSD was frozen and yes, it was frozen. To unfrozen use this command to suspend pc (sudo systemctl suspend) and wait 1 minute and wake up pc then the SSD go to "not froze" as you can see below executing -> hdparm -I /dev/sda

root@ubuntu:/home/ubuntu/Documentos/PS3_HDD_Decryption_Helper# hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
    Model Number:       CT2000BX500SSD1                   
    Serial Number:      2250E692DBD8 
    Firmware Revision:  M6CR061
    Media Serial Num:
    Media Manufacturer:
    Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
    Used: unknown (minor revision code 0x011b)
    Supported: 10 9 8 7 6 5
    Likely used: 10
Configuration:
    Logical        max    current
    cylinders    16383    16383
    heads        16    16
    sectors/track    63    63
    --
    CHS current addressable sectors:    16514064
    LBA    user addressable sectors:   268435455
    LBA48  user addressable sectors:  3907029168
    Logical  Sector size:                   512 bytes
    Physical Sector size:                   512 bytes
    Logical Sector-0 offset:                  0 bytes
    device size with M = 1024*1024:     1907729 MBytes
    device size with M = 1000*1000:     2000398 MBytes (2000 GB)
    cache/buffer size  = unknown
    Form Factor: 2.5 inch
    Nominal Media Rotation Rate: Solid State Device
Capabilities:
    LBA, IORDY(can be disabled)
    Queue depth: 32
    Standby timer values: spec'd by Standard, no device specific minimum
    R/W multiple sector transfer: Max = 1    Current = 1
    DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
         Cycle time: min=120ns recommended=120ns
    PIO: pio0 pio1 pio2 pio3 pio4
         Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
    Enabled    Supported:
       *    SMART feature set
            Security Mode feature set
       *    Power Management feature set
       *    Write cache
       *    Look-ahead
       *    WRITE_BUFFER command
       *    READ_BUFFER command
       *    NOP cmd
       *    DOWNLOAD_MICROCODE
       *    48-bit Address feature set
       *    Mandatory FLUSH_CACHE
       *    FLUSH_CACHE_EXT
       *    SMART self-test
       *    General Purpose Logging feature set
       *    WRITE_{DMA|MULTIPLE}_FUA_EXT
       *    64-bit World wide name
       *    {READ,WRITE}_DMA_EXT_GPL commands
       *    Segmented DOWNLOAD_MICROCODE
       *    Gen1 signaling speed (1.5Gb/s)
       *    Gen2 signaling speed (3.0Gb/s)
       *    Gen3 signaling speed (6.0Gb/s)
       *    Native Command Queueing (NCQ)
       *    Phy event counters
       *    READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
       *    DMA Setup Auto-Activate optimization
            Device-initiated interface power management
       *    Software settings preservation
            Device Sleep (DEVSLP)
       *    SANITIZE feature set
       *    BLOCK_ERASE_EXT command
       *    DOWNLOAD MICROCODE DMA command
       *    WRITE BUFFER DMA command
       *    READ BUFFER DMA command
       *    Data Set Management TRIM supported (limit 8 blocks)
Security:
    Master password revision code = 65534
        supported
    not    enabled
    not    locked
    not    frozen
    not    expired: security count
        supported: enhanced erase
    6min for SECURITY ERASE UNIT. 6min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 500a0751e692dbd8
    NAA        : 5
    IEEE OUI    : 00a075
    Unique ID    : 1e692dbd8
Device Sleep:
    DEVSLP Exit Timeout (DETO): 90 ms (drive)
    Minimum DEVSLP Assertion Time (MDAT): 26 ms (drive)
Checksum: correct

But when again try to change the max capacity using script, it couldn't change

PS3 HDD Tasker v1.5 by Berion
Script allows various of tasks HDD related. ALL are DANGER for unaware users!

Confirm root permissions everytime You will be asked for!

Choose the task:
 1. Remove OtherOS (NOR models only).
 2. Change UFS2 preservation space to 1%.
 3. Change maximum size of HDD.
 4. Backup partition table.
 5. Fix Bootloop.
 6. Create Key Vault on last sector of HDD.

3

This task doesn't need HDD decryption. Run the "PS3 HDD Umounter.sh" first.
ALL data on HDD will be LOST!

If task will fail, hibernate computer, wake him up and run script again.
This will unfrozen HDD/SSD, allowing to set or unset HPA area.

Choose your HDD from PS3 (type eg: /dev/sdx) from below device list:

MODEL              SIZE NAME
                   2,5G /dev/loop0
                     4K /dev/loop1
                  63,3M /dev/loop2
                 240,6M /dev/loop3
                 346,3M /dev/loop4
                  91,7M /dev/loop5
                  45,9M /dev/loop6
                   304K /dev/loop7
                  49,8M /dev/loop8
CT2000BX500SSD1    1,8T /dev/sda
SanDisk 3.2Gen1   57,3G /dev/sdb
                  57,3G ├─/dev/sdb1
                   4,6G │ └─/dev/mapper/ventoy
                    32M └─/dev/sdb2
MassStorageClass 238,5G /dev/sdc
                 238,5G └─/dev/sdc1

/dev/sda
Ok, so You've chose: "/dev/sda":


/dev/sda:
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 max sectors   = 3907029168/1(1?), HPA setting seems invalid (buggy kernel device driver?)
MODEL                    SIZE NAME
CT2000BX500SSD1 2000398934016 /dev/sda

Set maximum sector nubmer:
a. user defined LBA                - custom disk size
b. 4GiB   (~4.3GB)  LBA:8388608    - minimal accepted disk size
c. 22GiB  (~23.6GB) LBA:46137344   - minimal accepted disk size with OtherOS
d. 1TiB   (~1.1TB)  LBA:2147483648 - maximum disk size
e. 1.5TiB (~1.65TB) LBA:3221225472 - maximum disk size in unknown cases

e


/dev/sda:
 setting max visible sectors to 3221225472 (permanent)
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 a0 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 max sectors   = 3907029168/1(1?), HPA setting seems invalid (buggy kernel device driver?)


/dev/sda:
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 max sectors   = 3907029168/1(1?), HPA setting seems invalid (buggy kernel device driver?)
MODEL                    SIZE NAME
CT2000BX500SSD1 2000398934016 /dev/sda


All done. Press any key to exit.

I tried also using oficial tool of Crucial Crucial Storage Executive but it neither got to change it. I was reading documentation about that and find this -> https://www.crucial.com/support/articles-faq-ssd/overview-crucial-storage-executive

Also try the option Over Provisioning at 30% but it only work for NTFS format, first partition 1.3~TB NTFS and all the rest (30%) of SSD not format, but when I insert the SSD to PS3 indicates that this SSD is not compatible

So I don't have too much options

 

@macamba Overprovisioning is something different and shouldn't be in conflict with HPA. Because on SSD, it is firmware which deciding which blocks be exposed as which LBAs. So this is hidden space on lower level than HPA can cover.

So I have no idea why this doesn't work. Sorry.

 

After unlocking, the idle CPU temperature of the PS3 Slim is 74°C.
Even if I play at 74-75°C.
Can this be the reason?
Even after replacing the thermal paste, unfortunately no change in temperature.
RSX at 54-60°C

 

No, UFS2 changes have nothing to do with console stress.

 

I'm having black screen when I run the application...
it's not working anymore on 4.90?