Recalbox reset itself to default, all settings and roms gone?

[Substring]

@T33Hud so, still around for'some tests ?

[T33Hud]

@Substring absolutely

[Substring]

@T33Hud Well time to sleep now

[Substring]

@T33Hud Can you run /recalbox/scripts/recalbox-part.sh "share_internal" and confirm it replies /dev/mmcblk0p8 ?

[T33Hud]

@Substring I'm not showing that script on my system:

/recalbox/scripts/recalbox-part.sh "share_internal"
-sh: /recalbox/scripts/recalbox-part.sh: No such file or directory

..
cd recalbox
cd scripts
ls-a -a
. 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

[Substring]

@T33Hud d**n, i checked on a 4.1, i thought the script was the same in 4.0 ... wait a sec

[Substring]

@T33Hud all apologies, i let you down

So, can you run /recalbox/scripts/recalbox-mount.sh "ext4" 1 "/dev/mmcblk0p8" /recalbox/share and give me your output please ?

[T33Hud]

@Substring Not sure how you let me down? It's amazing to have help with this!

Here are my results:

cat /boot/recalbox-boot.conf
internal=/dev/mmcblk0p8
sharedevice=INTERNAL

/recalbox/scripts/recalbox-mount.sh "ext4" 1 "/dev/mmcblk0p8" /recalbox/share
mount: mounting /dev/mmcblk0p8 on /recalbox/share failed: Invalid argument

[Substring]

@T33Hud weiiiiird ... Can you ls -l /dev/mmc* ?

[T33Hud]

@Substring

ls -l /dev/mmc*
brw-rw---- 1 root disk 179, 0 Jan 1 1970 /dev/mmcblk0
brw-rw---- 1 root disk 179, 1 Jan 1 1970 /dev/mmcblk0p1
brw-rw---- 1 root disk 179, 2 Jan 1 1970 /dev/mmcblk0p2
brw-rw---- 1 root disk 179, 5 Jan 1 1970 /dev/mmcblk0p5
brw-rw---- 1 root disk 179, 6 Jan 1 1970 /dev/mmcblk0p6
brw-rw---- 1 root disk 179, 7 Jan 1 1970 /dev/mmcblk0p7
brw-rw---- 1 root disk 179, 8 Jan 1 1970 /dev/mmcblk0p8

[Substring]

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

[hobbitlap]

i know the is pretty old topic, but i got the same issue twice with different sd card and pi 3b.
habe you found the issue ?
i am on 4.1 beta !!

[OyyoDams]

@hobbitlap Hi,

First of all why don't you install the latest stable version ? I'm not sure you'll get support for the outdated beta version.

[ChickenW]

I'm running into the same exact problem.
with the last release (4.1.0).
each time i restart my Pi, all settings are back to default (except for the overscan param) and all the roms vanish from the storage.
Plus when i add roms, they don't appear in the liste, and there is no more "update game liste" button available anywhere in the menu.

[BlingTyson]

@chickenw said in Recalbox reset itself to default, all settings and roms gone?:

I'm running into the same exact problem.
with the last release (4.1.0).
each time i restart my Pi, all settings are back to default (except for the overscan param) and all the roms vanish from the storage.
Plus when i add roms, they don't appear in the liste, and there is no more "update game liste" button available anywhere in the menu.

Same Issue with a fresh install trough NOOBS on a new Pi3... Any help ?

[Javier Sandoval]

i notice i had the same issue once but on pcx64, on the options for the share drive, just change it once to something ealse, reboot, then change it once again to internal and reboot, problem gone.

[jamalwsilva]

Fixed with "fsck /dev/mmcblk0p2".

Change mmcblk0p2 to your actual userdata partition. And use it with care... Some data may be lost.