RetroPie will give you an LBS error trying to resize on boot with retropie 4.4 with berryboot. It will also not allow you to resize it from retropie raspi-config nor while you have retropie booted and using the command line.

If you are using berryboot with retropie you will need to reboot the pie and do this from berryboots terminal via the berry boot menu with ctrl + alt + F2. I was able to resize an image I took of a 16G SD card written to a 64G card and resize it to expand all available space to the SD.

Links~
https://raspberry-projects.com/pi/pi-operating-systems/raspbian/troubleshooting/expand-filesystem-issues
https://www.chrisnewland.com/resize-raspberry-pi-sd-card-partition-to-fill-32gb-card-from-a-running-raspberry-pi-245

I cannot take credit for this, but will link what helped me after I spent a few hours trying to figure it out. Back up your SD pay no attention to drive space numbers in the examples below.

Backup your SD card to an image file first!

Enter this to see the current partition usage:
df

E.g.
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 3698504 3351472 146524 96% /
/dev/root 3698504 3351472 146524 96% /
devtmpfs 494800 0 494800 0% /dev
tmpfs 99820 240 99580 1% /run
tmpfs 5120 0 5120 0% /run/lock
tmpfs 199620 0 199620 0% /run/shm
/dev/mmcblk0p1 57288 19400 37888 34% /boot

The rootfs and /dev/root is the same thing, its just a debian thing the have them both appear as separate

Enter this:
sudo fdisk /dev/mmcblk0

Then press 'p' to see the current partitions on the disk. E.g.

Disk /dev/mmcblk0: 7860 MB, 7860125696 bytes
4 heads, 16 sectors/track, 239872 cylinders, total 15351808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa6202af7
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 8192 122879 57344 c W95 FAT32 (LBA)
/dev/mmcblk0p2 122880 15351807 7614464 83 Linux

Now delete the 2nd partition (it won't actually delete the data on it)
Press 'd' > Enter
Press '2' > Enter

Now re-create it:
Press 'n' > Enter
Press 'p' > Enter
Press '2' > Enter

Enter the First sector and the same value as the original /dev/mmcblk0p2 partition (122880 from the above example).

For the Last sector just press enter to use the maximum value.

Now press 'p' > Enter to see the new partition setup.
Finally press 'w' > Enter to write it

Now reboot:
sudo shutdown -r now

Once its back do the resize:
sudo resize2fs /dev/mmcblk0p2

This may take a little while to complete…

Now enter the command
df

and hey presto, you've expanded to use all the space :-)

Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 7513804 3352360 3810208 47% /
/dev/root 7513804 3352360 3810208 47% /
devtmpfs 494800 0 494800 0% /dev
tmpfs 99820 240 99580 1% /run
tmpfs 5120 0 5120 0% /run/lock
tmpfs 199620 0 199620 0% /run/shm
/dev/mmcblk0p1 57288 19400 37888 34% /boot

@mitu
Well I tried running sudo ./RetroPie-Setup/retropie_setup.shand I tried to scrape using all of the websites but it kept showing data not found. I tried every single website and it kept saying data not found. Nothing was scraped even after I tried twice.

I still don't understand whats wrong. It keeps failing no matter what.

...

@mitu Thats where i looked, its gone-vanished of the face of the earth, hope the setup script fixes it

Thanks! I just figured out I could do file sharing and I'm currently copying the file to my desktop as I type. Thank you!!!!

@tr3v0r If you're just a beginner, then I suggest you use RGUI and the auto-configuration produced for RetroArch and don't edit any files.
Use the 'Core input remapping' (see docs) to change the RetroPad controls.

In my case, it was because I registered the PS3 dualshok controls, using the xbox360 driver ... In emulationstation it works ... But in RetroArch it does not.
The solution was: uninstall the xbox360 driver and re-activate the ps3 dualshock official driver, when rebooting ... Resigne the buttons in emulationstation, I recognized as ps3 dualshock command and I work the retroarch controls in all the emulators.

Oh, wait I understand now - I didn't realize each of these items in the lists were, themselves, subfolders containing the ROMs. The theme I was using, Eudora, didn't give any indication that the subfolders were different from the ROMs, and since that made the menu look buggy to me, I didn't want to test the "buggy ROM." The moment I switched to Carbon, the difference was obvious. A simple click would have answered all my questions.

I feel very sheepish, you'd think I'd never used a computer before. But you helped me work it out, and thank you for that!

@ProjectMars Did you save a game preset/override with these settings ? Check in \\retropie\configs\all\retroarch\config if you have any game override saved and delete the file.

@johnsorger6 How did you create the 7z archive ?
Can you run with verbose logging enabled and post the contents of the log file /dev/shm/runcommand.log on pastebin.com so we can take a look at what errors appear ?

If your ROMs are on the sdcard and your RetroPie installation is functional, just copy them over to your PC via File Shares or other transfer methods.

@dudleydes Thanks, I've already made the two new systems by making custom collections. but I need to remove the old ones. It looks like Emulation Station doesn't allow you to remove a system from the carousel. If I remove them in the es_systems.cfg, the roms they are attached to also disappear from the collection.

It used to be that you could do this - https://retropie.org.uk/forum/topic/10849/create-a-custom-es-system-able-to-launch-games-for-many-systems -
but collections are the new hotness.

you edit the config.txt file with some of these settings:

https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

@StarshipKnight That's a generic error message when the compilation (and the follow-up installation) fails. You'll find the detailed error message in the ~/RetroPie-Setup/logs folder, in the most recent log file.

@mitu Ah, that would explain why it worked during my last install, but not now. Updating all the core packages at once seemed to ignore the fact that there was a newer version of ES and left me on 2.7.5, so I updated that individually, which put me on 2.7.6, and everything works like it used to now. Thanks for your help there! You've saved me tearing my hair out looking for something I would never would have found by myself! :)

@tubewayarmy and use a topic that summarises the issue - not "Noobie".

@boomspar Generally BIOS and ROMs are not provided by RetroPie unless there's free/open source. That's why the BIOS requirements are always mentioned on the emulator's page. Just like for ROMs, you're responsible for copying the necessary BIOS files in place - they don't come with the package installed from the RetroPie-Setup.

@Earthboundfan15 Please add more info about your system as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

It depends how many roms you have and how many of them are part of the current mame set 0.201+202 if Progetto or scraping will be better. But a good option nonetheless.