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.
Posts by Da Flex
-
-
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):
Code[ 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:
Quote -
PS: It's a pretty old log from 2018.

-
-
The DEV's can have mine to work on as long as it's sent back.
If you do long term tests, and provide error log files, it would help dev's like escalade a lot.

-
-
How do you start autofs? What's the content of the config files? If it doesn't run in the background (demon mode), we can't expect a re-mount.
-
Also looking into using AutoFS, as it seems people claim it can handle this sort of situation better.
Does it run as a demon? If yes, you should see it with the "ps -A" command. In that case there is a chance to configure it for re-mount.
-
You could write a python script, started from autostart.sh, which automatically mounts / re-mounts your CIFS.
-
Sounds like an add-on error, which does a wrong key re-direction at first press. Try what happens when you uninstall the add-on. You actually don't need an add-on for key mapping, because you can manually create custom keymap files.
-
Code
2019-04-27 12:07:16.007 T:1937639824 NOTICE: load skin from: /storage/.kodi/addons/skin.aeon.nox.silvo (version: 7.0.1) 2019-04-27 12:07:17.759 T:1937639824 WARNING: Skin has invalid include: skinshortcuts-template-widget1 2019-04-27 12:07:17.759 T:1937639824 WARNING: Skin has invalid include: skinshortcuts-template-widget2Try the default skin.
-
I have a BRIX which uses Intel the addon HDhomerun freezes
I know.

You already had issues with the add-on on RPi, so I don't think it will be a fix for you. Here is the quote about Intel API:
Quote from Kodi 18.2 Release NotesVAAPI on Intel has gained some corrections for interlaced content that toggled interlaced flags during playback, and therefore caused stutter by reconfiguring the decoder.
-
Are there issues with the stability of 9.0.1?
Just to reconsider upgrading from 8.2.5 or wait until 9.0.2 or next iteration considered enough stable.
Depends on your hardware. If you have an RPi like me, you can safely update to 9.0.1. If you have an Intel, at least one issue (video stuttering) will be fixed with 9.0.2, so you better wait for that version.