Largest size micro sd card?
-
There are three pieces of additional information that might come in handy if you use the highly recommended link provided by Rion. First, symbolic linking an external rom folder to where the system already expects to find it (/home/pi/RetroPie/roms) can save you a lot of work in the future due to the es config constantly being rewritten whenever an update is done, or an emulator is added. Also, if you plan to auto-mount a fat32 drive, make sure you add the "vfat" variable to your fstab. At the same time it's important to remember that .sh launch scripts won't function on a fat32 drive unless you add the "exec" variable as well.
So by the example given in that link, you would change:
UUID=18A9-9943 /media/usb auto,users,rw,uid=pi,gid=pi 0 0
to
UUID=18A9-9943 /media/usb vfat auto,users,rw,exec,uid=pi,gid=pi 0 0
Again, other than the symbolic linking, these additions are only if you plan to run your roms folder from an external fat32 formatted USB drive.
-
@mediamogul what if you plan to use a NTFS formatted external HDD? maybe something like the 314GB WD PiDrive?
-
Someone please correct me if I'm wrong, but I believe you'll need to replace "vfat" from my example with "ntfs". According to that particular guide, you might also need to install:
sudo apt-get install ntfs-3g
As far as the exec command for .sh scripts, I don't really know. Just keep in mind that if you can't launch one of the Apple or Amiga emulators, then you will most likely need to add it as you would with fat32.
-
maybe try ext4 it has a faster transfere rate. and is better suited for usage on rpi
RPi 3 - RetroPie + 500gb HDD [consoles] + Razer Onza Tournament
RPi 3 - RetroPie + 32gb USB [computers] + Keyboard
both with AttractMode + FuzzBoxx Layout -
On 2nd thoughts, go with mediamogul et al.'s advice and ignore me :)
I hadn't realised you can't run .sh scripts directly from some file systems. Is that why you explicitly need to mount the drive rather than let it automount? Mediamogul suggests this step may not be necessary for a non FAT32 drive (but I can see it would be easier to explicitly mount if not sure). Hoping someone will say if that's right/wrong, so I understand the issue.
As a sidenote to es_systems.cfg alterations - the config I see is from /home/pi/.emulationstation/es_systems.cfg
This seems to be different from /etc/emulationstation/es_systems.cfg - in my case? This latter one gets updated, while "my one" stays the same. I've been updating it manually - which suits me as mine is somewhat customised. So I haven't realy looked into it, but any thoughts would be appreciated (unless I'm OT ;)).
-
@InsecureSpike said in Largest size micro sd card?:
is better suited for usage on rpi
Very true. It's also the path of least resistance. Auto-mount an external ext4 formatted drive, then symlink a roms folder and RetoPie will never know the difference.
Some Pros & cons of the ones mentioned so far:
ext4
Pros: Fast transfer rate. No additional considerations or setup past the mounting process.
Cons: Limited mostly to the Linux ecosystem, prohibiting general use in Mac/Win.fat32
Pros: Highest compatibility between platforms. Great for sharing between most systems.
Cons: 4GB limit on file sizes. Considerations must be made in setup to allow full compatibility with RetroPie.ntfs
Pros: Excellent compatibility with Windows. Fast transfer rate.
Cons: Considerations must be made in setup to allow full compatibility with RetroPie. -
/opt/retropie/configs/all/emulationstation
-
@chavatar said in Largest size micro sd card?:
I hadn't realised you can't run .sh scripts directly from some file systems. Is that why you explicitly need to mount the drive rather than let it automount?
Auto-mounting will work, you just need to tell the system how to auto-mount it so as to gain the maximum level of compatibilty. The one thing it still will not allow is putting a symlink on the mounted fat32 drive. eDuke32 for example, tries to use a symlink in launching from it's "emulators.cfg" ES menu script. This can be fixed by altering the script to call out to the actual folder it needs (-j/opt/retropie/ports/eduke32/shareware) rather than the symlink that does not exist because it couldn't be created.
...seems to be different from /etc/emulationstation/es_systems.cfg ...I haven't realy looked into it, but any thoughts would be appreciated
I was under the impression that one was a symlink of the other, but if you are customizing it without being affected by updates, then I guess they're different. That's interesting. I'll check it out tomorrow. Hah, or later today I guess. Although I've always subscribed to the notion that "the night belongs to the day before".
RetroPie v4.5 • RPi3 Model B • 5.1V 2.5A PSU • 16GB SanDisk microSD • 512GB External Drive
-
@mediamogul - much appreciated :)
I was under the impression that one was a symlink of the other
So was I, and I'm sure mine's odd in some way, but good to check.
"the night belongs to the day before"
Yang-yin baby! :)
-
@mediamogul said in Largest size micro sd card?:
@chavatar said in Largest size micro sd card?:
I hadn't realised you can't run .sh scripts directly from some file systems. Is that why you explicitly need to mount the drive rather than let it automount?
Auto-mounting will work, you just need to tell the system how to auto-mount it so as to gain the maximum level of compatibilty. The one thing it still will not allow is putting a symlink on the mounted fat32 drive. eDuke32 for example, tries to use a symlink in launching from it's "emulators.cfg" ES menu script. This can be fixed by altering the script to call out to the actual folder it needs (-j/opt/retropie/ports/eduke32/shareware) rather than the symlink that does not exist because it couldn't be created.
...seems to be different from /etc/emulationstation/es_systems.cfg ...I haven't realy looked into it, but any thoughts would be appreciated
I was under the impression that one was a symlink of the other, but if you are customizing it without being affected by updates, then I guess they're different. That's interesting. I'll check it out tomorrow. Hah, or later today I guess. Although I've always subscribed to the notion that "the night belongs to the day before".
@chavatar said in Largest size micro sd card?:
@mediamogul - much appreciated :)
I was under the impression that one was a symlink of the other
So was I, and I'm sure mine's odd in some way, but good to check.
"the night belongs to the day before"
Yang-yin baby! :)
the new location for custom es_systems.cfg etc
/opt/retropie/configs/all/emulationstation
the original is still at
/etc/emulationstation
RPi 3 - RetroPie + 500gb HDD [consoles] + Razer Onza Tournament
RPi 3 - RetroPie + 32gb USB [computers] + Keyboard
both with AttractMode + FuzzBoxx Layout -
Ah, good to know. Thanks Chavatar.
Edit: Sorry... I mean InsecureSpike.
-
@InsecureSpike said in Largest size micro sd card?:
/opt/retropie/configs/all/emulationstation
Cheers. Sorry you had to spell it out (again).
@mediamogul - not sure why you're thanking me ;)
Happy gaming!
-
@mediamogul - not sure why you're thanking me ;)
Lack of sleep.
Although, feel free to keep the thanks and use it throughout the day in lieu of those who forget to say it.
-
@InsecureSpike said in Largest size micro sd card?:
maybe try ext4 it has a faster transfere rate. and is better suited for usage on rpi
Ext4 if you are running an Linux distribution so you can easy read and write to it from you desktop.
Fat32 if you are running Windows.
Just my two cent. :)
-
I followed the directions here based on reading the advice and most things work. However now when I try to start mame4all roms I get issues where every rom errors out in loading stating that it can't find "romx, y, z"... I updated the xml file for the rom locations to /media/usb0/mame-mame4all
To verify that was the issue I moved a few back to /home/pi/RetroPie/roms/mame-mame4all and they started working again. Any thoughts?
-
@ceconl said in Largest size micro sd card?:
I followed the directions here based on reading the advice and most things work. However now when I try to start mame4all roms I get issues where every rom errors out in loading stating that it can't find "romx, y, z"... I updated the xml file for the rom locations to /media/usb0/mame-mame4all
To verify that was the issue I moved a few back to /home/pi/RetroPie/roms/mame-mame4all and they started working again. Any thoughts?
I would read this thread again and then mount the drive permanently using the link I provided. Also read the comments in this thread and in the link I posted.
That should solve your problems.
-
I use a 128GB micro SD...Sandisk Ultra. Works great. I have nearly 200 PS1 games on it
-
http://thecoolstufftobuy.com/largest-sd-card-larger-laptop/ here's an article i found talking about this subject i think it's a 1 Tb Sandisk
-
Because I'm a freak for aesthetics, I backup the fully sorted image to my server and run rsync on the save files to sync them to the server as well. If the SD corrupts, I just have to rewrite the sorted image, and sync saves.
Just another alternative option.
-
I have a 128GB SanDisk Ultra microSDXC UHS-I Card. Works pretty well for me. I went with using the Fat 32 Format tool method for the higher compatibility rate.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.