PS3 PS3 ISO on external HDD (WD BLACK P10 2TB)

John1971

Member
Hi
im wondering whats going on right now as i transfered all my PS3 ISO into another external HDD (Western Digital Black P10 2TB) recently purchased , freshly opened box , to finally gather all my iso into one single HDD 2TB.

Problem is , when i finished the transfer (2 days) , i correctly disconnected the hdd from the laptop and plugged it immediatelly into my CFW 4.86.1 Rebug Console...but now webman are not able to show/see the iso.
in "my game" the PS3 ISO folder is totally empty.

P.S. I formated the HDD in FAT32 with GuiFormat Program prior to transfert of data.

Any iday guys why i dont see my ISO files ?
 
I think you might want ntfs if using iso files on an external, but I've never personally used ntfs. right now, I'm only using my internal hdd. make sure also, that it's PS3ISO (no spaces).
 
1- Check if the content of the disk is visible using the File Manager of webMAN MOD
Go to http://127.0.0.1/dev_usb000 and check the directories.
2- Check that the folder PS3ISO is all uppercase
3- You're using the full edition of webMAN MOD
Go to http://127.0.0.1/ the edition appears at the bottoms of the screen
4- Go to Rebug Toolbox and check that you have Cobra enabled
5- Check that the scan for content has PLAYSTATION 3 selected and /dev_usb000 checked.

If everything is ok, refresh XMB & reload XMB.
 
I think you might want ntfs if using iso files on an external, but I've never personally used ntfs. right now, I'm only using my internal hdd. make sure also, that it's PS3ISO (no spaces).
Yes PS3ISO no space .
But someone told me that it was better to have external HDD set in FAT32 (with splitted iso)
Actually my 3 older smaller hdd size (250,1tb (931) are all in FAT32 format and PS3 dont have any issues detecting them , so im wondering...
 
1- Check if the content of the disk is visible using the File Manager of webMAN MOD
Go to http://127.0.0.1/dev_usb000 and check the directories.
2- Check that the folder PS3ISO is all uppercase
3- You're using the full edition of webMAN MOD
Go to http://127.0.0.1/ the edition appears at the bottoms of the screen
4- Go to Rebug Toolbox and check that you have Cobra enabled
5- Check that the scan for content has PLAYSTATION 3 selected and /dev_usb000 checked.

If everything is ok, refresh XMB & reload XMB.
Im actually on one feet (eating with my wife on my back...)i will smallow quickly and do your step by step dear Aldostools and come back to you in a shortly manner...
 
The step 1 assumes that you have connected your external HDD in /dev_usb000 (the port closest to the bluray drive).

If the content is not shown, it is possible that you formatted the disk as GPT instead of MBR. This link explains how to change:
https://www.diskpart.com/gpt-mbr/convert-gpt-to-mbr-without-data-loss-using-command-prompt.html
without knowning what i do when i format a HDD i assumed that its that part that i f***
how to know if i have a GPT or MBR right now ?

EDIT i just hope i will not have to erase and try transfer again...
hope their a way to change GPT/MBR MBR/GPT simply without loosing everything ...
 
The step 1 assumes that you have connected your external HDD in /dev_usb000 (the port closest to the bluray drive).

If the content is not shown, it is possible that you formatted the disk as GPT instead of MBR. This link explains how to change:
https://www.diskpart.com/gpt-mbr/convert-gpt-to-mbr-without-data-loss-using-command-prompt.html
My webman setting is in french
I changed ENGLISH for the PS3 system and made soft reboot , but my webman still stick in french
for better comprehension of your explanations on webman , i need it in english in order to not make error.
how i can set it back in english ?

EDIT : while waiting for your , i changed my windows 10 language setting for english
I gone throught "MANAGE" and i compared one of my old external HDD that is recognized by the PS3 and my last brand new one that i formatted in FAT32 two days ago and to my eyes are are set similar...but i still search where i can see the gpt vs mbr , i remember having seen theses words last year but i not able to remember in wich circonstances or using what type of programs ....
 
Last edited:
I have an external 2tb disk on the ps3 in ntfs and all the games in iso. When you change the disk, you must have the pepISO tool installed on your ps3, you run it, it will scan your disk, (it also works with exfat disks) , and when it finishes, you refresh the list of games from webman, restart and you should already have everything in place
 
HDD is set in GPT
...it is possible to switch MBR without erasing anything ?

Ok thanks for the link
i will try that , trying to not corrupt my iso files ;)

