What has happened?
I used the repo and now just updated to 3.4.1 by downloading the den and just installing it.
I personally find it easier to install nd less likely to have problem natively without docker
What has happened?
I used the repo and now just updated to 3.4.1 by downloading the den and just installing it.
I personally find it easier to install nd less likely to have problem natively without docker
Ok after installing the new updates including a ZFS update (I only updated OMV previously) it seems to be fixed now.
I rebooted a couple of times and ZFS was correctly mounted - thx a lot for your support here and keep up the good work!
Alles anzeigenGood to know.
@votdev have you though about instead of using Requires=, just create a custom target for those units that run at last, maybe even after multi-user.target?. Hypothetically tomorrow we can have a "yfs" that also does not obey fstab rules, then if we have a plugin you will have to add another Requires= for that particular "yfs"
If there is a custom target, then we can work it from the plugin using systemd overrides that can be shipped from the package. Just an idea
Hi
thx for the feedback. As @Blabla die I will remove my ZFS installation and re-intsall the plugin from scratch in the next days. I will let u know if that hepls.
Hi
Since I had to upgrade some stuff on my NAS I decided to go with OMV 4.x testing. The NAS is running just fine only ZFS doesn't mount after a reboot as the shared folders are created before the ZFS mount occurs
and the ZFS refuses to mount. So each time I reboot the NAS I have to ssh in and delete the shared folders and mount the ZFS - then it is all good.
This issues has been reported on the bugtracker:
0001851
0001827
Both bug reports are marked as "solved" but foe me nothing has changed - so before I re-open the bug I wanted to ask if anyone else is having this issue or if it is just me
thx
Any news here? In OMV 4.12 it still seems to be broken
I would advise anyone to just use the normal emby install instead if the plugin- works flawlessly - should so work under OMV2.
Gesendet von meinem SM-N950F mit Tapatalk
reported: http://bugtracker.openmediavault.org/view.php?id=1827
but because OMV4 is still beta, perhaps you need to wait a lot.
please consider to use OMV 3.0 instead.
Hi
I currently use 4.0.9 and it is still not fixed - contrary to the bugtracker. However I can't update the bugtracker....
Should work. You could try to check with powertop how long it runs on which frequencies
Gesendet von meinem SM-N950F mit Tapatalk
reported: http://bugtracker.openmediavault.org/view.php?id=1827
but because OMV4 is still beta, perhaps you need to wait a lot.
please consider to use OMV 3.0 instead.
I know but I needed the new vdr version
I just thought it might have been a zfs issue and not omv related.
I can deal with it and my usual reboot is only once a year so I will make a system image and then upgrade omv 4 when its released
Gesendet von meinem SM-N950F mit Tapatalk
Hi
I use OMV 4.0 because I thought it makes more sense to directly jumpt to debian 9.1 insteat of "older" v8.
So far I am not having any serious issue and I would be fine to just keep it running this way until OMV 4 is stable.
One thing I noticed however with ZFS is that after a reboot the ZFS array won't mount. When I try to mount it via "zfs mount -a" the error message is "/ZFSPool1 isn't empty" and that is true as it is filled with the folders of my ZFS array but all of them are empty. After I delete the contents via "rm -r *" I can finally mount the ZFS array an all is good.
Anyone else having this?
Alles anzeigenI use a self complied version of fernetmenta’s vnsi from github. The rest is from etobi's repo.
Coderoot@omv:~# vdr -V vdr (2.2.0/2.2.0) - The Video Disk Recorder epgsearch (1.0.1.beta5) - search the EPG for repeats and more vnsiserver (1.5.2) - VDR-Network-Streaming-Interface (VNSI) Server epgsearchonly (0.0.1) - Direct access to epgsearch's search menu conflictcheckonly (0.0.1) - Direct access to epgsearch's conflict check menu live (0.3.0) - Live Interactive VDR Environment quickepgsearch (0.0.1) - Quick search for broadcasts
Coderoot@omvusr/src/vdr/vdr-plugin-vnsiserver# git log commit 2c42df3cf1ba37184e9106091f383ea6009490da Author: Rainer Hochecker <fernetmenta@online.de> Date: Thu Jun 15 08:19:21 2017 +0200
This combination of packages works absolutely stable.
The omv vdr plugin isn't ported to omv4 at the moment. And I don't think that the omv vdr plugin works without adaption to omv4 (debian stretch). Debian stretch seems to bring vdr 2.2.0 by default. But there were some changes from vdr 2.0.3 (debian jessie) to vdr 2.2.0 (debian stretch), especially for the path where the recording directory has to be set.
Greetings Hoppel
Hi Hoppel!
I decided to go straight up to OMV 4 since much hasn't changed yet and just use the debian VDR packages.
After I endlessly tried to change the recording directory I finally figured that the config files had changed. After that everything went smoothly.
thx for your help!
At the moment I use OMV3 and installed the packages (vdr 2.2.0) from etobis repository. Everything works as expected.
Greetings Hoppel
OK.
That's good to hear. Which VNSI version do you use (in case u use it) and how did u install it?
Gesendet von meinem SM-N950F mit Tapatalk
Alles anzeigenHello guys,
at the moment I am considering how to install vdr at my fresh openmdiavault3 installation. Round about one year ago I installed the openmediavault-vdr plugin, but it used an outdated vdr version 2.0.3. So I decided to install vdr 2.2.0 at the command line from etobi's repository with the loss of the plugin gui.
Which version of vdr is used by the plugin today? Is it still using the default/stable debian jessie packages?
If I have a look at the version of the debian vdr packages, I still see the old vdr, but maybe the openmediavault plugin integrates another repo like etobi's repo nowadays. If this is the case, it would be an alternative for me to install the openmediavault-vdr plugin.
Coderoot@omv:~# apt-cache madison vdr vdr | 2.0.3-3 | http://ftp.de.debian.org/debian/ jessie/main amd64 Packages vdr | 2.0.3-3 | http://ftp.de.debian.org/debian/ jessie/main Sources
Otherwise I am fiddeling around with docker. I think it would be an ideal solution to encapsulate the vdr and its complete configuration files. But in the docker images repo we don't have an image for the vdr and I am completely new to docker.
Before I start I want to find out if it is possible to create a completely new container with the following packages from etobi's repo and git and if it is possible to give the container the needed access rights?
- vdr 2.2.0 from etobi's repo
- vdradmin-am from etobi's repo
- vdr-plugin-vnsiserver from git (so I also need the git packages in the docker container to compile)
- the docker container needs access to my dvb device (digital devices cine s2)
- the docker container needs access to a zfs filesystem to store recordings
- the docker container needs access to a separate hdd for timeshift
Is all this possible with the openemediavault-docker plugin gui or at least with the docker command line? If so, is there any good (maybe comparable) howto which describes the creation of such a docker container?
Thanks and greetings Hoppel
Alles anzeigenHello Hoppel,
i have vdr in an docker image.
If you are still interested i can give you my config.
Best regards
Hi!
I am facing the same issue here because I think it is about time to upgrade my OMV to v3 and Debian 8 VDR is still 2.0.3.
Does anyone have some expirience what might be the best solution from the following:
I am really a bit stuck here and from searching the forum it looks like not so many people here use OMV + VDR.
best reagrds
That did work - thx
listing the modules shows ZFS, so I guess it is working:
Mar 6 15:12:18 2017 from 192.168.7.50
root@StoreME:~# less /proc/modules
binfmt_misc 20480 1 - Live 0xffffffffc0a01000
cpufreq_userspace 16384 0 - Live 0xffffffffc09c0000
cpufreq_powersave 16384 0 - Live 0xffffffffc09b4000
cpufreq_conservative 16384 0 - Live 0xffffffffc09af000
nfsd 327680 2 - Live 0xffffffffc0e55000
auth_rpcgss 61440 1 nfsd, Live 0xffffffffc0a9b000
nfs_acl 16384 1 nfsd, Live 0xffffffffc08e7000
nfs 253952 0 - Live 0xffffffffc0e16000
lockd 90112 2 nfsd,nfs, Live 0xffffffffc0a6a000
grace 16384 2 nfsd,lockd, Live 0xffffffffc08ac000
fscache 61440 1 nfs, Live 0xffffffffc0790000
sunrpc 344064 6 nfsd,auth_rpcgss,nfs_acl,nfs,lockd, Live 0xffffffffc0aba000
zfs 2711552 3 - Live 0xffffffffc0b5e000 (POE)
zunicode 331776 1 zfs, Liv
Alles anzeigen
Can I restart the building of the module?
Ok now the output was as follows:
Setting up zfs-dkms (0.6.5.9-2~bpo8+1) ...
Loading new zfs-0.6.5.9 DKMS files...
Building for 4.9.0-0.bpo.1-amd64
Building initial module for 4.9.0-0.bpo.1-amd64
configure: error:
*** Please make sure the kmod spl devel <kernel> package for your
*** distribution is installed then try again. If that fails you
*** can specify the location of the spl objects with the
*** '--with-spl-obj=PATH' option.
Error! Bad return status for module build on kernel: 4.9.0-0.bpo.1-amd64 (x86_64)
Consult /var/lib/dkms/zfs/0.6.5.9/build/make.log for more information.
Setting up libuutil1linux (0.6.5.9-2~bpo8+1) ...
Setting up libnvpair1linux (0.6.5.9-2~bpo8+1) ...
Setting up libzpool2linux (0.6.5.9-2~bpo8+1) ...
Setting up libzfs2linux (0.6.5.9-2~bpo8+1) ...
Setting up linux-compiler-gcc-4.9-x86 (4.9.13-1~bpo8+1) ...
Setting up linux-headers-4.9.0-0.bpo.1-common (4.9.2-2~bpo8+1) ...
Setting up linux-kbuild-4.9 (4.9.13-1~bpo8+1) ...
Setting up linux-headers-4.9.0-0.bpo.1-amd64 (4.9.2-2~bpo8+1) ...
/etc/kernel/header_postinst.d/dkms:
cp: cannot stat '/var/lib/dkms/spl/0.6.5.9/build/spl_config.h': No such file or directory
cp: cannot stat '/var/lib/dkms/spl/0.6.5.9/build/module/Module.symvers': No such file or directory
Setting up linux-headers-amd64 (4.9+78~bpo8+1) ...
Setting up zfsutils-linux (0.6.5.9-2~bpo8+1) ...
Setting up zfs-zed (0.6.5.9-2~bpo8+1) ...
Setting up openmediavault-zfs (3.0.10) ...
Processing triggers for libc-bin (2.19-18+deb8u7) ...
Processing triggers for openmediavault (3.0.64) ...
Updating locale files ...
Updating file permissions ...
Purging internal cache ...
Restarting engine daemon ...
Fertig ...
Alles anzeigen
It looks to me like the build failed, but the ZFS plugin is there. I uncertain if its safe to plug in the ZFS drives !?
Depends largely on how fast your cpu is.
Can you post the rest of the output from installing?
Nope, that output was already gone.
Since ZFS was the 1st I insatlled I just restarted from scratch. I will keep u postedt
thx