Jump to content

thomas.rehberg

Membres
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About thomas.rehberg

  • Rank
    Jeune Qnapeur

Profile Information

  • Matériel
    Futur Qnapeur

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. thomas.rehberg

    Kodi Leia

    FINALLY: I can confirm now to the forum that the measure to walk away from legacy filesystem, and migrate to a thick-volume, does solve the problem with Kodi 18.3 on the Hybrid Station 4.03. Got it working now, and I think indeed this was the reason why for some folks it worked out of the box, whilst others (including me) where facing trouble big time ... I will talk back to QNAP Support that they should be very explicit in their compatibiliy statements when it comes to legacy volumes support, or simply drop it completely. At least it has to be part of regression testing. So I hope these efforts have been of some use to the community, at least at my end I'm happy now looking into Kodi back again
  2. thomas.rehberg

    Kodi Leia

    in case it is a legacy volume the good thing is that you can manage the filesystem with standard Linux tools. Meaning you can also mount the drive in any other Linux system, if not encrypted. Hence you can have access to the data of the disk quite easily, it‘s not a big deal to copy data from a deinstalled RAID drive to other media. To your question: I once migrated my NAS like you described from scratch, by using one of the two RAID drives as backup, the other one for a clean install of the NAS. After the reinstall of QTS mount the „data“ drive to the „virgin“ RAID (as the 2nd drive) and wait until resync is done. Takes 10hours but works. But NEVER do this without a second copy of your precious data, otherwise you are cooked in case something fails !!! Now, the problem is: The volumes created under the new storage manager CANNOT be managed with standard Linux tools any longer, this is how QNAP says. So I cannot yet say if the above will work in case of migrating legacy volumes to e. g. static, thin or thick volumes, better keep your mirror drive safe, or invest into a large USB disk for local backup, they are not too expensive any longer.
  3. thomas.rehberg

    Kodi Leia

    you need to look into the storage manager of the control center. There you should find how your volumes are labeled. If you are coming from QTS firmware 3.x then chances are high that your volumes are „legacy“ still. In the other case y are labeled thin-, thick- or static-volume. I never changed to the new volume structure as for me legacy quite did the job, and I don‘t wanted to spent the effort on migration. Now it seem that I‘m forced to do it, so I will next time I‘m in the LAN. However it ask for a complete reinitialization of the NAS, and you need to choose which kind of volume to create. There are quite some howtos available in the internet, including ones coming official from QNAP.
  4. thomas.rehberg

    Kodi Leia

    as a result of the support -ticket I have raised meanwhile QNAP R&D came to conclusion that the root cause for HD-player (Kodi 17.3) not starting in my HD-Station 4.03 is because of I‘m still running my NAS on a legacy volume. I should upgrade to the new filesystem, introduced with FW 4.x, to make it work. I cannot test it now as on holidays but will do when back. If confirmed this could explain why Kodi works for some platforms, but not for others. I will come back to the forum once I can confirm success by applying this measure However, this will ask for a complete reinstallation, be aware.
  5. thomas.rehberg

    Kodi Leia

    Now, the funny thing is: When I install the HD-Player of QNAP (which in fact is Kodi 17.6 with a very odd theme...) what happens is basically the same issue ! Hence I have opened a ticket to QNAP support, they should spend an effort to fix it as this QPKG is from their official Appstore. Maybe this will tackle the larger problem. Also, in the french forum, you see a lot of people reporting the same issue, so there must be fundamental topic behind. In parallel, with some help of the forum.qnqp.com (mainly yabba235) I´m carrying on with getting a native install done (apt- get install kodi) with some tweaking needed for to get the icon to the HDS desktop. For the ones interested, this thread is under https://forum.qnap.com/viewtopic.php?f=295&t=146654&p=718945#p718945
  6. thomas.rehberg

    Kodi Leia

    Done that, but the problem persists. I rebooted the NAS and tried to start Kodi again, 2 more lines at the very end of the logfile: INFO: ADDON: cpluff: 'Could not read plug-in directory /share/MD0_DATA/.qpkg/Kodi18/opt/lib/kodi/addons: No such file or directory' DEBUG: ADDON: cpluff: 'Not all directories were successfully scanned.' then the logfile closes as before with: FATAL: addon 'audioencoder.kodi.builtin.aac' not installed or not enabled. FATAL: CServiceManager::InitStageTwo: Unable to start CAddonMgr In fact there are two symlinks used in order to get to addon.xml: ~opt to "/share/MD0_DATA/.qpkg/Entware-ng", then in Entware-ng there is another symlink ~Kodi18 to " /share/MD0_DATA/.qpkg/Kodi18/opt/" but these links do work properly, as [/] # cat /opt/Kodi18/share/kodi/addons/audioencoder.kodi.builtin.aac/addon.xml is providing: <kodi/addons/audioencoder.kodi.builtin.aac/addon.xml <?xml version="1.0" encoding="UTF-8"?> <addon id="audioencoder.kodi.builtin.aac" version="1.0.0" name="AAC encoder" provider-name="spiff"> <extension point="kodi.audioencoder" extension=".m4a" library_linux="dummy.so"/> <extension point="xbmc.addon.metadata"> <summary lang="en">AAC Audio Encoder</summary> <description lang="en">AAC is a set of codecs designed to provide better compression than MP3s, and are improved versions of MPEG audio.</description> <platform>all</platform> </extension> </addon> So I really don't understand what is going on here. How can it be that Kodi cannot access files that in fact do exist... and b.t.w. also cat /opt/Kodi18/lib/kodi/addons/audioencoder.kodi.builtin.aac/addon.xml is providing the same output, as the QPKG is installing the addons in both of the directories.
  7. thomas.rehberg

    Kodi Leia

    no. I have tried this version as well, same behavior. There must be something fundamentaly wrong here. Can I specify which addon Kodi will want to load at startup ?
  8. thomas.rehberg

    Kodi Leia

    I have a HS-251+ with HDS 4.0.2 (the right version that installs on QTS 4.3.6), and succesfully installed Kodi 18.2 on top of it. But Kodi is not starting: The logfile is reporting that the "audioencoder.kodi.builtin.acc" addon is not installed or enabled, and the Cservicemamager then is failing. I have spent the whole weekend checking all path and access rights, no success. Some hints in forums advise to delete the Addons27.db, which will automatically rebuild at startup (obviiously it can get corrupted occasionally), doesn^t help. See kodi.log attached, any advise appreciated ... I´m out of ideas actually. The problem is reported at the end of the logfile: ------------------------------------------ 2019-05-19 21:09:22.760 T:140528452640704 NOTICE: ----------------------------------------------------------------------- 2019-05-19 21:09:22.760 T:140528452640704 NOTICE: Starting Kodi (18.2 Git:20190424-nogitfound). Platform: Linux x86 64-bit 2019-05-19 21:09:22.760 T:140528452640704 NOTICE: Using Release Kodi x64 build 2019-05-19 21:09:22.760 T:140528452640704 NOTICE: Kodi compiled 2019-04-24 by GCC 7.3.0 for Linux x86 64-bit version 4.15.18 (266002) 2019-05-19 21:09:22.760 T:140528452640704 NOTICE: Running on Ubuntu 18.04.1 LTS, kernel: Linux x86 64-bit version 4.2.8 2019-05-19 21:09:22.761 T:140528452640704 NOTICE: FFmpeg version/source: 4.0.3-1~18.04.york0 2019-05-19 21:09:22.761 T:140528452640704 NOTICE: Host CPU: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 4 cores available 2019-05-19 21:09:22.761 T:140528452640704 NOTICE: special://xbmc/ is mapped to: /opt/Kodi18/share/kodi 2019-05-19 21:09:22.761 T:140528452640704 NOTICE: special://xbmcbin/ is mapped to: /share/MD0_DATA/.qpkg/Kodi18/opt/lib/kodi 2019-05-19 21:09:22.761 T:140528452640704 NOTICE: special://xbmcbinaddons/ is mapped to: /share/MD0_DATA/.qpkg/Kodi18/opt/lib/kodi/addons 2019-05-19 21:09:22.761 T:140528452640704 NOTICE: special://masterprofile/ is mapped to: /opt/Kodi18/.kodi/userdata 2019-05-19 21:09:22.762 T:140528452640704 NOTICE: special://envhome/ is mapped to: /opt/Kodi18 2019-05-19 21:09:22.762 T:140528452640704 NOTICE: special://home/ is mapped to: /opt/Kodi18/.kodi 2019-05-19 21:09:22.762 T:140528452640704 NOTICE: special://temp/ is mapped to: /opt/Kodi18/.kodi/temp 2019-05-19 21:09:22.762 T:140528452640704 NOTICE: special://logpath/ is mapped to: /opt/Kodi18/.kodi/temp 2019-05-19 21:09:22.762 T:140528452640704 NOTICE: The executable running is: /share/MD0_DATA/.qpkg/Kodi18/opt/lib/kodi/kodi-x11 2019-05-19 21:09:22.762 T:140528452640704 NOTICE: Local hostname: NAS-Rehberg 2019-05-19 21:09:22.762 T:140528452640704 NOTICE: Log File is located: /opt/Kodi18/.kodi/temp/kodi.log 2019-05-19 21:09:22.762 T:140528452640704 NOTICE: ----------------------------------------------------------------------- 2019-05-19 21:09:22.763 T:140528452640704 INFO: loading settings 2019-05-19 21:09:22.809 T:140528452640704 NOTICE: special://profile/ is mapped to: special://masterprofile/ 2019-05-19 21:09:22.827 T:140528452640704 DEBUG: CSkinSettings: no <skinsettings> tag found 2019-05-19 21:09:22.827 T:140528452640704 NOTICE: CMediaSourceSettings: loading media sources from special://masterprofile/sources.xml 2019-05-19 21:09:22.828 T:140528452640704 DEBUG: CMediaSourceSettings: <games> tag is missing or sources.xml is malformed 2019-05-19 21:09:22.851 T:140528452640704 NOTICE: No settings file to load (special://xbmc/system/advancedsettings.xml) 2019-05-19 21:09:22.852 T:140528452640704 NOTICE: Loaded settings file from special://profile/advancedsettings.xml 2019-05-19 21:09:22.852 T:140528452640704 NOTICE: Contents of special://profile/advancedsettings.xml are... <advancedsettings> <videoscreen> <screen>0</screen> </videoscreen> <!-- <cputempcommand>sed -e 's/000$/ C/' /sys/class/hwmon/hwmon0/device/temp1_input</cputempcommand> --> <cputempcommand>/opt/kodi/bin/get_NAS_temperature.sh</cputempcommand> <gputempcommand>sed -e &apos;s/000$/ C/&apos; /sys/class/hwmon/hwmon0/device/temp1_input</gputempcommand> <loglevel>1</loglevel> <setting id="debug.extralogging">true</setting> <setting id="debug.setextraloglevel">131072</setting> </advancedsettings> 2019-05-19 21:09:22.852 T:140528452640704 NOTICE: Log level changed to "LOG_LEVEL_DEBUG" 2019-05-19 21:09:22.852 T:140528452640704 WARNING: CSettingsManager: missing version attribute 2019-05-19 21:09:22.853 T:140528452640704 NOTICE: Default Video Player: VideoPlayer 2019-05-19 21:09:22.853 T:140528452640704 NOTICE: Default Audio Player: paplayer 2019-05-19 21:09:22.854 T:140528452640704 NOTICE: Disabled debug logging due to GUI setting. Level 1. 2019-05-19 21:09:22.854 T:140528452640704 NOTICE: Log level changed to "LOG_LEVEL_DEBUG" 2019-05-19 21:09:22.858 T:140528452640704 INFO: creating subdirectories 2019-05-19 21:09:22.859 T:140528452640704 INFO: userdata folder: special://masterprofile/ 2019-05-19 21:09:22.859 T:140528452640704 INFO: recording folder: 2019-05-19 21:09:22.859 T:140528452640704 INFO: screenshots folder: 2019-05-19 21:09:22.865 T:140527626487552 DEBUG: Thread Lirc start, auto delete: false 2019-05-19 21:09:22.865 T:140527626487552 INFO: Loading special://xbmc/system/Lircmap.xml 2019-05-19 21:09:22.868 T:140527626487552 INFO: * Adding remote mapping for device 'mceusb' 2019-05-19 21:09:22.868 T:140527626487552 INFO: * Adding remote mapping for device 'XboxDVDDongle' 2019-05-19 21:09:22.868 T:140527626487552 INFO: * Adding remote mapping for device 'Microsoft_Xbox' 2019-05-19 21:09:22.869 T:140527626487552 INFO: * Adding remote mapping for device 'PinnacleSysPCTVRemote' 2019-05-19 21:09:22.869 T:140527626487552 INFO: * Adding remote mapping for device 'anysee' 2019-05-19 21:09:22.869 T:140527626487552 INFO: * Adding remote mapping for device 'iMON-PAD' 2019-05-19 21:09:22.869 T:140527626487552 INFO: * Adding remote mapping for device 'Antec_Veris_RM200' 2019-05-19 21:09:22.869 T:140527626487552 INFO: * Adding remote mapping for device 'MCE_via_iMON' 2019-05-19 21:09:22.869 T:140527626487552 INFO: * Adding remote mapping for device 'TwinHanRemote' 2019-05-19 21:09:22.870 T:140527626487552 INFO: * Adding remote mapping for device 'linux-input-layer' 2019-05-19 21:09:22.870 T:140528452640704 NOTICE: Running database version Addons27 2019-05-19 21:09:22.870 T:140527626487552 INFO: * Linking remote mapping for 'linux-input-layer' to 'cx23885_remote' 2019-05-19 21:09:22.870 T:140527626487552 INFO: * Adding remote mapping for device 'mediacenter' 2019-05-19 21:09:22.870 T:140527626487552 INFO: * Adding remote mapping for device 'devinput' 2019-05-19 21:09:22.870 T:140527626487552 INFO: * Adding remote mapping for device 'devinput-32' 2019-05-19 21:09:22.871 T:140527626487552 INFO: * Adding remote mapping for device 'devinput-64' 2019-05-19 21:09:22.871 T:140527626487552 DEBUG: CIRTranslator::Load - no userdata Lircmap.xml found, skipping 2019-05-19 21:09:22.880 T:140528452640704 FATAL: addon 'audioencoder.kodi.builtin.aac' not installed or not enabled. 2019-05-19 21:09:22.880 T:140528452640704 FATAL: CServiceManager::InitStageTwo: Unable to start CAddonMgr ------------------------------------------------
×