Eretropie Delete Roms From Usb Drive After Uploading

Running ROMs from a USB drive

Rather than running everything from an SD card, it can be desirable to store and run ROMs from an external USB drive. The benefits of this are as follows:

• Reliability: USB storage tin can be less sensitive to corruption than SD cards.
• Separation of data: In the event that a RetroPie installation becomes corrupted or a new epitome is required, whatsoever ROMs, saves, etc, are not lost. Merely remove the USB stick, re-image the SD menu, re-apply these setup instructions, and all that information is retained.
• Piece of cake ROM transfer: When the system is off, you tin can remove the stick and plug it into any other estimator and easily copy-and-paste ROMs into the right folders.
• Speed: USB transfer speeds can be faster than SD carte transfer speeds (run across Raspberry Pi Benchmarks).
• Cost: USB storage tends to be cheaper than the equivalent microSD menu.
• Capacity: USB storage tin can reach huge capacities, whereas microSD is express.
• Compatibility: microSD cards endure from compatibility issues with Raspberry Pi systems. USB storage devices should mostly all work.

There are a number of means you can achieve this, but the following method is desirable equally it fully integrates the USB drive with the existing directory construction, rather than requiring you to tweak configuration files so RetroPie is looking for ROMs in a different identify. Below there are two ways to accomplish this: an automated method, or a manual method.

Format USB drive

Either on linux, or on a PC, format the USB bulldoze to FAT32 (used in this guide as it is the almost compatible across different operating systems):

• Instructions to format on Linux
• Instructions to format on Windows (diverse)
• Instructions to format on OSX

Automated Mountain (Easiest Method)

Before proceeding, brand sure the usbromservice (Optional packages department) is installed and enabled, especially if you have installed RetroPie manually.

1. Create a folder called retropie-mount on the USB drive
2. Plug into Raspberry Pi
3. It volition continue to automatically copy the RetroPie folder AND all of its contents (yous may demand to reboot to start the copying)

Note: if you have a large ROM collection already on the SD bill of fare information technology volition copy all of the ROMs as well so make certain your USB is big enough. It is easiest if you lot haven't added any roms yet.

Once the folder construction is copied over the USB volition be mounted over the RetroPie binder so any ROMs you add to your Pi will be run off of the USB.

Note: XU4 owners The XU4 and its Bone practice not respond the aforementioned as the Raspberry Pi with Rasbian and it does not provide a way to know when the sync is completed. It is recommended that you permit a decent amount of fourth dimension for the procedure to sync.

Video Tutorial

Manual Mount

After formatting your USB based on the in a higher place footstep:

Disable USB transfer daemon

1. Enter the RetroPie Setup menu within the RetroPie menu in EmulationStation.
2. Select Configuration / Tools.
3. Select usbromservice - USB ROM Service
4. Disable USB ROM Service scripts.

Plug in USB drive

This can be done when the system is powered on.

Transfer the existing RetroPie file construction

This step is mandatory regardless of whether you take whatever roms on your system. RetroPie has a specific directory structure and a number of files required packaged with fifty-fifty empty installations.

Either via SFTP, or using the final (via exiting emulationstation, pressing F4, or remotely using SSH), move the /home/pi/RetroPie folder into your USB stick. The reason for moving the whole folder, and non only /home/pi/RetroPie/roms is that there are other folders, such every bit /home/pi/RetroPie/BIOS, that are worth keeping on the external bulldoze likewise.

To do this via terminal, outset enter the command df to print a listing of the file systems. Example output:

                            pi@retropie:~ $ df Filesystem     1K-blocks     Used Bachelor Employ% Mounted on /dev/root        7318456  3367852   3609928  49% / devtmpfs          372100        0    372100   0% /dev tmpfs             376436        0    376436   0% /dev/shm tmpfs             376436     5424    371012   two% /run tmpfs               5120        4      5116   ane% /run/lock tmpfs             376436        0    376436   0% /sys/fs/cgroup /dev/mmcblk0p1     58234    20476     37758  36% /boot /dev/sda1       30480256 26921632   3558624  89% /media/usb0                          

Wait for an entry on /media/usb0, or like. In our above example:

                            /dev/sda1       30480256 26921632   3558624  89% /media/usb0                          

The important things to annotation down are the mount signal: /media/usb0, and the position on the device tree: /dev/sda1

At present we can move our existing RetroPie folder to our new USB drive. Enter the control:

                            sudo mv -v /home/pi/RetroPie/* /media/usb0/                          

Later on this, the USB directory construction should wait something similar:

                            pi@retropie:~ $ ls /media/usb0 -l total 96 drwxrwxrwx  8 root root 16384 Jun fifteen 00:17 BIOS drwxrwxrwx  3 root root 16384 April 22 17:05 retropiemenu drwxrwxrwx 52 root root 16384 Jun  three 00:11 roms drwxrwxrwx  2 root root 16384 April 13 xvi:xiv splashscreens                          

Configure fstab to automatically mount USB drive

Establish the drive's UUID number past entering the control ls -l /dev/disk/by-uuid/. Example output:

                            pi@retropie:~ $ ls -l /dev/disk/by-uuid/ total 0 lrwxrwxrwx 1 root root 15 Jun 19 21:59 7cc81461-50b9-45a8-a561-fd5c4aa71934 -> ../../mmcblk0p2 lrwxrwxrwx 1 root root 15 Jun 19 21:59 AE51-7D54 -> ../../mmcblk0p1 lrwxrwxrwx 1 root root ten Jun xix 21:59 E44B-FC4E -> ../../sda1                          

sda1 was our device tree position from earlier (the section higher up describes how to find this), so E44B-FC4E is our UUID.

Edit fstab with this command: sudo nano /etc/fstab and add a new line similar the beneath:

                            proc            /proc           proc    defaults          0       0 /dev/mmcblk0p1  /kicking           vfat    defaults          0       ii /dev/mmcblk0p2  /               ext4    defaults,noatime  0       1 # a swapfile is not a swap partition, no line here #   use  dphys-swapfile swap[on|off]  for that UUID=E44B-FC4E  /abode/pi/RetroPie      vfat    nofail,user,uid=pi,gid=pi 0       2                          

...where UUID= the UUID of your drive, and everything else is the same equally the example. Note that each item is tab delimited. If you lot use spaces instead of tabs this will not piece of work.

In the case of errors with ext4 file systems use

                            UUID="XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX" /dwelling/pi/RetroPie ext4 nofail,defaults 0    0                          

In the case y'all want to allow execution of file with fat32 file organisation (E.g : OpenBOR), use

                            UUID=E44B-FC4E  /home/pi/RetroPie      vfat    rw,exec,uid=pi,gid=pi,umask=022 0       ii                          

Restart arrangement

This must be a full restart, not but Emulationstation. When it boots up y'all should meet any ROMs you previously had show upward in Emulationstation.

Transfer ROMs

At present transfer ROMs either directly to the USB drive, or via whatever of the usual methods (aside from using the automatic USB copy, obviously!). Now that the USB drive is mounted direct to home/pi/RetroPie, every fourth dimension this directory is accessed, y'all're actually accessing the USB bulldoze.

mahoneylocatell.blogspot.com

Source: https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/

Share this post