Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Problem: Kernel Panic
#1
While scanning the library, Moode crashes with a kernel panic, making it impossible to access the web browser interface. By analyzing the log with moodeutl -l I discovered some corrupt files which, once deleted, no longer blocked the system. However, the same files do not block Volumio which simply does not display them. Is all this normal?


Attached Files Thumbnail(s)
   
Reply
#2
(10-18-2023, 08:37 AM)ECELO Wrote: While scanning the library, Moode crashes with a kernel panic, making it impossible to access the web browser interface. By analyzing the log with moodeutl -l I discovered some corrupt files which, once deleted, no longer blocked the system. However, the same files do not block Volumio which simply does not display them. Is all this normal?

It looks weird to me, that there are some errors of the Zend library detecting an invalid (well, more than one) FLAC file; then there is the log about the library update, and then again some Zend errors...
It looks like there is a thumbnail regeneration in progress, and before it's finished a library update is launched... could this be the cause of the kernel panic?!?
I have never seen a KP in my entire life, if not when removing hardware "live"...

What Pi are you running moOde on?
What version of moOde are you running?

Moreover, could you upload somewhere (on a file-sharing platform) 3 or 4 of those invalid FLAC files and provide a link to me, @Tim Curtis and @TheOldPresbyope for us to try to reproduce the issue?

@Tim Curtis: what previous log could we check to see the kernel-panic (if ever possible)?
Reply
#3
Unfortunately we don’t see the log entries at the point of the kernel panic itself. ISTR generating some in the past as fallout from an out-of-memory situation. So, more info needed. Model Pi, moOde version (and 64-bit or 32-bit), additions/alterations, total size of library, yada, yada, yada. 

Regards,
Kent
Reply
#4
Couple things:

1. Library update and thumbnail generation run in parallel as separate unrelated tasks. One can finish before the other.
2. I've never experienced a kernel panic either so no clue how to troubleshoot

The symptoms "While scanning the library, Moode crashes with a kernel panic" suggests something external to moOde software for example a hardware issue or resource depletion (out of memory, out of disk space, etc).

@ECELO post details your setup including the startup log (moodeutl -l)
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#5
(10-18-2023, 12:15 PM)Tim Curtis Wrote: Couple things:

1. Library update and thumbnail generation run in parallel as separate unrelated tasks. One can finish before the other.
2. I've never experienced a kernel panic either so no clue how to troubleshoot

The symptoms "While scanning the library, Moode crashes with a kernel panic" suggests something external to moOde software for example a hardware issue or resource depletion (out of memory, out of disk space, etc).

@ECELO post details your setup including the startup log (moodeutl -l)

Hi Tim, the system is now stable, but I recovered a photo of the last crash before finding the possible corrupt file error. I don't know if this helps in understanding the problem. The Raspberry is a 4GB Pi4 running the latest version of MoOde 64bit


Attached Files Thumbnail(s)
           
Reply
#6
@exocet 

If I were seeing errors like "Unable to mount root fs..." the first thing I would do if flash a fresh moOde image to a different, known-to-be-good uSD card (or USB stick if booting from USB). Also, be sure you've got a good made-for-RPi power supply and interconnecting cable. Flaky memory cards and power supplies are frequently the source of odd, intermittent errors.

Regards,
Kent
Reply
#7
(10-21-2023, 12:10 PM)TheOldPresbyope Wrote: @exocet 

If I were seeing errors like "Unable to mount root fs..." the first thing I would do if flash a fresh moOde image to a different, known-to-be-good uSD card (or USB stick if booting from USB). Also, be sure you've got a good made-for-RPi power supply and interconnecting cable. Flaky memory cards and power supplies are frequently the source of odd, intermittent errors.

Regards,
Kent

It's the first thing I did. Purchased a new 32GB card, but nothing has changed. 4 amp switching power supply.
Reply
#8
(10-21-2023, 01:24 PM)ECELO Wrote: It's the first thing I did. Purchased a new 32GB card, but nothing has changed. 4 amp switching power supply.

You just said "the system is stable now", and suddenly "nothing has changed"...
can you elaborate on that?
Reply
#9
(10-21-2023, 01:26 PM)Nutul Wrote:
(10-21-2023, 01:24 PM)ECELO Wrote: It's the first thing I did. Purchased a new 32GB card, but nothing has changed. 4 amp switching power supply.

You just said "the system is stable now", and suddenly "nothing has changed"...
can you elaborate on that?

This statement refers to all the attempts made before finding the errors in the file library. In practice, before analyzing the system log, I immediately thought it was a microSD error and bought a new one. However, I fear that the system is not yet completely stable, given that I still had a block like the previous ones just yesterday. I don't know what to think anymore... I'm starting to think about possible hardware errors in the PI4. Maybe some memory area of the 4GB on board has problems and when the processor tries to use it it crashes the operating system?
Reply
#10
@ECELO 

Far be it for me to declare categorically that the RPi memory isn't at fault, but it seems highly unlikely.

It's frustrating to try to diagnose your problem when we still don't have the basic information that's already be asked for. Rather than guess I'll just throw out the usual trouble-shooting suggestion: simplify. 

Start off with only the RPi4 with its power supply and headphones or such plugged into the headphone jack. No attached disks or other hardware add-ons. Boot moOde with no customizations and no music library sources added and play radio stations and the sole moOde test file. Do you still experience problems?

Speaking of the power supply---you say a "4 amp switching power supply" but what is it, actually? Is it a Raspberry Pi product or something else? The voltage output under load is an important parameter. Google is your friend on the subject of RPi power and on undervolt messages.

As for the onboard RPi memory, if you insist, you can install and run memtester (sudo apt update && sudo apt install memtester). This tech-head tool is not end-user friendly. Again, Google is your friend.

Good luck.

Regards,
Kent
Reply


Forum Jump: