Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USB ROM Copy on PI 2 Running Version 3.4 #1211

Closed
taylorbat opened this issue Jan 28, 2016 · 15 comments
Closed

USB ROM Copy on PI 2 Running Version 3.4 #1211

taylorbat opened this issue Jan 28, 2016 · 15 comments

Comments

@taylorbat
Copy link

In order to automate the ROM transfer process I have created a USB thumb drive with all of my ROMs in the correct folder structure. In previous versions after expanding the file system, restarting, and then inserting the USB drive the system would begin copying the ROMs within about 15 or 20 min. In this current version it appears that the ROMs will copy in the beginning of the reboot process for a few minutes and then stop. Currently the only way to transfer the entire USB drive of games is to restart the entire system over and over until all games have been transferred. Is anyone else having this issue? Has the USB ROM file transfer process changed in this version?

@joolswills
Copy link
Member

I have heard others mention it on the forum. Nothing has changed in our scripts, so it must be related to the underlying os. Possibly something has changed in usbmount.

@taylorbat
Copy link
Author

The last time this worked for me it worked on 3.3.1 wheezy, I dont have a copy of 3.3.1 jessie to test it.

@joolswills
Copy link
Member

I have replicated the problem. The problem is caused by systemd on Jessie killing the script - need to look into disabling the timeout

Feb  5 07:47:51 retropie usbmount-01_retropie_copyroms-[935]: Attempting to create directory structure for ROMS in '/media/usb0/retropie/roms' ...
Feb  5 07:47:54 retropie usbmount-01_retropie_copyroms-[935]: Syncing roms ...
Feb  5 07:47:54 retropie usbmount-01_retropie_copyroms-[935]: Syncing configs ...
Feb  5 07:48:20 retropie systemd-udevd[848]: timeout: killing '/usr/share/usbmount/usbmount add' [878]
Feb  5 07:48:20 retropie systemd-udevd[848]: '/usr/share/usbmount/usbmount add' [878] terminated by signal 9 (Killed)
Feb  5 07:48:39 retropie kernel: [   83.214594] usb 1-1.4: USB disconnect, device number 6
Feb  5 07:48:39 retropie systemd-udevd[1040]: inotify_add_watch(6, /dev/sda, 10) failed: No such file or directory
Feb  5 07:48:39 retropie usbmount[1044]: executing command: umount -l /media/usb0
Feb  5 07:48:39 retropie kernel: [   83.493965] FAT-fs (sda1): unable to read boot sector to mark fs as dirty
Feb  5 07:48:39 retropie usbmount[1044]: executing command: run-parts /etc/usbmount/umount.d

@joolswills
Copy link
Member

@joolswills
Copy link
Member

Looks like a problem in the way usbmount is implemented and we may need to use another mechanism for this - which is rather annoying as it all worked before systemd.

@joolswills
Copy link
Member

@joolswills
Copy link
Member

@joolswills
Copy link
Member

the correct way is to launch a systemd service - the "fixed" usbmount doesn't work either as it get killed by udev still. I am going to have to disable the non working usbmount for now until we can roll our own working solution that uses udev + systemd service. usbmount is just broken by design unfortunately

@joolswills
Copy link
Member

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774149 - contains working systemd service we can use

@joolswills
Copy link
Member

I have implemented a hopefully working usbmount for jessie now

please update retropie-setup and then go to the setup menu and choose to enable the usbromservice again. it should go and grab/build a package, and hopefully then it will work.

@bernd69
Copy link

bernd69 commented Feb 5, 2016

Problem solved. Sorry.

Thanks and best regards
Boern

@joolswills
Copy link
Member

did you update retropie-setup first?

The changes have been tested by two people so I'm pretty sure they work, so let's debug it before you downgrade :)

@joolswills
Copy link
Member

it doesn't use an empty stick btw,. you need to make a "retropie" folder first in the root.

@bernd69
Copy link

bernd69 commented Feb 5, 2016

Sorry. Forget it. I have two Sandisk stick which are the same. One is formatted with Mac OSX. I´ve scrambled them ...

Thanks, Bernd

@HerbFargus
Copy link
Member

Issue should be resolved now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants