|
| 1 | +# Safe Mode |
| 2 | + |
| 3 | +## Safe Mode |
| 4 | + |
| 5 | +This feature gives users the option to not end up in a Kodi restart loop if something went wrong on the Kodi side and the possibility to fix an existing installation. |
| 6 | + |
| 7 | +### How does it work |
| 8 | + |
| 9 | +If for whatever reason Kodi crashes and therefore created a crashlog more than 5 times in 900 seconds (15 minutes), then we will enter the safe mode. This will avoid that you won't be able to get a running Kodi in any way. |
| 10 | + |
| 11 | +### Behind the scenes |
| 12 | + |
| 13 | +What has happened once you entered the save mode? Pretty simple. Once you end up in safe mode, we did a backup of your existing Kodi installation in a different folder. From a technical point of view we simply renamed the existing (and failing) `/storage/.kodi` folder to `/storage/.kodi.FAILED` and triggered a reboot after that. That will mean your next Kodi start will end up with a vanilla Kodi but with a special red background and a notification screen, that you now have entered the save mode. It will look like this: |
| 14 | + |
| 15 | + |
| 16 | + |
| 17 | +### What to do now? |
| 18 | + |
| 19 | +First you should read the infos given from from the notification screen above and also probably make notes if you might think you can't remember them later. Once that is done, you should follow this section which is similar to the "first run wizard" and gives you specific options to either enter a hostname, enable Samba and/or SSH or setting up your network connection like shown in the screenshots below: |
| 20 | + |
| 21 | + |
| 22 | + |
| 23 | + |
| 24 | + |
| 25 | + |
| 26 | + |
| 27 | + |
| 28 | + |
| 29 | +We recommend to enable both SSH and Samba as this might be necessary to debug why your Kodi ended up in the safe mode at all. |
| 30 | + |
| 31 | +After you ended the wizard all your settings, add-ons, library and what not from the previous (failing) installation are stored inside the `/storage/.kodi.FAILED` folder. This folder can either be accessed by SSH or Samba as we also share this folder by default if it exists. Please read the following if you don't know how to access LibreELEC: Accessing LibreELEC |
| 32 | + |
| 33 | +From now on, if you want to debug why Kodi entered the safe mode, we will completely focus to the `/storage/.kodi.FAILED` folder which contains all the necessary information we might need to see what happened. |
| 34 | + |
| 35 | +So for providing the logfile via SSH use the following command: |
| 36 | + |
| 37 | +`pastebinit /storage/.kodi.FAILED/temp/kodi.log` |
| 38 | + |
| 39 | +or search via Samba for the ''Kodi-Failed'' folder and enter the ''temp''-subfolder to get the ''kodi.log'' logfile. |
| 40 | + |
| 41 | +For the very best option, we recommend to use the log uploader option we built-in in LibreELEC. |
| 42 | + |
| 43 | +### After debugging or fixing |
| 44 | + |
| 45 | +After we might have found out what the problem might have caused and we also might have fixed it, you don't need to do anything else beside rebooting your machine. We will automatically restore the old (and probably fixed) installation and at the next boot you will directly boot into Kodi like you are used to. |
| 46 | + |
| 47 | +Be aware, that if we haven't fixed anything, that you will again enter the safe mode to be able to fix your installation if Kodi crashes multiple times again. |
| 48 | + |
| 49 | +### How to disable safe mode |
| 50 | + |
| 51 | +It can be completely disabled by creating `/storage/.config/safemode.disable` . |
| 52 | + |
| 53 | +Login via SSH and type touch `/storage/.config/safemode.disable` |
| 54 | + |
| 55 | +### How to fix a broken add-on |
| 56 | + |
| 57 | +As Kodi don't provide any help you have to manually remove the addon. |
| 58 | + |
| 59 | +Login via SSH and type `rm -rf /storage/.kodi.FAILED/addons/addon.name` |
0 commit comments