PS3 External NTFS HDD works with multiMan, but ain't in WebMAN MOD

Hello All,
I run in to a strange problem, as the title says my external NTFS HDD is not recognised by webMAN MOD, but it works perfectly fine with multiMan. I tried all 4 usb port, cobra mode on/off.
Any idea?

My setup:
- PS3 PHAT CECHC04, Rebug 4.86.1 LITE, WebMAN MOD 1.47.28 with prepISO 1.27,
multiMan v0.4.85.01.

- WD MyBook Essential 1TB external HDD formatted to NTFS (MBR partition)
 
multiMAN uses the PFS library, while prepISO uses the same NTFS library of IRISMAN / Iris Manager.

webMAN MOD uses a reduced version of the NTFS library modified by freddy38510 and bguerville

So it's normal to expect different results between mmCM and wMM.

I suggest that also check with IRISMAN.

If you have multiple partitions, the order of them may affect the recognition.

IIRC there are some sector sizes that have issue with NTFS lib too. Maybe @bguerville has more details since he was working on this project some years ago.
 
The psl1ght compiled libntfs library for ps3 was ported by Estwald years ago when he still worked on Irisman.
The libntfs port Freddy & I participated to was a port to compile with the original sdk toolchain. It was necessary mainly because only the official toolchain supports sprx projects so homebrews like webman, sMan or xai_plugin could not use the libntfs library directly, some of those projects had to rely on separate self executables to leverage the ntfs capabilities offered by Estwald's port.

The second port is not limited to sprx projects however, it can be used with self executables compiled with the official toolchain too. I am not aware of any particular outstanding issue with the original libntfs by Estwald.
Like @aldostools indicated, you should try Irisman (or Managunz) to see if you have the same issue with that original port.

However with the port for official toolchain projects, there is a problem (specific to sprx projects) that comes to mind immediately.
It was 4 years ago so I cannot remember how this library tweak for sprx was implemented by deank or merged later by Fred, it should only apply to sprx projects, not self projects.
Anyway, when the lib is used in a sprx, depending on the size of the partition, the ntfs cluster size could be an issue. The bigger the partition, the more likely the issue.
It might be related to a problem deank fixed, if my memory serves me well, when he included ntfs support in sMan, he found some issue with resource management & resorted to ironing it out by lowering the value of a constant in the library, something along those lines..

So let's say for instance that your ntfs partition is big enough & its cluster size is low enough, I think that 4kb might be the default value when preparing a ntfs partition on Windows, you may need to change it to 8kb or more, depending on partition size, to get the partition to be recognised properly by sMan or webMAN-MOD.
A decent partition manager can modify the cluster size without having to reformat.
 
Last edited:
Neither IRISMAN, or ManaGunZ worked in this issue.

But the cluster size point and therein lies the problem.
My drive cluster size was 512byte, so I started to increase step by step, as a trial and error experience and after 16KB everything started to recognise it. I tried it with another drives, and same result. for me it looks like it recognised everything from 16KB-64KB(my partition manager unable to modify it to higher) for sure.

TL;DR external NTFS drive cluster size should be at least 16KB.

@bguerville , @aldostools Thank you for your fast response and assistance solving this issue. Much appreciated!
 
Hi,

I would like to add that it may not be the cluster and it might be the LFS version as in my case.

My hdd can be use via multiman using usb.cfg (pfs driver) but prepiso and irisman was out of the question.
on the other hand my other hdd is detectable. i found that the undetectable ones are the ones with LFS 2.0

you can check using this command in CMD

fsutil fsinfo ntfsinfo <drive>: (eg fsutil fsinfo ntfsinfo d: )

it will show the LFS version in windows 8 and above (yes windows 10 has it but windows 7 do not)

any how, you can change the LFS version to 1.1 by going to device manage > disk > [the disk] > properties > policies tab > select quick connect and apply. voila! it should be detectable now.

important note:
you cannot configure the hdd directly from usb if its using the convertible type where you can detach the hdd. If its the detachable then you must connect it directly to a sata interface or if laptop using a hdd bay (cdrom to hdd) to change the type of LFS. if it direct usb like some branded ext hdd models (eg WD) then its should be possible to change it without any issues but its likely that the hdd is already v1.1)

reference:
https://social.technet.microsoft.co...derations-with-prior-versions-of-windows.aspx
 
Last edited by a moderator:

Similar threads

Back
Top