u/RockstarArtisan

There's this excellent wiki page about hdd sizes: https://www.psdevwiki.com/ps3/Harddrive According to the page, a hdd with 931 GiB is perfectly fine when it comes to the filesystem check, nothing should fail.

Unfortunately, at least in my experience (tested in multiple configurations), the filesystem check also breaks for drives with 931GiB and below, but the symptoms only appear after the HDD is filled up.

I'm currently setting up a new ps3, with a perfectly working 1tb hdd (full format passes just fine, no sector issues), and I've noticed that somewhere between 400gb and 600gb of taken space the filesystem check function doesn't finish at 100%, but instead bails at 15%-25% (consistent wrt to the contents of the hdd, as long as you don't change the contents the failing pct is the same) and the console just reboots without finishing the check.

I have tried to narrow down the cause, this happens on a different console (why I tried to make a new setup in the first place), with a different drive (931GiB SSD), with a different CFW version (4.92 and 4.93 evilnat), and with barely any software running. I have this issue on a fresh setup where I have multiman for filemanagement, webmanmod for the iso menu and apollo for setting up the psn account; the setup is so fresh there wasn't even a hard reset or anything. All I have done was just set these up these 3 packages and copy the files from a fat32 drive to dev_hdd0.

What is the cause here? Are the filesystem functions in multiman somehow borked, or is there a hard limit not just on the drive size as the wiki claims, but also on how much of the drive is occupied? Thoughts?

The consolemods recovery guide talks about ability to mount dev_hdd0 for reads and writes: https://consolemods.org/wiki/PS3:Recovering_Data

The recommended method (HDD Decryption Helper Scripts), contrary to the description, doesn't mount the filesystem as read/write even if you compile an rw_ufs driver due to what seems to be a bug in the script which negates the ufs module presence check.

Looking at UFS itself, the fs seems to be implementation defined, with netbsd and freebsd having divergent implementations. Which scheme does the linux ufs driver implement? Ps3 seems to fork from both netbsd and freebsd, which implementation does it use and at which stage?

Are people able to successfully use the ufs linux support for ps3 hdd access? Should r/w access be warned against instead of being the default recommended access method for linux?