Posts by Cinhil

  • greyhole plugin discovered as not supported after updating to OMV 3

    Hi,
    gboudreau did help me very fast.


    In debug log level of samba we found:

    Code
    Oct 24 20:48:51 impeldown smbd[31557]:   Error loading module '/usr/lib/x86_64-linux-gnu/samba/vfs/greyhole.so': libsmbd-base-samba4.so: cannot open shared object file: No such file or directory


    It was fixed by using the following commands:

    Code
    TARGET_LIBDIR=/usr/lib/x86_64-linux-gnu
ls -l ${TARGET_LIBDIR}/samba/libsmbd-base-samba4.so
ln -s ${TARGET_LIBDIR}/samba/libsmbd-base.so.0 ${TARGET_LIBDIR}/samba/libsmbd-base-samba4.so
ls -l ${TARGET_LIBDIR}/samba/libsamba-debug-samba4.so
ln -s ${TARGET_LIBDIR}/libsamba-util.so.0 ${TARGET_LIBDIR}/samba/libsamba-debug-samba4.so

  • greyhole plugin discovered as not supported after updating to OMV 3

    I found this in the meantime

    Code
    update-rc.d -f greyhole remove



    It unlock me the installation of OMV 3.


    Then I did reinstall greyhole by using the script documented from the greyhole website.


    I am still stuck when after adding the options on shares :

    Code
    dfree command = /usr/bin/greyhole-dfree
vfs objects = greyhole


    It keeps making me this error on mounting


    Code
    error probing vfs module 'greyhole': NT_STATUS_UNSUCCESSFUL
smbd_vfs_init: vfs_init_custom failed for greyhole
vfs_init failed for service Video


    even with the correct symlinks:

    Code
    root@impeldown:/usr/lib/samba/vfs$ ls -lah
total 8.0K
drwxr-xr-x 2 root root 4.0K Oct 23 17:43 .
drwxr-xr-x 4 root root 4.0K Oct 23 13:59 ..
lrwxrwxrwx 1 root root   39 Oct 23 17:43 greyhole.so -> /usr/lib64/greyhole/greyhole-samba42.so


    I will probably need to ask gboudreau.

  • greyhole plugin discovered as not supported after updating to OMV 3

    I am still stuck with

    Code
    root@impeldown:/etc/init# dpkg --configure samba
Setting up samba (2:4.2.10+dfsg-0+deb8u3) ...
insserv: Service samba has to be enabled to start service greyhole
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package samba (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 samba

    I continue to search but in case it is obvious to you please tell me.

  • greyhole plugin discovered as not supported after updating to OMV 3

    Hello,


    I tough greyhole plugin was ok after seing it on http://omv-extras.org/joomla/index.php/omv-plugins-3.
    So all was clear to update to OMV3. But it was not.
    I am stuck now on middle on the OMV update (that come with Wheezy to Jessie update).
    The install did fails because samba is not configured.


    Samba does not want to configure because of :

    Code
    root@impeldown:/tmp# dpkg --configure samba
Setting up samba (2:4.2.10+dfsg-0+deb8u3) ...
insserv: Service samba has to be enabled to start service greyhole
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package samba (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 samba


    And openmediavault does not want to update because of :

    Could somebody have an idea for me to fix my installation ?Thank you very much


    The full install -f log:

  • How to compile/install a plugin from source?

    Hi,
    One more thing : after installing the compiled debian package with dpkg -i, it will usually fail the first time complaining about missing dependencies.
    You just have to call "sudo apt-get -f install" to install them and fix the dpkg install.

  • Greyhole Plugin for 0.4

    Dears,
    Do you have any news about a greyhole support for 0.5 or an approximative ETA ?
    I am stuck with 0.3 and hope to switch to 0.5 or 0.6 once it will be supported.
    Best regards,
    Cinhil

  • Some Words... Decision to abandon some plugins

    Dear all,


    First at all, I would say thank you Marcel for the work done.
    All thing has an end and it is good to be able to say stop when it is needed.


    From this list I am using website and greyhole plugin.
    Especially, I did choose openmediavault because of greyhole. I was searching a NAS software capable to store and protect my data without anything complicated, also capable to grow. Greyhole was perfect for me : simplicity, number of copy, sticky share, ...


    I am maybe the only one in this case, but maybe not. If I am not, maybe it should be important for the evolution of OpenMediaVault to continue this Greyhole integration.
    I understand this could be even not possible by lack of time from developers... I would like to take this plugin responsibility but it is currently impossible by lack of time...
    If I am the only one, OK, good, I need to manage it myself properly on OMV, avoiding conflict with OMV managed Samba configuration and making it my way.


    So, I would like to know if we forget Greyhole on OMV or not so I can decide in which direction to go : stick on v3, waiting for v5 and integrate Greyhole myself, or something else.


    Regards,
    Cinhil

  • add/remove backup disks and shares

    Hi,
    Electrical overload caused by lightning usually burns more than one PC, same for house fire.
    I only tried to achieve rsync with a backup disk locally, usual strategy for backup. Once backup is done, the disk has to be moved somewhere else.
    Rsync service provided by the OMV web interface uses shares, so I did create shares on backup disk.
    I can mount the disk and execute rsync from the command line without using the web interface but I would like to achieve this from the web interface.
    Cinhil

  • add/remove backup disks and shares

    Hello,
    Firstly, merry christmas to everyone ;-).
    I am happy with OMV since some month now. I use Greyhole but like any connected device, the only safe backup solution is to also have an unplugged copy in an other place. So I would like to keep an rsync copy of my important file. I have an eSata docking station where I have put an HDD. Inside OMV interface I have formatted this disk, configure shares on it and use RSync Job also from the interface to copy files from the shares to the backup shares (the -L additional command give the ability to follow the symlinks so Greyhole symlink is not a problem for rsync).
    Until there, all is ok. But now I would like to unplug the HDD. In filesystem, the unmount button is disabled for this disk. Maybe because they are shares configured on it. But I do not want to remove them since I also have the RSync jobs that use these shares...
    Is there a nice solution to my problem ?
    Did you have some advices for me ?
    Kind regards,
    Cinhil