PS2 [Testers Needed] OPL internal exfat 2TB+ HDD and multi-BDM devices

Spent all night adding games and working to manually add cover art, and ran into a big issue. When plugging my working drive back into my windows PC, my PC says that the drive is empty and in raw format. I thought it had been erased, but when I plugged it back into my PS2 it still worked correctly. This means that, for me at least, a big part of the use case for this version of OPL is lost (the ability to drag and drop files using windows explorer).

I had previously been able to successfully swap my Hard drive between my ps2 and PC, the only difference since then is that I renamed a game file through OPL (which as I noted earlier, resulted in a crash of my PS2) To rename a file I had to turn on OPL write permissions. My shot in the dark guess is that maybe OPL (which was previously expecting MBR drives) tried changing the header when I gave it those permissions and saved the changes, which is why it is still usable on the PS2, but Windows and Mac see it as a corrupt drive. (Windows Explorer lists it as raw data and says it needs to format, Minitool Partition Wizard says it is MBR, despite it having been formatted in GPT). The MBR format should be impossible as it is a 4tb drive.

Update: Was able to fix the corrupted drive with MiniTool Partiton Wizard and now it seems to be working as intended. No idea what led to the issue, but felt you all would want as much information as possible.
 
Last edited:
I have a fat ps2, SPH-3001, and pademu isn't available in my controller settings on the GrimDoomer OPL. I have the latest build. Has the functionality been takin out?
I wanted to use my ps3 and ps4 controller on my ps2 when possible
 
Sorry for triple post, please feel free to edit all these together. My drive with the tool MiniTool Partition Wizard is showing up as MBR.. it was originally formatted as GPT and is a 4tb drive, so as far as my limited tech knowledge goes, that shouldn't be possible and is likely the source of my issue.

Yup, MBR is limited to about 2.2TBs. It's why I said in my video to use MBR for 2TB or less and GPT for everything higher, but in all technicality, I should've said any hard drive with a total capacity of 1.98TB in actual space should use MBR because some drives are not exactly 1TB (my Seagate is actually 931GB) or 2TB (i.e. 1.98TB). Seagate is exact in their math; WD uses general consensus (i.e. 1000GB = 1TB) ...
 
Thank you so much grimdoomer for an excellent fork!

Is MX4SIO faster than a USB hard drive or are the two equivalent? Also, Gran Turismo 4 in ZSO format blackscreens, in ISO it infinitely loads a map.
 
New build available: https://github.com/grimdoomer/Open-PS2-Loader/releases/tag/v1.2.0.3-beta

