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

[DjLeChuck]

@T33Hud I'm summoning @Substring
This is maybe a corrupted SD Card yes. It was the same the twice times?

[Substring]

@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.

[T33Hud]

This post is deleted!

[T33Hud]

@Substring Thanks for looking into this, sorry about the late response:

login as: root
root@192.168.0.167's password:
mount
/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

[Substring]

@T33Hud As expected, you share is in RAM :
tmpfs on /recalbox/share type tmpfs

Can you cat /boot/recalbox-boot.ini (i'm not sure about the filename though)

[T33Hud]

@Substring result of cat /boot/recalbox-boot.conf

internal=/dev/mmcblk0p8
sharedevice=INTERNAL

[Substring]

@T33Hud d**n, i'll be back home tomorrow, i can't help further for now without a recalbox at hand

[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.