Cant get Retro Pi to run Roms from USB

[muffinlockdown]

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.

[hydraulix]

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.

[muffinlockdown]

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

[InsecureSpike]

I’ll post a guide ove the next few days

[muffinlockdown]

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

[InsecureSpike]

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

(saves me writing a guide)

[muffinlockdown]

Cheers ill try when i get home :)

[muffinlockdown]

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

[InsecureSpike]

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

[muffinlockdown]

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

[InsecureSpike]

sudo blkid

[muffinlockdown]

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

[muffinlockdown]

for some reason drive 2 does not have a PARTUUID?

[InsecureSpike]

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?

[muffinlockdown]

fat32 or something fat

[InsecureSpike]

can you also posy up the UUID numbers from
sudo blkid

[muffinlockdown]

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

[InsecureSpike]

thats fine i just need the UUID number

[muffinlockdown]

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

[InsecureSpike]

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

[muffinlockdown]

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

[InsecureSpike]

ok, thanks mate, you too

[muffinlockdown]

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

[InsecureSpike]

is that the full UUID number?

[muffinlockdown]

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”

[InsecureSpike]

sorry, double post

[InsecureSpike]

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)

[muffinlockdown]

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

[muffinlockdown]

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.

[InsecureSpike]

pls check spelling of label

[muffinlockdown]

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.

[InsecureSpike]

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

[muffinlockdown]

This is the code i have put in so far

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

[InsecureSpike]

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

[muffinlockdown]

it would not let me

Also issue with usb or linux?

[Author]

Posts