Cant get Retro Pi to run Roms from USB

Tagged: Usb retropie games roms

This topic has 37 replies, 4 voices, and was last updated 8 years, 2 months ago by muffinlockdown.

Viewing 35 posts - 1 through 35 (of 38 total)

1 2 →

Author

Posts
02/19/2016 at 22:56 #117556

muffinlockdown
Participant

I have just downloaded the latest Retro Pi and it refususes to run roms from usb no matter what i have tried.

When into each individual rom folder
And edited the cfg setting for the path to run from usb and not sd but cant get it working got a rpi2.
Tried multiple usbs thinking it may be the uusb.

My pi i filling up with games and dont know how to run roms from usb

Already enabled rom service in Retropie-setup.

Any help appreciated.

02/19/2016 at 23:23 #117558

hydraulix
Participant

The rom service will use your usb to copy games from it to the SD card.

If you can detail out the commands your using to find your usb and mount it to a folder, I can help you out with getting them running directly from the usb.

02/19/2016 at 23:42 #117560

muffinlockdown
Participant

Cd /Media/usb0
Ls

But just recently its not reading the usb on start up it was having a failed message after the retro pi load up

And when doing the above commmand it does not find the usb

02/20/2016 at 01:45 #117562

InsecureSpike
Participant

I’ll post a guide ove the next few days

02/20/2016 at 03:50 #117564

muffinlockdown
Participant

Thank you everyone,
When i get home ill send throught the directory instructions which i try to get into it with..

Kind Regards
The Muffin Man

02/20/2016 at 09:54 #117575

InsecureSpike
Participant

here, https://ccollins.wordpress.com/2013/02/04/how-to-mount-usb-disks-on-linux/

(saves me writing a guide)

02/20/2016 at 10:11 #117577

muffinlockdown
Participant

Cheers ill try when i get home :)

02/20/2016 at 23:16 #117614

muffinlockdown
Participant

okay so when i have the folder on my USB called retropi on the front it does not ready my usb but when i move it is allows me to see my usb?

on the start of set up everytime that i have a usb in i get an error
[FAILED] Failed to start
See ‘systemctl Status ‘ for details

02/20/2016 at 23:46 #117617

InsecureSpike
Participant

ok post up what sudo blkid prints out

and I’ll write a guide as it looks as if some info from that guide is missing

02/20/2016 at 23:47 #117620

muffinlockdown
Participant

also step 1 can not be done on the retro pi 3
blkid does not work it just does nothing
and all the drives are sd1 at the time of connection
there is no sd 1-5 or anything like that

02/20/2016 at 23:52 #117621

InsecureSpike
Participant

sudo blkid

02/20/2016 at 23:57 #117622

muffinlockdown
Participant

there is
/dev/sdb1 : LABEL= “TITLE OF DRIVE1 ” UUID” numbers ” TYPE ” VFAT pART id:”numbers”
/dev/sdb1 : LABEL= “TITLE OF DRIVE2 ” UUID” numbers ” TYPE ” VFAT pART id:”numbers”

HMMMMMM i didnt try doing that before and doing

sudo

and

blkid

before

02/21/2016 at 00:00 #117623

muffinlockdown
Participant

for some reason drive 2 does not have a PARTUUID?

02/21/2016 at 00:00 #117624

InsecureSpike
Participant

ok, I have to go to work now, I’ll get a guide set up, do you no what format the USB drive is formatted to?

02/21/2016 at 00:04 #117625

muffinlockdown
Participant

fat32 or something fat

02/21/2016 at 00:13 #117626

InsecureSpike
Participant

can you also posy up the UUID numbers from
sudo blkid

02/21/2016 at 00:18 #117630

muffinlockdown
Participant

also when i try and edit the fstab file i get an access denied page
tried running in administrator same thing happens

Permission denied.
Error Code 3
Error message from server : permission Denied

02/21/2016 at 00:21 #117632

InsecureSpike
Participant

thats fine i just need the UUID number

02/21/2016 at 00:27 #117636

muffinlockdown
Participant

Hmm is uuid compramise any think with security of the device?

02/21/2016 at 00:29 #117637

InsecureSpike
Participant

no, its just a unique number for that drive, like a finger print, its fine to post up

02/21/2016 at 01:13 #117641

muffinlockdown
Participant

Okies will post when return home have a good day at work

02/21/2016 at 01:29 #117642

InsecureSpike
Participant

ok, thanks mate, you too

02/21/2016 at 11:39 #117665

muffinlockdown
Participant

/dev/sda1: LABEL=”16GB1″ UUID=”08D4-47E3″ TYPE=”vfat”

02/21/2016 at 12:05 #117666

InsecureSpike
Participant

is that the full UUID number?

02/21/2016 at 12:20 #117668

muffinlockdown
Participant

Yes it is all the “UUID”
thats copy paste from retro pi terminal after “sudo blkid”

Again when i have the folder “retropi” on the local dir of the usb [main directory] it does not allow me to be able to see its content.

when I use the below i cant see the files when i try the see LS
“cd /media/usb0” 0-7 (tried all of them)
“ls”

02/21/2016 at 12:21 #117669

InsecureSpike
Participant

sorry, double post

02/21/2016 at 12:22 #117671

InsecureSpike
Participant

1) sudo e2label /dev/sda1 USBdrive

2) sudo mkdir /media/sda1 USBdrive

3) sudo nano /etc/fstab (to make Linux automate this process for you)

UUID=08D4-47E3 /media/USBdrive vfat defaults 0 2

(so it looks like the image I’ve attached, taking into account i have 2)

[attachment file=”Screen Shot 2016-02-21 at 11.12.16.png”]

ctrl + X to save

4) sudo mount -a (This will mount all file systems listed in the /etc/fstab configuration file)

02/21/2016 at 12:27 #117674

muffinlockdown
Participant

pi@retropie:/ $ sudo e2lable /dev/sda1 USBdrive
sudo: e2lable: command not found

02/21/2016 at 12:31 #117675

muffinlockdown
Participant

Corrected the spelling of “e2label”
and below comes up

pi@retropie:/dev $ sudo e2label /dev/sda1 USBdrive
e2label: Bad magic number in super-block while trying to open /dev/sda1
Couldn’t find valid filesystem superblock.

02/21/2016 at 12:32 #117676

InsecureSpike
Participant

pls check spelling of label

02/21/2016 at 12:34 #117677

muffinlockdown
Participant

spelling corrected

Message which comes up
pi@retropie:/dev $ sudo e2label /dev/sda1 USBdrive
e2label: Bad magic number in super-block while trying to open /dev/sda1
Couldn’t find valid filesystem superblock.

02/21/2016 at 12:44 #117679

InsecureSpike
Participant

ok, looks like you’ll need to repair your damaged “superblock” now I’m not sure how to do this, so you’ll need to google

Bad magic number in super-block while trying to open /dev/sda1

02/21/2016 at 12:44 #117680

muffinlockdown
Participant

This is the code i have put in so far

pi@retropie:/dev $ cd ..
pi@retropie:/ $ ls
bin dev home boot etc lib media pi@retropie:/ $ cd dev
pi@retropie:/dev $ ls
autofs loop1 block loop2 bsg loop3 btrfs-control loop4 bus loop5 cachefiles loop6 char loop7 console loop-control cpu_dma_latency mapper cuse mem disk fb0 mmcblk0 fd mmcblk0p1 full mmcblk0p2 fuse mqueue gpiomem net hidraw0 hidraw1 hwrng null initctl ppp input ptmx kmsg pts log ram0 loop0 ram1 pi@retropie:/dev $ ^C
pi@retropie:/dev e2label: Bad Couldn’t pi@retropie:/dev $ lost+found mnt proc run srv tmp var
opt root sbin sys usr
ram10 snd tty26 tty48 uinput
ram11 stderr tty27 tty49 urandom
ram12 stdin tty28 tty5 vc-cma
ram13 stdout tty29 tty50 vchiq
ram14 tty tty3 tty51 vcio
ram15 tty0 tty30 tty52 vc-mem
ram2 tty1 tty31 tty53 vcs
ram3 tty10 tty32 tty54 vcs1
ram4 tty11 tty33 tty55 vcs2
ram5 tty12 tty34 tty56 vcs3
memory_bandwidth ram6 tty13 tty35 tty57 vcs4
ram7 tty14 tty36 tty58 vcs5
ram8 tty15 tty37 tty59 vcs6
ram9 tty16 tty38 tty6 vcsa
random tty17 tty39 tty60 vcsa1
raw tty18 tty4 tty61 vcsa2
network_latency rfkill tty19 tty40 tty62 vcsa3
network_throughput sda tty2 tty41 tty63 vcsa4
sda1 tty20 tty42 tty7 vcsa5
sdb tty21 tty43 tty8 vcsa6
sdb1 tty22 tty44 tty9 vcsm
sg0 tty23 tty45 ttyAMA0 vhci
sg1 tty24 tty46 ttyprintk xconsole
shm tty25 tty47 uhid zero
$ sudo e2label /dev/sda1 USBdrive
magic number in super-block while trying to open /dev/sda1
find valid filesystem superblock.

02/21/2016 at 12:46 #117681

InsecureSpike
Participant

also just run commands from the root directory, no need to be in a curtain folder

02/21/2016 at 12:48 #117682

muffinlockdown
Participant

it would not let me

Also issue with usb or linux?
Author

Posts