Sometimes a drive is FAT32, but the PS2 still won't read it because of how the partition table is structured.
Modern operating systems (Windows 10/11, macOS, Linux) often format large USB drives using the GUID Partition Table (GPT). The PS2’s legacy USB stack was designed in the late 1990s and strictly expects Master Boot Record (MBR) partitioning.
The PS2’s USB ports are notorious for being underpowered (USB 1.1, 500mA max). Some modern, high-capacity USB 3.0/3.1 drives draw more current than the PS2 can reliably provide. This can cause the drive to spin up, be detected as a mass: device, but then fail during directory enumeration, resulting in an empty listing.
The Fix:
This paper examines the "mass empty" functionality in UlaunchELF (uLaunchELF), a homebrew file manager/launcher for the PlayStation 2. We define the operation, describe implementation approaches used by homebrew users, analyze risks (data loss, bricked consoles, file system corruption), and provide recommendations and safe procedures for performing bulk deletions or resets while minimizing harm.
A: OPL has a more robust, custom-written USB driver. uLaunchELF uses the older Sony PlayStation 2 I/O Processor (IOP) driver. They are not the same. OPL compatibility does not guarantee uLaunchELF compatibility. You must still use FAT32/MBR for uLaunchELF.
If you are encountering a "mass empty" issue in uLaunchELF (uLE) on your PS2, where the mass: folder (USB drive) appears empty or shows no files even though you know files are present, it is usually due to filesystem or partitioning incompatibility. The PS2 is very picky about USB drives. Here is how to resolve the uLaunchELF mass empty issue: 1. Fix Partitioning (Must be MBR)
The PS2 only reads USB drives formatted with an MBR (Master Boot Record) partition table.
If your USB is GPT, you must use a tool like Rufus on your PC to reformat it, choosing MBR under partition scheme. 2. Fix Filesystem (Must be FAT32) uLaunchELF does not support exFAT or NTFS natively.
Format your USB drive to FAT32. If the drive is larger than 32GB, use a third-party tool like GUIFormat to format it to FAT32. 3. Try "Hot-Swapping" the USB
If the drive is properly formatted but still shows empty, load into uLaunchELF, open mass:/, see it is empty, go back, unplug the USB, and plug it back in. 4. Check for USB Incompatibility
Many USB drives are not compatible with the older USB 1.1 ports on the PS2.
Try a different, preferably older or smaller (e.g., 4GB, 8GB, 16GB) USB flash drive if the first one doesn't work. 5. Update to wLaunchELF ulaunchelf mass empty
Consider using wLaunchELF (a modern fork of uLaunchELF) which includes better USB drivers. 6. Use Correct Files
Ensure the .ELF files you are trying to run are actually in the root of the USB drive (or in a folder you can navigate to) and are not corrupted. To narrow this down, could you tell me: What size is your USB drive? Did you format it to FAT32? Are you using a USB 2.0 or 3.0 drive?
Knowing this will help determine if it's a compatibility issue or just a formatting issue.
ULaunchElf freezes when I access mass when there's a usb in it
Here’s a forum-style post addressing the common issue of uLaunchELF showing “Mass: Empty” when trying to access a USB drive on a PS2.
Title: uLaunchELF says “Mass: Empty” – tried everything, any fix?
Post:
Hey all,
I’m trying to copy some save files from my USB stick to my PS2 memory card, but when I go into uLaunchELF and open mass:, it just says “Empty” even though there are definitely files on the drive.
Here’s what I’ve tried so far:
Still nothing. The USB light flashes when I plug it in, but mass: shows empty.
Is this a compatibility issue with uLaunchELF 4.43a? Do I need a different USB drive, or maybe a special folder structure? I’ve read that some USB sticks just don’t work with the PS2’s old USB 1.1 controller.
Any recommendations on known-working USB drives or a config tweak? Thanks! Sometimes a drive is FAT32, but the PS2
Troubleshooting "Mass: Empty" in uLaunchELF If you are trying to browse your USB drive in uLaunchELF
directory appears empty, it is likely due to a hardware incompatibility or an incorrect drive format. Because the PlayStation 2 uses dated USB 1.1 drivers, it is notoriously picky about modern storage devices. 1. Partition Scheme: MBR vs. GPT
This is the most common cause for modern drives failing to show up. Most new USB sticks and Windows 10/11 formats default to (GUID Partition Table), which the PS2 cannot read. You must reformat the drive using the (Master Boot Record) partition scheme. Use a utility like
to force the drive into "Non-bootable" mode with the "MBR" partition scheme selected. 2. Filesystem Format: FAT32 Only
The PlayStation 2 does not support NTFS, exFAT, or APFS. Your drive must be formatted to Constraint:
Windows cannot natively format drives larger than 32GB to FAT32. For larger drives, use a third-party tool like to ensure it is FAT32 with a 32KB cluster size. 3. Hardware Compatibility
Not every USB stick is compatible with the PS2’s hardware. Drive Speed: Surprisingly, older
drives often work more reliably than high-speed USB 3.0/3.1 sticks. Power Draw:
Large external hard drives (HDDs) often draw more power than the PS2 USB ports can provide. If using a physical hard drive, ensure it has its own external power source. 4. The "Hot Start" Trick
Sometimes the PS2 fails to mount the drive during the initial boot sequence.
Try unplugging the USB drive while on the uLaunchELF main menu, wait a few seconds, then plug it back in before entering the FileBrowser
. This can sometimes force the system to re-scan the ports and detect the "mass" device. Summary Checklist Requirement Partition Scheme (Master Boot Record) Filesystem Preferably Smaller drives (8GB–32GB) have the highest success rates Dumping BIOS - PCSX2 Modern operating systems (Windows 10/11, macOS, Linux) often
The problem of the mass:/ directory appearing empty in uLaunchELF is a common hurdle for PlayStation 2 homebrew users. This issue typically stems from a mismatch between modern storage technology and the aging software drivers of the PS2. The Core Problem: Modern Drives vs. Legacy Software
While modern PCs can read almost any USB drive, uLaunchELF relies on specific, older drivers to interface with the PS2’s USB 1.1 ports. If your drive is formatted or partitioned incorrectly, uLaunchELF will simply show an empty folder instead of your files. 1. Partition Scheme: MBR vs. GPT
This is the most frequent culprit. Modern Windows installations often default to the GPT (GUID Partition Table) scheme for drives. However, the PS2 and uLaunchELF strictly require the MBR (Master Boot Record) scheme.
Solution: Use a tool like Rufus to reformat your USB drive. In the settings, ensure "Partition scheme" is set to MBR and "Target system" is set to BIOS (or UEFI-CSM). 2. File System: FAT32 is Mandatory
Standard uLaunchELF cannot read exFAT or NTFS file systems. While newer forks like wLaunchELF or Open PS2 Loader (OPL) have added limited exFAT support, basic uLaunchELF remains limited to FAT32.
Constraint: For drives larger than 32GB, Windows’ built-in formatter won't offer FAT32. You must use third-party software like GUIFormat or AOMEI Partition Assistant to force FAT32 formatting. 3. Physical Compatibility and Power
The PS2's USB ports provide very little power. High-capacity external hard drives (especially those over 1TB) or newer USB 3.0/3.1 sticks may draw more current than the port can provide, causing the drive to fail to initialize. Troubleshooting: Try a different USB port on the console.
If using a large external HDD, ensure it has its own external power source.
Test with an older, smaller USB 2.0 stick (e.g., 4GB or 8GB), as these have the highest compatibility rates. 4. Software Initialization Bug
Sometimes uLaunchELF fails to load the USB drivers on the first attempt.
The "Re-plug" Trick: Open the mass:/ directory; if it's empty, back out to the main menu, unplug the USB stick, plug it back in, and then re-enter mass:/. This often forces the driver to re-scan the device.
By ensuring your drive is MBR, formatted to FAT32, and physically compatible with the PS2's limited power output, you can reliably resolve the "mass empty" error and begin managing your homebrew files. Multiple USB_mass drives and partitions.txt - GitHub