briangilbertParticipant03/25/2016 at 06:09Post count: 3
I have a piDrive on a rPI3:
and have followed the steps at:
To try and make the retropie image boot directly from the hard drive, but the resizing script just ran forever (4hours until I killed it)
After rebooting I see the retropie boot screen, but after that I’m thrown to a prompt.
df shows the following:
Filesystem 1K-blocks Used Available Use% Mounted on /dev/root 2371536 2284240 0 100% / devtmpfs 372268 0 372268 0% /dev tmpfs 376588 0 376588 0% /dev/shm tmpfs 376588 5296 371292 2% /run tmpfs 5120 4 5116 1% /run/lock tmpfs 376588 0 376588 0% /sys/fs/cgroup /dev/mmcblk0p1 129776 21046 108730 17% /boot /dev/sda1 58234 19952 38282 35% /media/usb1
I’m hoping someone may be able to help me figure out how to get this working?InsecureSpikeParticipant03/25/2016 at 14:01Post count: 571
but I’d probably stay away of doing that way, as if you develop a fault in you file system, you’ll need to probably start all over again.
I’d suggest just running your roms from your pi drive!briangilbertParticipant03/26/2016 at 06:29Post count: 3
I ended up using one of the Multo Boot Pi images:
So your suggestion to just run the roms from the drive seems a much simpler way to do it.. What would be the recommended way to direct the emulators to look there for them?InsecureSpikeParticipant03/26/2016 at 10:01Post count: 571
edit the es_systems.cfg
sudo nano /etc/emulationstation/es_systems.cfg
edit these bits… <path>/home/pi/RetroPie/roms/amiga</path>
i would also move it to
so as updates won’t write over itbriangilbertParticipant03/28/2016 at 00:36Post count: 3
- The forum ‘New to RetroPie? Start Here!’ is closed to new topics and replies.