Forced fsck failed. your system is broken beyond repair

Sylvester · 15 August 2017 03:48

Hi guys,

I have lakka start when i power on my RPi, then when i quit retroarch it boots kodi through openelec.

I followed a guide online and it said i could add lakka to my favourites. so i did, but when i clicked on it today, i got this message:

Forced fsck failed. your system is broken beyond repair Please re-install Lakka

What do i do now?

gouchi · 15 August 2017 08:55

Which tutorial did you follow ? As we don’t support multiboot.

Sylvester · 15 August 2017 14:30

Lakka & KODI Dual Boot

gouchi · 15 August 2017 17:49

According to the article, "“Lakka has now been modified to “Boot-Back” into our KODI system when it exits”. But there is no source about the change ? You should ask the guy what is the change. Maybe RA doesn’t stop well when he switched to Kodi.

mattrix · 15 August 2017 21:45

/storage/.config/autostart.sh

#!/bin/sh
(
until pid=$(pidof retroarch); do   
     sleep 0.5
done

while kill -0 $pid; do
    sleep 0.5
done

reboot {kodi_partition}
) &

Waits for Retroarch to start.
Waits for Retroarch to exit.
Reboots to kodi partition.

As for as I am aware, this is the only way to catch Retroarch exiting? It then uses the standard reboot command which should do a clean reboot right?

I do recall asking quite a while ago somewhere (can’t find post), and this was the only solution at that time.

Sylvester · 16 August 2017 00:14

Thanks for coming over to reply Matt.

I don’t really tinker with my RPi.

What are the steps to getting it back into shape?

gouchi · 16 August 2017 19:27

@mattrix you may try to use ?

systemctl status retroarch
systemctl stop retroarch

mattrix · 17 August 2017 01:44

Thanks @gouchi!

So, I’ll check the status every 0.5 seconds and then if it has stopped, then stop it (to stop auto restart). Then do the reboot.

I looked for a systemctl command that could disable the restart systemd option but doesn’t seem to be way.

Maybe a better way is to use a drop-in.

/storage/.config/system.d/retroarch.service.d/10-restart-to-kodi.conf

[Service]
Restart=on-failure
ExecStopPost=/bin/bash -c '[ $SERVICE_RESULT = "success" ] && reboot {kodi_partition}'

That should also remove the current unwanted behavior of it rebooting if retroarch crashes for some reason.

I just tried this and it works beautifully. I will update my add-on to use this method instead of the current autostart.sh method

@Sylvester I think you’ll need to start from scratch. NOOBS / PINN doesn’t allow simply re-installing one system. You need to reinstall them all. If you boot into KODI, you can make a backup. KODI should also mount the storage partition from Lakka. So, via KODI - you could make a backup of your Lakka settings.

Sylvester · 17 August 2017 03:57

Thanks guys,

So once i get everything set up again, I plan to have Lakka as the first thing that boots, is that okay?

But I’ll set it up so it exits to Kodi. But then how do I make a backup like previously mentioned?

::EDIT:: Oh I see, you need to update the NOOBS companion

mattrix · 17 August 2017 03:59

Just do everything the video says (like you did originally).

To make it boot to Lakka, use the “Set Default Boot” in NOOBS Companion context menu on Lakka item.

The addon has been updated, so when you start fresh, you will get the updated add-on with the new “Boot-back” method which hopefully means you won’t get the same error ever again (unless you do a sudden power loss).

DudRodriguez · 27 March 2018 14:46

Hello friends, nice to meet you from Chile.

I am new, I have no idea where to create a new topic and I do not see any option or button to do it, my English is not very good, but I will try. I have problems when starting Lakka on my Cubieboard A20, perform the installation as indicated on the page. I attach images so you can see and can help me. I remain attentive to your comments, good day.