Change log:
  • Fixed issues with manual start mode for devices
  • Fixed issues with freezing on startup
  • Fixed issues with IGR freezing/not working (I've tested this quite a bit and it hasn't crashed yet, but I'm still not confident the issue is fully fixed)
  • Fixed issues with renaming/deleting games not refreshing the game list
  • Fixed issues with config files causing freezing on startup (thanks Bat_Rastard for the config file upload)
I've included a pdaemu version with this build as well, though it's completely untested. There's a couple things I want to highlight which I've detailed below.

MBR vs GPT
MBR partition style only works on drives up to 2.2TB (it's technically like 2.19TB), but GPT works on all sizes. The drive does not need to be larger than 2TB to use GPT, you can format a drive of any size using GPT partition style. When you do format a drive using GPT style you will also get what's called a "protective MBR". It's an MBR partition sector that's there for backwards compatibility with OS's that don't support GPT. Unless you're plugging this drive into a very old PC (like Windows XP old) every version of Windows from Vista and up have support for GPT, so you're not losing anything by using GPT even for drives of smaller sizes.

OPL has no insight as to whether the device is MBR or GPT, that's all handled by a different module and as far as OPL is concerned there's no difference between the two. There isn't any reason why one would perform better than the other. Once the MBR/GPT sectors are parsed and the exFAT file system is mounted they're never accessed again until OPL is restarted.

OPL has no ability to rewrite the MBR or GPT sectors, nor will it try to. If you experienced file system corruption issues and you haven't reformatted the drive since using one of the previously posted OPL builds with corruption issues, this is probably a result of those issues. I would recommend formatting any drive used with the older versions I posted as there was a chance of file system corruption occurring, even if it seemed to work fine since then. This is exactly why I removed those builds from my github. It's possible there is some other corruption bug at hand that I haven't fixed yet, but I have been using my HDD, USB, and MX4SIO devices heavily since the last two builds and haven't had any issues.

Config file issues
This latest build I posted, v1.2.0.3, contains a number of bug fixes for issues with config files causing freezing on startup. However, I still have not fixed the issues related to config files being loaded/saved to incorrect devices. The bottom line is, this is complicated for other reasons. Some people want the config file on the MC, some people want it on the usb stick, others might want it on the HDD. Trying to save it to mass0 might not save it to the same device every time, as mass0 isn't specific to a single device, rather, it's whichever device was mounted first.

Rather than trying to come up with some complicated logic for where the config file should be saved to, I opted to leave this as-is. OPL will default to looking on the memory card first, and check mass0 second, and again, mass0 is the first fat/exFAT partition to get mounted across all devices plugged in. It may not be the same partition/device every time depending on how long it takes for the devices to ready up and which devices you have plugged in at the time. This feature is probably due for a redesign now, but I don't have any plans on doing this myself.

Menu issues
There are still a number of bugs with the main menu after adding in "hot-plugging" support for BDM devices. Things like
  • The left/right arrows appearing/not appearing correctly based on the current menu state
  • Enabling/Disabling BDM devices in the OPL settings menu may require a reboot of OPL before they appear in the games list menu
The bottom line is the OPL menu system was not designed to handle menus dynamically appearing and disappearing. It was designed to handle 4 or 5 static menus with no ability to dynamically update the menu list. Adding support for hot-plugging devices was a feature I thought most people would enjoy when using BDM devices, but it has pushed the menu system to its limits and these bugs are a result of that. I don't really have any plans on refining this any further, as it's taking more time to address these smaller issues than it's worth, and trying to fix one issue just causes another to appear. Ultimately the menu system should really be rewritten to handle this type of functionality vs. me trying to hack it in and hoping for the best.

Submitting back to the main OPL repository/PR status
My initial goal was to get my changes checked into the main OPL repository but a number of things have changed along the way and I no longer intend to submit a PR for these changes. The reality is I ended up making way more changes to support these new features than I initially anticipated, and it's too big to submit in a single PR. There's also a number of smaller issues at hand (menu things, config file things, etc).

Submitting multiple PRs would take a long time, and any issues that pop up (and there will be issues) whether my fault or not, I will have to go investigate. The debug-ability of OPL (and ps2 homebrew in general) is extremely poor, and debugging even a small issue can take hours to investigate. As I mentioned above OPL was not designed to handle some of these new features (40+ people have been hacking things into it for over 10 years now and the code shows for it), and there are other features which are now due for a redesign as different people expect different behaviors from them than how they used to function.

When I initially took this project on I had no intention of sticking around the ps2 community long term. I mostly came to making loading games off a HDD easier, and look into a couple hardware specific things. I will continue to try and look into any major bugs that pop up, but as I have mostly achieved my main goal of making it easier to load games I no longer plan to see this through to the end for the reasons stated above. I will leave all the changes I've made on my fork of OPL on my github, and I may even try and clean up my changes into a "PR ready" branch in case someone else wants to try committing them back to the main repo. But I don't have any plans on submitting them myself.

Once again a huge thanks to everyone who helped test this and reported feedback, without you this would not have come as far as it has in such a short period of time.
 
Thank you for all the work you've done on this @grimdoomer. Managing the HDD for the PS2 was an archaic nightmare previously, and exFAT support was a sorely needed update to modernize the process. Hopefully the other OPL contributors can take your work and merge it in slowly but surely. I certainly can't see myself going back to my old APA drive because this is just so much better.

Sad to hear you don't plan to stick around long term, but its completely understandable.
 
I will still look into fixing major issues, but smaller issues like some of the things I mentioned are turning into time sucks and I most likely wont address them if it's not a quick fix.

Thanks for your work so far, even if this is your final version it made a huge difference, and for the most part does what you set out to do.

The good thing about github is someone may take it on at a later date and improve on it
 
Tried it quickly this morning before work.

File rename is now working.

However all games now boot to black screen. I tried deleting the OPL folder same issue.

Will try again and troubleshoot later if I have time or tomorrow
 
It's all working for me in this new update.
Now it's booting from Modbo 5 USB menu, don't get anymore black screens. Still crashing when i press reset, but now the console shuts down automatically.
Btw, thank you so much for this fork and all you hard work so far. It's a really helpful tool and now it's easier as never before.
 
Tried rolling back a build and still black screen.

Deleted opl folder and tried new build again with same settings changed. Same issue.

Deleted opl folder but this time with previous build and changed to same settings and it worked the time, tried new build with the opl cfgs created by previous build and it worked.

Backed up opl folder and deleted tried new build with expectation of the issue reoccurring to compare the contents of the opl folder, however this time it worked (took 5 clean attempts overall)

So for some reason it must be an issue when creates the opl folder cfg files. Not sure what or how it triggers as everytime I started from scratch I did everything the same way
 
Strange. I know I have the black screen right after changing the config and going to games list but a reboot fixes that. Actually this version works better than last for me. Was able to launch GT4 ISO. Are you using ZSO format? That still doesn't work for GT4 for me.
 
I tested the new version, I can report that doing the game reset still freezes the console, have to shutdown the console
I deleted the OPL folder from my MC so the new version created a new one
After saving the settings for the first time, when going to the games list, OPL gave a black screen. After shutting down the PS2 and launching OPL again the games showed up
 
I tested the new version, I can report that doing the game reset still freezes the console, have to shutdown the console
I deleted the OPL folder from my MC so the new version created a new one
After saving the settings for the first time, when going to the games list, OPL gave a black screen. After shutting down the PS2 and launching OPL again the games showed up

Yes I had issue with black screen after enabling bdm hard drive, and showed on reboot.

However igr using L1,L2,R1,R2,Start and select reboots fine for me
 
Yes I had issue with black screen after enabling bdm hard drive, and showed on reboot.

However igr using L1,L2,R1,R2,Start and select reboots fine for me
Maybe is it my PS2?, I have a Matrix chip all games freeze for me when doing that button combo
UPDATE
I went back to use the .1 version and the .0 one and the IGR works fine and takes me back to the FMCB menu
The latest 2 releases don't work for me
 
Last edited:
Just wiped the 1TB Seagate clean and turned it back to GPT. Copying 300GB over and will boot it up with the new build once its done.
I'll edit this post accordingly ...

EDIT: First boot up with build 1986 gave me a clean OPL config. I'd learn why momentarily.

The only options I changed were ...
Remember Last Game Played -- Yes (Autostart 0)
BDM Start Mode -- Auto -- Block Devices -- HDD Only
Display Mode -- 1920x1080i

Went to save ... "Config Saved To MC1" (my MC0 is flaking out) ...
Pressed Circle. Instant black screen and freeze with that underline status bar at bottom of the screen half way across ...

Power cycled and relaunched build 1986 ... and my HDD showed up! Also, the config on MC0 got loaded because BDM for iLink and MX4SIO was enabled when I didn't enable them on first boot. Tweaked it further by disabling HDD, ETH, and APPS Start mode to "Off" and all BDM devices off except for USB and HDD, and I'm getting no freezes, black screens, and lockups!

Nice work, Ryan! ;)
 
Last edited:

Similar threads

Back
Top