Since (as I have written above) Kodi is not running at all, this log file is not available. Also I'm not sure if kodi.log contains what I need.Can you confirm that kodi.log would contain messages from the kernel about tuner card drivers?
If you just need an add-on of Kodi, then you'll see the errors, warnings etc. generated by that add-on. You can run LE non-headless for testing, if no kodi.log appears headless - I'm not sure about it.
Really?
Yes, read here.
HD sound pass-through is not supported by LE on RPi (was already mentioned in another thread). You need more processing speed to pass-through that much data, it's not just "copy and paste".
Kodi has an own log system, which is different to standard Linux.
The kodi.log is the replacement for kern.log, and it's located (when is logging activated) at /storage/.kodi/temp.
There are different log levels. Log level 1 should fit your needs.
Activate logging at level 1 by creating the file /storage/.kodi/userdata/advancedsettings.xml with this content:
<advancedsettings>
<loglevel>1</loglevel>
</advancedsettings>I don't see any nightly builds for 9.0.2, too. It takes time to implement Kodi 18.2. The LE 9.0.x branch is still alive.
Update: I changed the volume name of the drive and now its working again as intended. Thanks for the relpys
What volume name do you use now? Knowing the name conventions could help other people.
To my knowledge they currently build LE 9.0.2, which implements Kodi 18.2. 9.0-devel should be the nightly builds for that version.
A good logic is (don't know if they do so):
LE 9.0.x implements Kodi 18.x
LE 9.1.x implements Kodi 19.x
I was not using HDhomerun. Was using it for my private library to watch movies
Sorry for my wrong interpretation.
Where are your videos stored? (internal SSD, external hard disk, NAS)
I know you have a large library. How long is the list you are scrolling through?
Does it freeze forever, or just for some time?
This forum is the wrong place, because you already mentioned in other postings that it's about the HDHomeRun add-on. Please use the support forum of HDHomeRun. I'm sure they are very interested in feedback of heavy DB users.
You can find some config at "/etc/udevil/udevil.conf", but I don't think that's the problem. Login with SSH, find the drive's mount path by using the "mount" command (/var/media/...), and check the read / write permissions of the files you can't write. Use the "ls -la" command to read file permissions, and the "chmod" command to make files writable.
The file ".udevil-mount-point" says, it has been mounted, but the last lines of your log file say, it has been reseted (after the mount):
[ 11.304998] sd 0:0:0:0: [sda] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 11.305531] sd 0:0:0:0: [sda] Write Protect is off
[ 11.305546] sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08
[ 11.306038] sd 0:0:0:0: [sda] No Caching mode page found
[ 11.306052] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 11.366122] sda: sda1
[ 11.372714] sd 0:0:0:0: [sda] Attached SCSI disk
[ 87.270874] usb 1-1.3.1.4: reset high-speed USB device number 7 using dwc_otg
[ 119.177588] usb 1-1.3.1.4: reset high-speed USB device number 7 using dwc_otgThe mount / reset cycle can indicate a power issue. Attach a separate PSU at the disk to get extra wattage, or use a better PSU at the hub.
I have an almost identical 2Tb WD drive attached to my home server for Plex. Only difference is that it’s NTFS file system. If I attach that to the RPi everything works fine.
EXT4 has a Linux rights management. You probably don't have the rights to enter some directories. You can change it with the "chown" and "chmod" commands from SSH login.
Depending on the menu structure I might need to navigate to for a report. I don't dig into sub systems often. So other than that one section within kodi. I'm walking around blind most likely.
No problem. If you get an error and don't find answers, create a new thread, and somebody will show you how to add the log file.
So, should I submit a bug report? I'm fairly sure this is a LibreELEC bug, since others have reported solving this issue by moving to CoreELEC.
The link above already leads to a bug report. I would just rename the thread title by using the [BUG] prefix. If you're lucky, they will fix it this week with LE 9.0.2.
What, my log? I've generated and uploaded it yesterday.
Yes, you have a mix of old and new entries in there. This is impossible, and probably another bug:
2018-06-22 08:11:52.981 T:4086567712 NOTICE: Kodi compiled 2019-02-21 by GCC 8.2.0 for Linux ARM 32-bit version 3.14.29 (200221)
PS: It's a pretty old log from 2018.
This line of the log file could be the cause:
2018-06-22 08:11:53.706 T:4064064368 WARNING: Pulseaudio module module-allow-passthrough not loaded - opening PT devices might failLooks like an LE bug.