LE 8.95.003 frozen on RPI3

kevtuning · January 27, 2019 at 8:45 PM

Hi,

My LE 8.95.003 is freeking quite often (allmost each day, the first time I am trying to access) on my Rpi 3 ==> only solution is removing power supply with the risk to corrupt SD card

the rpi is replying to ping... but not to ssh or samba... and if I look on tv side, the display is frozen...

I am not doing very special things... just running LE and some docker containers (transmission and Plex server)

Any idea where it's coming from ?

**Klojum** · January 27, 2019 at 9:42 PM Official Post

A corrupt SD card can be rewritten. Bit rot is something else and more permanent.

Try a different SD card and do a 24 hour test. LibreELEC for RPi is normally rock stable.

kevtuning · January 27, 2019 at 9:49 PM

Hi, I didn't said that my SD card is corrupted...

When I reboot the RPI it works fine...

But LE is freezing often...

**Da Flex** · January 27, 2019 at 11:02 PM Official Post

I'm using the same LE version on my RPi3B+, and it runs fine. I don't use docker containers, so that could be the cause in your setup.

kevtuning · January 28, 2019 at 12:25 PM

Last docker container "installed" is the Plex server...

But there's no sense that a docker container is freezing the complete system

**Da Flex** · January 28, 2019 at 3:12 PM Official Post

If you are 100% sure about MicroSD card and docker containers, the next step is activating log level 1 and reading kodi.log for errors.

cmb · February 2, 2019 at 3:38 AM

Quote from Da Flex

...the next step is activating log level 1 and reading kodi.log for errors.

In an attempt to track down this freezing problem, I modified my /storage/.kodi/userdata/advancedsettings.xml file to enable debug logging.

Code

<advancedsettings>
<loglevel>1</loglevel>
<cache>
<memorysize>73400320</memorysize>
<readfactor>20</readfactor>
<buffermode>1</buffermode>
</cache>
</advancedsettings>

Today my stream of a television program stopped at about 4 minutes, 50 seconds from the start. I couldn't use the Yatse remote app on my tablet computer to do anything with LibreElec. The keyboard attached to Raspberry Pi USB port also did not work. The only way I could revive LibreElec was to remove DC power from the unit. When I plugged the Raspberry Pi's power supply back in, LibreElec booted as expected.

Then I went to the desktop computer on my local area network to open the /storage/.kodi/temp directory on LibreElec. I found the new kodi.log file there but a crash log was apparently not created.

Next, in LibreElec, I went to Settings > LibreElec > System > Submit Log > Upload Latest Kodi crash log. That file pasted successfully and what little there is can be found at http://ix.io/1zma.

Then I tried to upload the latest full Kodi.log suite created since the power-cycle reboot. That failed three times with the error message, Failed to Paste Logs, Try Again. (It might be that a 4.6 MB log is too large.)

Finally I rebooted LibreElec and once again tried Settings > LibreElec > System > Submit Log > Upload Latest Kodi log. This time it was successful. You can see that log here: http://ix.io/1zme.

I restarted the television program I was watching and it finished without further interuption.

Can you see anything in the logs that might lead to freezing or the inability to create a crash log?

System Information

Internet Source: Frontier Communication DSL line through a Netgear D2200D gateway. The LibreElec is fed from a port on the gateway over powerline network using a pair of TP-Link 200 MBps modems.

Raspberry Pi 3 Model B, Micro-SD Card - 32 GB

LibreElec Version 8.95.003 9.0

**chewitt** · February 2, 2019 at 3:59 AM Official Post

cmb are you deliberately hijacking the original thread from kevtuning or trying to be helpful replicating someone else's problem while using a non-standard Kodi configuration? (e.g. modified cache settings which are almost never required).

cmb · February 2, 2019 at 5:06 PM

It appeared that I was having the same problem as kevtuning. He didn't step up with a log as suggested by Da Flex so I tried to provide one.

Shall I move my installation up to 9.0.0 now or leave it at 8.95.003 for further diagnostics?

Shall I remove the modified cache settings from my advancedsettings.xml file?

**Da Flex** · February 2, 2019 at 8:07 PM Official Post

Quote from cmb

Can you see anything in the logs that might lead to freezing or the inability to create a crash log?

Yes, your second log file shows read errors at "special://masterprofile". Kodi stores configuration data there, and read errors at this directory can cause crashes. Please check your MicroSD card. There are several diagnostic programs for free out there. Sometimes read errors go hand-in-hand with increasing heat. Correct booting doesn't means much, when it's about broken storage devices.

cmb · February 3, 2019 at 5:38 AM

Quote from Da Flex

Please check your MicroSD card.

I have a SanDisk Ultra 32 GB Class 10 SD card in my Raspberry Pi 3. I removed it from the Raspberry Pi and copied the image to a backup directory on my Linux desktop computer. Then I ran a badblocks read/write test on the SD card.

Code

