Pi 4 + Running ROMS from USB stick
-
Hi all so ill give as much info as I know.
Downloaded Retopie Thursday last week so I think it's the latest (4 6.?) version.
I have a Pi 4 B 4gb
SanDisk 128gb USB 3.0
I've followed the auto guide formatted the USB thumb drive as FAT32 and added the folder retropie-mount. Made sure usbservice is installed and enabled in optional packages.
Whilst on the emulationstation menu I plug in the USB drive push Start - Quit - Reboot Machine
It runs through the usual black screens full of writing but then it stops with an error about admin permissions?
Can anyone shed any light on where I'm going wrong?
Thank you
-
@Chapster5 said in Pi 4 + Running ROMS from USB stick:
Whilst on the emulationstation menu I plug in the USB drive push Start - Quit - Reboot Machine
Why ? You don't need to reboot the system and you should at least waited for the
usbromservice
to copy your existing ROMs/BIOS to the USB.It runs through the usual black screens full of writing but then it stops with an error about admin permissions?
What does the error say, exactly ?
-
@mitu thanks for the reply
Does it display anything to the screen whilst copying? I didn't see anything and in the guide it says you may need to reboot. I don't know what to expect or when to know it's done. If I remove the USB it boots just fine to emulation station.
The error says
"You are in emergency mode. After logging in, type" journalctl - xb" to view system logs, "systemct1 reboot" to reboot, "system to default" or "exit" to boot into default mode.
Cannot open access to console, the root account is locked. See sulogin(8) man page for more details.
Press enter to continue. "
-
@Chapster5 said in Pi 4 + Running ROMS from USB stick:
Does it display anything to the screen whilst copying? I didn't see anything and in the guide it says you may need to reboot
No, there's no progress displayed, unless your USB stick/disc has an activity led which you can use to track the copying.
"You are in emergency mode. After logging in, type" journalctl - xb" to view system logs, "systemct1 reboot" to reboot, "system to default" or "exit" to boot into default mode.
Try removing the USB stick, then type the command for reboot (
systemctl reboot
). -
@mitu thank you. I've restarted and plugged the USB into my laptop and seems it's started building the folder hierarchy inside the folder I created. Guess I'll leave it for a few hours and hope it finishes unfortunately I don't have an activity led on the USB stick so it's a guessing game 😂👌
-
@Chapster5 You don't have to reboot. Once the copying finishes, it will automatically set up the ROMs/BIOS/etc. folder from the USB. Just don't add something new right now, since it might not get copied.
-
@mitu perfect if I have to turn off before it's finished copying will this corrupt anything? Will it continue where it left off copying?
-
@Chapster5 You should leave it on to finish the copying.
-
@mitu OK so I plugged it back in last night left it overnight to do its thing checked on the laptop this morning and it's not copied anything across from when I last checked it, should i just format the stick again and start again?
-
Did you leave it to finish copying the first time ? If no, reformat and try again.
-
@mitu more than likely a no I took it out after about 3 minutes haha so it's not had a chance to do anything I'll reformat and try again thank you :)
-
@mitu OK so, I've started a fresh with the USB device. Formatted as FAT32 created the retropie_mount folder. Plugged it in whilst on the enulationstation menu screen. Waited around 12/18h just to be sure. Unplugged it from the pie put it into my laptop and checked the file structured had been created and files copied. That was all OK. Turn the pie off plugged it back in switched the pie on and it stops on the inital startup black screens with the following message
Any thoughts I've pushed enter and it just repeats itself.
-
@Chapster5 Did you modify the
/etc/fstab
file to mount the stick ? It's not needed if you use theusbromservice
. -
@mitu I have the usbromservice installed an ld enabled. Unless I have to modify that file aswell?
-
@Chapster5 No, you shouldn't, but for some reason the boot process stops because of the USB stick.
Can you remove the stick, see if your system boot, then run the following commands on the command line and post the output:sudo lsblk -zf cat /etc/fstab cat /boot/cmdline.txt
-
@mitu boots just fine without the USB in here's the commands you asked me to run
-
The
fstab
seems fine. To get access to the system when the error occurs, you should set theroot
password:sudo su passwd # enter the new password for user "root"
Then insert the USB stick and - when you get the boot error - you should be able to access the console and run
journalctl -xb
to view the logs. -
@mitu I apologise in advance for app the links I don't know how to copy and paste to a paste bin dump site so there's a lot of mention of not being able to find a clock then it mentioned the file system a but further down failing to mount it.
https://ibb.co/Nx9YB72
https://ibb.co/ZgQhLTh
https://ibb.co/h7DFwzF
https://ibb.co/Trp6YSg
https://ibb.co/60g8VTx
https://ibb.co/VYwgQC7
https://ibb.co/19Z9Trd
https://ibb.co/W2kq5K1
https://ibb.co/F65G27J
https://ibb.co/D19f10z
https://ibb.co/H4SCX3Y
https://ibb.co/Bg4bphR
https://ibb.co/F6VzQS0 -
Ha, that was interesting, no need to apologize. The error is in the following picture:
Seems like the 1st USB disk partition is mistakenly mounted as
/boot/
(well at least tried to mount), instead of the actual/boot
partition on the SDcard. I wonder if the card and the/boot
partition have the samePARTITION_UUID
.As a workaround, modify
/etc/fstab
and, instead ofPARTUUID=9b2d5bc6-01 /boot vfat defaults 0 2
write
LABEL=boot /boot vfat defaults 0 2
You'll have to use
sudo nano /etc/fstab
and edit the file. Make sure you're not adding any extra chars or erasing something else, it's a sensitive file.
After saving the file, reboot with your USB stick inserted.If everything works ok, then run the following command and post the output (the USB stick must be present):
blkid
-
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.