Login at Kodi Home

JonSnow88 · 2015-04-16, 05:31

This has been happening once in a while going back to the Pi1, Every so often openelec will freeze at the OE splash screen and will just sit there, the LED light on the pi will go solid green but nothing loads. Rebooting the Pi fixes this and it starts to boot normally.It's very rare when it happens but I'm just trying to figure out what causes it. Do you guys think adding a small boot delay will help with this?

**popcornmix** · 2015-04-16, 12:36

Any overclock settings? How is the power supply?
You can add, e.g.

Code:
boot_delay=10

to pause before booting the arm, but I'm not convinced it would help.

JonSnow88 · (This post was last modified: 2015-04-16, 14:25 by JonSnow88.)

No OC, default clock settings for now. Powered off two USB ports on 1 TV and the other is plugged into a 2.1 amp surge protector with built in USB ports, always been an issue but happens so rarely its hard to pin point.

Milhouse · 2015-04-16, 19:21

If you add "progress" to the end of your line in /flash/cmdline.txt, you'll get boot progress information when you boot OpenELEC - this might prove useful on those odd occasions when it hangs. Knowing the point it had reached before hanging would be useful, particularly if it's consistently the same point.

JonSnow88 · (This post was last modified: 2015-04-17, 02:04 by JonSnow88.)

Like this?

Code:
boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet progress

Milhouse · 2015-04-17, 02:08

Yep

speedwell68 · 2015-04-17, 08:32

(2015-04-16, 14:23)jebise Wrote: No OC, default clock settings for now. Powered off two USB ports on 1 TV and the other is plugged into a 2.1 amp surge protector with built in USB ports, always been an issue but happens so rarely its hard to pin point.

Why powered off of two ports? The 2.1 amp supply should be enough.

mcelliott · 2015-04-17, 09:17

(2015-04-17, 08:32)speedwell68 Wrote:
(2015-04-16, 14:23)jebise Wrote: No OC, default clock settings for now. Powered off two USB ports on 1 TV and the other is plugged into a 2.1 amp surge protector with built in USB ports, always been an issue but happens so rarely its hard to pin point.

Why powered off of two ports? The 2.1 amp supply should be enough.

I interpreted that to mean that he was powering it from USB rather than the normal power supply. I didn't know you could do this, although this would explain some of my USB related glitches.

JonSnow88 · (This post was last modified: 2015-04-17, 14:32 by JonSnow88.)

(2015-04-17, 08:32)speedwell68 Wrote:
(2015-04-16, 14:23)jebise Wrote: No OC, default clock settings for now. Powered off two USB ports on 1 TV and the other is plugged into a 2.1 amp surge protector with built in USB ports, always been an issue but happens so rarely its hard to pin point.

Why powered off of two ports? The 2.1 amp supply should be enough.

Two different pi's, one has to be powered by USB ports on the TV based on my network configuration but the one up stairs is powered by a surge protector with built in USB ports.

I decided to get a micro USB Y cable so if it's low on power with the TV USB port it can get the extra power it needs from a second USB port.

But the issue has occurred on both, less frequent on the upstairs pi but it is also used allot less.

JonSnow88 · (This post was last modified: 2015-04-18, 03:56 by JonSnow88.)

okay so I got one to hang, the green LED was solid and the last two entries are below.

Starting Kodi clean debug logs...
Starting Kodi hacks...

after which I had no choice but to pull power and after rebooting the SD was corrupt. This seems to be the exact behavior I experienced on the pi1 as well multiple times in the past year but the SD card would not corrupt so I never bothered looking into it. I only started looking into it because as soon as this happens on the pi2 I know SD corruption is just around the corner.

Milhouse · 2015-04-18, 04:22

OK, let's see if it's the same when it hangs next time.

kodi-hacks.service runs this script which could be a problem on a corrupted fs, but under normal circumstances should be harmless.

JonSnow88 · 2015-04-18, 05:17

okay will do, assuming this needs to be run from cli via ssh?

Milhouse · 2015-04-18, 05:48

No, you don't need to run anything - I'm just pointing out what script is being run when it apparently hangs.

JonSnow88 · 2015-04-18, 07:18

ohh I read your post the wrong way, need sleep.

janxyz · (This post was last modified: 2015-04-18, 21:53 by janxyz.)

(2015-04-18, 03:50)jebise Wrote: okay so I got one to hang, the green LED was solid and the last two entries are below.

Starting Kodi clean debug logs...
Starting Kodi hacks...

after which I had no choice but to pull power and after rebooting the SD was corrupt. This seems to be the exact behavior I experienced on the pi1 as well multiple times in the past year but the SD card would not corrupt so I never bothered looking into it. I only started looking into it because as soon as this happens on the pi2 I know SD corruption is just around the corner.

I was bugged by the exact same problem for the past weeks. I tried to find resources to fix it myself because I simply assumed that something went down when I pulled the plug. However, it also happens after updates or when installing an add-on. After spending enough time with this error I figured out how to at least get the whole thing running again without needing to reinstall everything.

If you have a Linux machine sitting around just 'fsck' the corrupted partition and you are good to go. You will probably lose some unsaved settings.

'fsck -y /dev/mmc...'

Edit: I just had another corrupted filesystem. What I did:

I was editing my keyboard.xml via remote access and was logged into ssh. I did not unmount the drive on my Mac and did not log out of ssh. When I rebooted to apply the new keyboard.xml it hung on boot ('...Starting d-bus system message bus').