Recalbox reset itself to default, all settings and roms gone?
I'm not exactly sure what happened, my daughter was playing the recalbox I had set up and did not turn it off. When I turned it on again, the system was locked up and not responding via SSH. I had to pull the plug. When the system rebooted all of the roms were gone, the original homebrew roms were back and it didnt recognize my gamepad, essentially it reverted back to the original default install.
Is this SD card corruption? was something triggered when used? I was on the newest build, had just updated via the built in system. Thanks
Still looking for a little help: twice now I've got through the install process, added all my roms, added the pin 56 switch line to the config, added my LED config (dtparam=act_led_gpio=22) to /boot/config.txt ...and both times after a few cold reboots all my changes are gone. Recalbox reverts back to the default rom set and there is no room to add roms to my shared folder. I briefly saw some text flash on the screen but was unable to take a pic, something about ext4... partition problem I guess?
This is on the latest build of Recalbox, Pi Zero, generic Amazon SNES USB controller and a Logitech K400r wireless keyboard / mouse combo.
Anyway if anyone has a suggestion or can see what is causing the problem I would appreciate the help
DjLeChuck last edited by
@T33Hud I'm summoning @Substring
This is maybe a corrupted SD Card yes. It was the same the twice times?
@T33Hud if you could log in (local tty or with SSH) we should check the result of the mount command, looks like your /recalbox/share is in the RAM or some crap like that.
This post is deleted!
@Substring Thanks for looking into this, sorry about the late response:
login as: root
/dev/root on / type ext4 (ro,relatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=120900k,nr_inodes=30225,mode=755)
proc on /proc type proc (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
tmpfs on /tmp type tmpfs (rw,relatime)
tmpfs on /var type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/mmcblk0p6 on /boot type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocha**et=ascii,shortname=mixed,errors=remount-ro)
tmpfs on /recalbox/share type tmpfs (rw,relatime,size=131072k)
Let me know if you were looking for something else
@T33Hud As expected, you share is in RAM :
tmpfs on /recalbox/share type tmpfs
cat /boot/recalbox-boot.ini(i'm not sure about the filename though)
@Substring result of cat /boot/recalbox-boot.conf
@T33Hud d**n, i'll be back home tomorrow, i can't help further for now without a recalbox at hand
@T33Hud so, still around for'some tests ?
@T33Hud Well time to sleep now
@T33Hud Can you run
/recalbox/scripts/recalbox-part.sh "share_internal"and confirm it replies /dev/mmcblk0p8 ?
@Substring I'm not showing that script on my system:
-sh: /recalbox/scripts/recalbox-part.sh: No such file or directory
. moonlight recalbox-usbmount.sh
.. powerswitch.sh rpi-pin356-power.py
bluetoothcontrollers.sh recalbox-config.sh rpi-pin56-power.py
emulatorlauncher.sh recalbox-mount.sh runcommand.sh
essetting.sh recalbox-support.sh splash.sh
generateEmuConfigs recalbox-sync.sh systemsetting.sh
kodilauncher.sh recalbox-upgrade.sh udev-sixpair.sh
@T33Hud d**n, i checked on a 4.1, i thought the script was the same in 4.0 ... wait a sec
@T33Hud all apologies, i let you down
So, can you run
/recalbox/scripts/recalbox-mount.sh "ext4" 1 "/dev/mmcblk0p8" /recalbox/shareand give me your output please ?
@Substring Not sure how you let me down? It's amazing to have help with this!
Here are my results:
/recalbox/scripts/recalbox-mount.sh "ext4" 1 "/dev/mmcblk0p8" /recalbox/share
mount: mounting /dev/mmcblk0p8 on /recalbox/share failed: Invalid argument
@T33Hud weiiiiird ... Can you
ls -l /dev/mmc*?
ls -l /dev/mmc*
brw-rw---- 1 root disk 179, 0 Jan 1 1970 [1;35m/dev/mmcblk0[0m
brw-rw---- 1 root disk 179, 1 Jan 1 1970 [1;35m/dev/mmcblk0p1[0m
brw-rw---- 1 root disk 179, 2 Jan 1 1970 [1;35m/dev/mmcblk0p2[0m
brw-rw---- 1 root disk 179, 5 Jan 1 1970 [1;35m/dev/mmcblk0p5[0m
brw-rw---- 1 root disk 179, 6 Jan 1 1970 [1;35m/dev/mmcblk0p6[0m
brw-rw---- 1 root disk 179, 7 Jan 1 1970 [1;35m/dev/mmcblk0p7[0m
brw-rw---- 1 root disk 179, 8 Jan 1 1970 [1;35m/dev/mmcblk0p8[0m
well, looks like i'd rather connect to your recalbox and check this by myself. But can't do that before Monday 8pm CET. We'd use teamviewer and you'd allow me having fun by SSH. What do you think ? unless you know how to open a port on your router to the recalbox SSH