Thanks
I will get back next weekend to let you know how it turned
 
Last edited:
I have an external 2tb disk on the ps3 in ntfs and all the games in iso. When you change the disk, you must have the pepISO tool installed on your ps3, you run it, it will scan your disk, (it also works with exfat disks) , and when it finishes, you refresh the list of games from webman, restart and you should already have everything in place
I was unaware of this pepISO tool (homebrew) ? until you mention it , could be a life saver...
did you think it could help me beeing in FAT32 in GPT instead of MBR ? I dont want to erase and re-install 2TB of iso
 
The MBR or the GPT indicates how is stored the info at the most begining of the hdd (we could say is the boot area)
MBR is something legacy used by PC's since tenths of years ago, the PS3 only understands MBR (not GPT)
And for the filesystems of external devices the PS3 only understands FAT (not NTFS or exFAT)
Im talking only about the features supported nativelly in OFW

But by using custom code we have this options nowadays:
MBR + FAT <--- native support, supported by all backup managers, and other official functions
MBR + NTFS <--- custom support, supported by all backup managers, but every backup manager uses his own NTFS driver and/or implementation that are different
MBR + exFAT <--- custom support, only supported by prepISO/webman by now, and soon by the next managunz release

The payback of using MBR/FAT is that you need to split the files bigger than 4GB, but other than that there is no problems with it
The other 2 options MBR/NTFS or MBR/exFAT are going to be on pair in the ammount of support/problems/features
 
The MBR or the GPT indicates how is stored the info at the most begining of the hdd (we could say is the boot area)
MBR is something legacy used by PC's since tenths of years ago, the PS3 only understands MBR (not GPT)
And for the filesystems of external devices the PS3 only understands FAT (not NTFS or exFAT)
Im talking only about the features supported nativelly in OFW

But by using custom code we have this options nowadays:
MBR + FAT <--- native support, supported by all backup managers, and other official functions
MBR + NTFS <--- custom support, supported by all backup managers, but every backup manager uses his own NTFS driver and/or implementation that are different
MBR + exFAT <--- custom support, only supported by prepISO/webman by now, and soon by the next managunz release

The payback of using MBR/FAT is that you need to split the files bigger than 4GB, but other than that there is no problems with it
The other 2 options MBR/NTFS or MBR/exFAT are going to be on pair in the ammount of support/problems/features

Thanks for the clarification Sandungas , with everything in mind now i will choose the long & painful way but in the end i will be 100% supported natively by all backup managers and other official functions. (the best choice)

The MBR or the GPT indicates how is stored the info at the most begining of the hdd (we could say is the boot area)
MBR is something legacy used by PC's since tenths of years ago, the PS3 only understands MBR (not GPT)
And for the filesystems of external devices the PS3 only understands FAT (not NTFS or exFAT)
Im talking only about the features supported nativelly in OFW

But by using custom code we have this options nowadays:
MBR + FAT <--- native support, supported by all backup managers, and other official functions
MBR + NTFS <--- custom support, supported by all backup managers, but every backup manager uses his own NTFS driver and/or implementation that are different
MBR + exFAT <--- custom support, only supported by prepISO/webman by now, and soon by the next managunz release

The payback of using MBR/FAT is that you need to split the files bigger than 4GB, but other than that there is no problems with it
The other 2 options MBR/NTFS or MBR/exFAT are going to be on pair in the ammount of support/problems/features
Before formating the hdd , did the "allocation size unit" is important ? so many selection offered...
 
Last edited by a moderator:
Before formating the hdd , did the "allocation size unit" is important ? so many selection offered...
The theory is.. when we store a file, is going to use an space on hdd that is going to be "rounded up" to a multiplyer of the cluster size, lets say...
If you store a file of 37KB and your cluster size is 64KB, then that file is going to use 64KB (one cluster)
If you store a file of 65KB and your cluster size is 64KB, then that file is going to use 128KB (two clusters)

