aldostools
Error 0x8001002C: Too many open files, while copying data to FAT32 external hard drive with IRISMAN
Following up the previous issue, I've noticed that when copying folders with a large amount of files to an external hard drive formatted in FAT32, IRISMAN will randomly encounter an error 0x8001002C. I say randomly because I've see this happen with folders containing 195 items of different sizes between 0B and 300MB, just like it has happened with folders of 400 items of sizes between 0B and 8MB or large folders of more than 2000 items. So I'm not sure if this happens just because of the large number of items or if their size also influence during the copy operation. One thing is that I have noticed this happen at random times: in the folder containing 400 items, IRISMAN returned that error around the 154th item and in the folder containing 195 items, it did so much earlier at the 80th item being copied.
Once this error has happened, it becomes impossible to even copy a small folder with 10 items: IRISMAN will retrun the same error as soon as the copy starts. The only way to successfully copy something else after this error appears is to close IRISMAN (PS Button -> Quit), reconnect the hard drive and restart IRISMAN.
To avoid this error, one can manually select the items to be copied, thus keeping their number small enough for the copy to succeed and repeating the operation until the folder is fully copied. But even doing so, with different folders of different sizes is cumbersome because the error appears after selecting 120 items, 90 items or even 60 items.
I've used both a 512GB and 1TB NVMe SSD formatted in FAT32 with respectively 8KB and 32KB cluster sizes and got the same error on large folders.
Error 0x8001002c = Maximum number of operable files exceeded
If you used IRISMAN File Manager, that using the embedded exFAT Manager or try copying the files swith multiMAN.
I have to say that it was also my first time using the exFAT Manager because I always assumed that NTFS support was better somehow but glad that I got it to work with the exFAT Manager as suggested. Thank you.
Another question just to know before closing this issue, given the robustness of the exFAT Manager, would you recommend using exFAT or NTFS on external storage with IRISMAN to launch backups? I have used NTFS so far, it works well, minus some hiccups here and there like sometimes launching a backup will freeze or shut down the console.
NTFS support was added earlier than exFAT, so NTFS used to be preferred for large files.
exFAT is compatible with PS2, PS4, PS5. So you can use the storage device on these consoles too.
Today more PS3 homebrews support exFAT than a few years ago:
- IRISMAN supports exFAT, FAT32, ext2/3/4 and NTFS through exFAT Manager. Only FAT32 and ext2/3/4 and NTFS for games.
- ManaGunZ has similar support (not 100% sure due I barely have used it)
- webMAN MOD supports exFAT, FAT32, ext2/3/4 and NTFS through prepISO.
- multiMAN MOD added exFAT and ext2/3/4 recently. The official multiMAN only supports FAT32 and NTFS for external drives.
- exFAT Manager = Simple File Manager MOD 0.11
- Apollo Save Tool MOD also includes exFAT Manager. Use L1 + START to access it from Apollo's GUI
That's awesome to know, I really had no idea, thank you! I will switch to exFAT then and see how it goes. I prefer the simplicity of IRISMAN to launch backups. In my case, it helps especially because I don't have to babysit my niece and nephew when they use the PS3 when they come over. I just wish we could also hide some of the more advanced info on the UI. I started a discussion about this request too, maybe it's possible with a small update. Or I could submit a PR if there was a guide on how to compile IRISMAN.
To compile IRISMAN you basically need the PSDK3v2 provided by Estwald, whos is the original author of Iris Manager. https://github.com/Estwald/PSDK3v2
You first need to compile the payloads, payload_controlfan, loader, sm_monitor, fm_exFAT and rawseciso included in the project.
Run language_util.bat to copy the translation files to datas
Then use _Make_EBOOT.BIN.bat to compile RELOAD.SELF
I've setup the environment but when compiling, the process can't find unrar.h so I'm also unable to successfully compile fm_exFAT
Thank you, @aldostools! I was able to successfully compile and test the changes made. So far, so good. I'm currently using the compiled version to finish my back up. I will submit the PR once that's done. I have been backing up my hard drive for 2 days now, unbelievable! :D