OSMC stuck in boot loop after reboot

I restarted my Pi2 and it’s now stuck in a boot loop. I wasn’t installing an update; just a normal reboot and now it seems my install is trashed. Any suggestions for debugging/fixing this?

This seems to happen pretty regularly to my Pi; it goes for a few months and then will randomly die and I have to wipe and re-install. It’s quite frustrating, as I have to restore all the data to the system and spend a bunch of time re-configuring everything. I’ve tried three different power supplies (I just wanted to make sure that a power drop wasn’t causing a corrupted SD card), but nothing seems to help.

I am able to hit ESC after the boot screen appears, but I’m still unable to actually start OSMC. It keeps on crashing.

I found this:

during boot as soon as you see the blue OSMC splash screen hold down CTRL on the keyboard until you see a login prompt

Worth a try if Esc isn’t working for you.

Since you are repeatedly getting these corruptions and are sure you’ve used power supplies that meet the required spec. for the Pi 2, it might be worth considering a replacement SD card. They can get quite a workout and some brands that might work just fine in, say, a camera, simply aren’t good enough for running an operating system.

1 Like

Thanks so much for the info. I should’ve been a little clearer; I can use ESC to get to a login prompt, login, but I can’t actually get OSMC to start.

I have a decent quality Sandisk card currently. Do you recommend a different card? It’s good quality and should be plenty fast enough to run the Pi, so I’m not entirely sure what else I’m looking for in a card to run my Pi.

Perhaps you mean Kodi won’t start, since the operating system appears to be up and running. At this point, I’d suggest you run grab-logs -A and let us know the link to the file.

Sandisk is a quality brand, for sure. But I guess like with cars, even the most reliable brands still go wrong, just less often. I’m using a Samsung Evo+ on a Pi 3. I bought it because I already had a Samsung Evo on a car dashcam and found it to be remarkably trouble-free, given the regular use it had.

1 Like

Perhaps you mean Kodi won’t start

Yes sorry *facepalm*. Today’s clearly not my day hehe.

I was unable to get grab-logs to actually upload (network connectivity errors), but here’s a pastebin with the file: OSMC upload log - Pastebin.com

It looks like this is possibly the problem:

Apr 14 11:09:19 osmc mediacenter[314]: /usr/lib/kodi/kodi.bin: error while loading shared libraries: liblibcli-lsa3.so.0: cannot open shared object file: No such file or directory

There does seem to be some data corruption on the SD card (and possibly even on the 3 TB external disk).

The liblibcli-lsa3.so.0 shared-object file that it can’t find when trying to start Kodi should be in directory /usr/lib/arm-linux-gnueabihf/samba . The fact that it’s gone missing strongly suggests a data corruption issue that’s unlikely to be confined to this one file.

As to the why, your 3 TB disk might well be the culprit if it is USB-powered. If it has its own external power supply then it’s probably in the clear. (Powering an external disk from its USB port on a Pi 2 can be risky.)

1 Like

There does seem to be some data corruption

That’s what I was afraid of :confused:

The 3TB disk is self powered, so that shouldn’t be causing the problem. If it is actually corrupted, like I was guessing, I have a suspicion that it may have been a DVD drive I used on the Pi awhile back without a powered hub. However, I didn’t see this problem on the Pi right away, so that makes me wonder why it took so long to show up.

I also have a Flirc controller plugged in as well, but I kinda doubt that’s causing the issue, right?

Very unlikely by itself, but it’s the total load that counts, and transient spikes in the load can do real damage.

Maybe the corruption was there but didn’t affect the system until you rebooted, when it needed to be read from disk.

That’s correct.

It’s also not a recently adjusted dependency, so it’s not the result of a partially installed / failed update. The card seems corrupted at the very least. Not something an fsck will fix trivially unfortunately.


Thanks for your replies @dillthedog and @sam_nazarko. I wiped and re-installed from scratch.

On the second and third boots, I couldn’t even log into the command line after hitting ESC, further giving proof that the SD card was corrupted.

I’m going to keep an eye on power usage. Thanks for the recommendation for the EVO card.