As you can see there is always an small amount of space wasted, but this is something that matters only when you are going to store lot of tiny files
Lets say... if you want to store thousands of files of 65KB then using a cluster size of 64KB could be a bit unnefficient (it would be like reducing the capacity of the whole hdd to half)
But in this case it doesnt matters because the files you are going to store are huge (ISO's of several GB), for every ISO file you are going to waste 1 cluster, and it doesnt matters the size of that cluster because are going to be just a few KB (if we compare the size of the cluster with the size of the ISO... the space of the wasted cluster is ridicully small)
So... from the point of view of storing data efficiently, in this case the cluster size doesnt matters at all

------------
In this case the most important thing to consider is that using big clusters is better for the functions that accesess the data, the functions knows that the file starts in (lets say) cluster 2234 and is needed to read 17862 clusters consecutivelly then the function reads all that clusters as a data stream
By using big cluster we are reducing that numbers so the functions doesnt needs to do so many "jumps" to find the next cluster
Also, all that clusters needs to be "indexed" in the filesystem table, by using big clusters we are reducing that index

So... in therory the biggest cluster size is the better in this case because the files we are reading are huge... but i dont know all the answers of what works best for PS3

-------------------
Personally, i bought a 2TB USB hdd some years ago to dedicate it for the PS3 and i decided to format it in MBR/NTFS
If you ask me nowadays what i would choose, in between MBR/FAT or MBR/NTFS or MBR/exFAT.... im not sure what i would choose, i think everyone of them has his "pros" and "contras"

The cluster size i choosed when i formatted it to MBR/NTFS... i dont remember, i formatted it in windows and i just acepted the default cluster size microsoft windows was suggesting to use
 
Last edited:
The theory is.. when we store a file, is going to use an space on hdd that is going to be "rounded up" to a multiplyer of the cluster size, lets say...
If you store a file of 37KB and your cluster size is 64KB, then that file is going to use 64KB (one cluster)
If you store a file of 65KB and your cluster size is 64KB, then that file is going to use 128KB (two clusters)

As you can see there is always an small amount of space wasted, but this is something that matters only when you are going to store lot of tiny files
Lets say... if you want to store thousands of files of 65KB then using a cluster size of 64KB could be a bit unnefficient (it would be like reducing the capacity of the whole hdd to half)
But in this case it doesnt matters because the files you are going to store are huge (ISO's of several GB), for every ISO file you are going to waste 1 cluster, and it doesnt matters the size of that cluster because are going to be just a few KB (if we compare the size of the cluster with the size of the ISO... the space of the wasted cluster is ridicully small)
So... from the point of view of storing data efficiently, in this case the cluster size doesnt matters at all

------------
In this case the most important thing to consider is that using big clusters is better for the functions that accesess the data, the functions knows that the file starts in (lets say) cluster 2234 and is needed to read 17862 clusters consecutivelly then the function reads all that clusters as a data stream
By using big cluster we are reducing that numbers so the functions doesnt needs to do so many "jumps" to find the next cluster
Also, all that clusters needs to be "indexed" in the filesystem table, by using big clusters we are reducing that index

So... in therory the biggest cluster size is the better in this case because the files we are reading are huge... but i dont know all the answers of what works best for PS3

-------------------
Personally, i bought a 2TB USB hdd some years ago to dedicate it for the PS3 and i decided to format it in MBR/NTFS
If you ask me nowadays what i would choose, in between MBR/FAT or MBR/NTFS or MBR/exFAT.... im not sure what i would choose, i think everyone of them has his "pros" and "contras"

The cluster size i choosed when i formatted it to MBR/NTFS... i dont remember, i formatted it in windows and i just acepted the default cluster size microsoft windows was suggesting to use
Sorry for late reply but thanks Sandungas!
 
Which games are the 3 ones you have in JB format @John1971 ?
Im curious because (in theory) all the PS3 games that was published in physical format (as a bluray disc) should run fine in ISO format
 
Hello guys i hope that you are doing fine i wanted to add something additional regarding the cluster size i actually do have an External 2tb HDD into a fat32 format i do actually store un format games and Split iso ones too and i managed ti setup the cluster size to be up to 64 kb it is because that i saw that it makes a difference at the moment that it reads the stored information much better and smoothly that the standard 4kb, also it does not defragment too much when on my case i need to do defrag process, best regards
 
Back
Top