# sudo badblocks -o ./badblocks.list -w -s -v -b 4096 -c 16 /dev/sdd
Checking for bad blocks in read-write mode
From block 0 to 7791743
Testing with pattern 0xaa: done
Reading and comparing: done
Testing with pattern 0x55: done
Reading and comparing: done
Testing with pattern 0xff: done
Reading and comparing: done
Testing with pattern 0x00: done
Reading and comparing: done
Pass completed, 0 bad blocks found. (0/0/0 errors)

Display More

There were no reported errors and the badblocks.list file is empty.

(Also, for what it's worth, the MD5 check sums for the LibreElec image on the SD card and the image backed up to the Linux machine matched.)

Finally I restored the LibreElec image from backup to the SD Card, placed it in the Raspberry Pi and booted the device. LibreElec 8.95.003 is running again.

**Da Flex** · February 3, 2019 at 4:43 PM Official Post

cmb:

Fine. If you still get errors, do this tests to check RAM, PSU and temperature.

cmb · February 3, 2019 at 11:06 PM

As suggested I have run a series of tests on my Raspberry Pi 3 hardware. The memtester tests showed no errors over 5+ loops (condensed below).

Code

LibreELEC:~ # memtester 512M
memtester version 4.3.0 (32-bit)
pagesize is 4096
pagesizemask is 0xfffff000
want 512MB (536870912 bytes)
got  512MB (536870912 bytes), trying mlock ...locked.
Loop 1:
Stuck Address       : ok
Random Value        : ok
Compare XOR         : ok
Compare SUB         : ok
Compare MUL         : ok
Compare DIV         : ok
Compare OR          : ok
Compare AND         : ok
Sequential Increment: ok
Solid Bits          : ok
Block Sequential    : ok
Checkerboard        : ok
Bit Spread          : ok
Bit Flip            : ok
Walking Ones        : ok
Walking Zeroes      : ok
8-bit Writes        : ok
16-bit Writes       : ok

Loop 2:
Stuck Address       : ok
Random Value        : ok
Compare XOR         : ok
Compare SUB         : ok
Compare MUL         : ok
Compare DIV         : ok
Compare OR          : ok
Compare AND         : ok
Sequential Increment: ok
Solid Bits          : ok
Block Sequential    : ok
Checkerboard        : ok
Bit Spread          : ok
Bit Flip            : ok
Walking Ones        : ok
Walking Zeroes      : ok
8-bit Writes        : ok
16-bit Writes       : ok

...

Loop 5:
Stuck Address       : ok
Random Value        : ok
Compare XOR         : ok
Compare SUB         : ok
Compare MUL         : ok
Compare DIV         : ok
Compare OR          : ok
Compare AND         : ok
Sequential Increment: ok
Solid Bits          : ok
Block Sequential    : ok
Checkerboard        : ok
Bit Spread          : ok
Bit Flip            : ok
Walking Ones        : ok
Walking Zeroes      : ok
8-bit Writes        : ok
16-bit Writes       : ok

Loop 6:
Stuck Address       : ok
Random Value        : ok
Compare XOR         : ok
Compare SUB         : ok
Compare MUL         : ok
Compare DIV         : ok
Compare OR          : ok
Compare AND         : ok
Sequential Increment: ok
...

Display More

The power supply also passed.

Code

LibreELEC:~ # vcgencmd get_throttled
throttled=0x0

My power supply is a Canakit Model DCAR-052A5 that is rated at 5 VDC output at 2.5 amperes. Using a Fluke 8022A multimeter, I measured 5.05 VDC at the Raspberry Pi. That is within the range of 4.75 to 5.25 VDC required by the computer.

It is unlikely that the hardware is a problem. I have been using this configuration since February of 2017 through several iterations of LibreElec (and probably some versions of the earlier OpenElec).

This freezing problem is new to me. I don't recall seeing this behavior until LibreElec version 8.95.003 or perhaps 8.95.002.

I have italicized freezing because it might be a misnomer. On the surface it looks like LibreElec has frozen or locked up. The stream stops. The software is unresponsive to a remote control and to the USB-attached keyboard. Communications with LibreElec is not possible with FTP. On the other hand, I have noticed that the Raspberry Pi's SD Card Activity indicator continues to flash. Something's going on in there.

I see this behavior only during a program stream. It seems that the buffer runs out of program material and playback stops. LibreElec closes its ears to the outside world but is busy doing something. Unfortunately it is too occupied to write a crash log. What changed in this 8.95.xxx series?

**Da Flex** · February 4, 2019 at 6:41 AM Official Post

I'm running out of ideas.

My final thoughts:

Maybe LE does quicker file system access in newer versions, and your card / card reader combo doesn't like that.

1) Buy another MicroSD card. (MicroSD HC, Class 10 is what I use)

2) If the new MicroSD card doesn't helps, buy another RPi.

Good luck!

**Da Flex** · February 4, 2019 at 10:39 PM Official Post

PS: If you use a MicroSD XC card, that could be the cause of your crashes.

cmb · February 4, 2019 at 11:26 PM

Quote from Da Flex

PS: If you use a MicroSD XC card, that could be the cause of your crashes.

I just checked. It is an HC card.