Hi,
Since a week or so, every time I rebooted my Pi my Kodi was muted.
Looked around a bit, didn’t really find a solution for it.
But yesterday I changed where the subtitles should be displayed and now after a reboot, those settings are back to the old setting also…
So I had another look through ssh this time and my guisettings.xml keeps reverting to a version from 05/27/2016!?
Anybody who knows why this is happening!?
When you reboot, are you choosing reboot in the Kodi GUI ?
Does Kodi disappear quickly or does it remain on screen for 20 seconds ?
Hi,
I use the Kodi GUI.
It disappears rather quickly, I’d say after about 2-3 seconds the screen goes black…
Anybody else have an idea about this?
Otherwise I guess I’ll just have to reinstall to fix it?
I suspect your filesystem is corrupted, likely due to improperly powering down the device.
You can try editing cmdline.txt and adding ‘forcefsck’, but this corruption should be repaired on boot.
Also check usual culprits like SD card and power supply.
Did you restore from a backup? Are the permissions on the files in your .xbmc directory correct?
I added ‘forcefsck’ and booted.
Should I see anythig special during boot?
After booting ‘forcefsck’ wasn’t in cmdline.txt anymore, is that normal?
What do you mean that the corruption should be repaired at boot? Isn’t that what the forcefsck is for?
No, no restore, I installed clean months ago.
These are the permissions. Seems OK, or should I change it to be rw for all users?
Permissions look OK, you could try rw for all but it shouldn’t make a difference unless you’ve changed the Kodi user
I tried some other stuff.
I changed all entries in fstab to 1, nothing happened at boot.
Then I found a post from DBMandrake to put fsck.mode=force fsck.repair=yes in cmdline.txt.
I put my card in my pc, added the command and saved the file. I removed the card, but as a double check I put the card back in and checked cmdline.txt, and the extra commands were gone!!!
So there’s already a problem with the fat32-part of my card it seems.
Probably no easy way of fixing this.
When I run a chkdsk on the card, it says there are no problems found…
That doesn’t sound good. I would recommend formatting the card, but also would consider getting another. It seems that it may be faulty.
You should consider getting another. Recommended brands:
That’s what I was afraid for. Well, I’ve probably installed it a hundred times already, 1 more time won’t hurt 
Have a couple Sandisks laying around, I’ll give one of those a try.
Thanks for the help!
I’ve been having way more problems with this then I anticipated 
I reinstalled it to a new SD without any problems, but after that I can’t get my Hyperion running as it should anymore, not even if I switch to OpenElec (which I just did as a test, I would never ever switch from OSMC 
)
So I’m now trying to get this corrupt installation running as it should again and I just noticed something weird.
This is the output of fdisk -l:
osmc@Raspi-Berging:~$ fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mmcblk0: 3.7 GiB, 3945791488 bytes, 7706624 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000e3b21
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 2048 499711 497664 243M c W95 FAT32 (LBA)
/dev/mmcblk0p2 501760 7706623 7204864 3.4G 83 Linux
Are all those ramdisks normal?? 
And if not, how can I get rid of them?
Are you running this on NOOBS?
Doesn’t look like it
Yes thats normal and not related to your problem.
Nope. Pure OSMC.
I’m stuck between 2 problems now.
My old installation has Hyperion running perfectly, but all changes to the filesystem are lost after a reboot.
New installations of OSMC and OpenElec turn on a part of my LEDs, even if the Hyperion service is not running.
I’m going to test if I can get the card fixed with a live Ubuntu or something like that…
Probably best asked in the big 'ol Hyperion thread.
Problem ‘solved’.
I just dd’ed the broken SD and wrote it to another one. 
No more read-only and Hyperion working as expected 
Thought the SD might be the issue.
Glad to hear it is resolved.
I also noticed in my rpi1, 2 and 3 this /dev/ram0 - /dev/ram15
@fzinken is it normal then? Its from rpi firmaware or OSMC? can be disabled?