Posts by UZI

    For some CPU a fix is available already, you need to check if this fix applies to your system.


    As i understand if OMV setup uses backports configuration and your system is up to date then latest microcode fix is installed by default.
    I checked this with my configuration and found that latest microcode was installed already.


    Regards
    UZI

    Hallo,


    ich habe jahrelang ein OMV mit zwei Platten betrieben. Dabei habe ich täglich einen rsync Lauf von Platte A auf Platte B gemacht. Hat - wie gesagt- über Jahre ohne Probleme funktioniert. Diese Lösung birgt natürlich nicht die Datensicherheit wie ein vernünftig aufgebautes RAID. Allerdings hatte es den Vorteil, dass eine Platte meist im SpinDown war. Parallel habe ich noch wöchentlich den Datenbestand auf eine Synology (diese wurde/wird nur zu Sicherungszwecken hochgefahren) automatisiert per rsync gesichert.
    Als meine Platte zu klein wurde, habe ich mit SnapRaid (OMV Plugin vorhanden, http://www.snapraid.it/, http://www.technikaffe.de/anle…itung_fuer_openmediavault) meine Kapazität erhöht und gleichzeitig RAID Funktionen erhalten. Für mich hat es halt immer noch den Vorteil, dass man im Grunde auf ein natives Dateisystem und damit auf den Datenbestand zugreifen kann und nicht von einem RAID Controler abhängig bin oder RAID Experte sein muss. BAckup weiterhin auf die Synology.


    Vielleicht hilft der Ansatz


    VG
    UZI

    Yes, i checked Duplicati and i do think it's a nice tool to create backups. But my purpose is slightly different. As i do have several PC/Mac in my house i'd like to have my DropBox account on one single source (OMV) directory. This will prevent that i have to check for software updates frequently and wasting hdd space on PC/MAC. It's kind of an easy fileshare with friends and customers.


    But many thx for pointing me to Duplicati i might use it for it's standard purpose ;-)


    Kind regards
    UZI

    Nope. I haven't done anything more with the plugin. Not much time and no ideas on where to go with the plugin. I guess you could use the plugin to create the rclone config and then run it manually.

    @ryecoaaron
    i guess you don't have an update on a rclone plugin?
    I would appreciate to have such kind of plugin available in OMV :)

    @jollyrogr


    My current setup is:

    • OMV on Debian
    • installed virtualbox plugin in OMV
    • two virtualbox VM based on dietpi distro (http://dietpi.com/phpbb/viewtopic.php?f=8&t=390)
      • PiHole with a fixed IP which is different from OMV IP adress
      • NextCloud with DHCP IP adress which is different from OMV IP adress
        Access to OMV user data through SMB/CIFS

    Setup of PiHole and configuration of router settings took me half an hour and now it's operating fine since 1 week without hazzle.
    Pros:

    • no additional hardware required => no invest
    • no additional power concumption (i know Pi current draw is small ;-) )
    • no additonal hardware i have to take care of
    • if PiHole breaks it won't affect OMV setup directly (same for NextCloud!)
    • especially DietPi VM comes with a relatively small footprint => no demanding VM
    • my Core i3 NAS will be utilized in a better way

    Cons:

    • i'm relying on virtualbox plugin and i do hope that it will be supported in upcoming releases (MANY THANKS TO ryecoaaron!!!)
    • i'm relying on dietpi VM and i do hope that it will be supported in upcoming releases
    • ... tbd

    All in all, right know i'm happy with this setup. By trend i do think it might be better to have a combination of OMV focussing on fileservices (BTRFS, SNAPRAID, ZFS, Unionfilessystem, SMB/CIFS, AFP, NFS, FTP, timemachine, Antivrus ...) with VM with dedicated servers (i.e. PiHole, NextCloud, PLEX, ...). This would easier the maintenance/development of OMV for the OMV team. Again many thanks for the effort to Volker and all the other guys maintaining the distro!!!


    Regards
    UZI

    3.0.68 changed a few things especially the change from data drives being mounted on /media to /srv. I am having a hard time keeping up with the changes to OMV. I will try to fix it.

    hmm, this makes me nervous as my OMV is on 3.0.68 since this morning. I'm using mergerfs / snapraid and right now everything is mounted to /media and NOT to /srv.
    Would be glad to get hints if i need to do something special to avoid that my OMV installation will break =O ...

    Pi-Hole is based on dnsmasq, so if you have any dns stuff set up on your OMV machine, it will screw that up. It also has its own web server.


    It's probably safer to run it in a VM or a docker container.

    i personally agree to this approach.
    Currently i'm using Pi-Hole based on DietPi VM (http://dietpi.com). Actually DietPi does offer plenty of useful setups.
    I myself have now two VM in operation 1. PiHole 2. NextCloud (with SMB access to my OMV shares)
    Setup was not to complicated and it simply works out of the box without screwing my OMV setup :-)

    Hello to everybody,


    i recently had to move my OMV installation back from USB Stick (SLC) to a normal harddisk. Everything went fine so far and everything was working. Even virtualbox plugin and VM were working.
    Since last Sunday i notived that after an update of the system i do have an issue with virtualbox and my VM.
    As soon as i'm starting a VM i get this message
    ########################################################
    The device helper structure version has changed.
    If you have upgraded VirtualBox recently, please make sure you have terminated all VMs and upgraded any extension packs.
    If this error persists, try re-installing VirtualBox. (VERR_PDM_DEVHLPR3_VERSION_MISMATCH)
    ########################################################


    I purged the virtualbox plugin and did a complete reinstall. I tested Backports Kernel 4.8 and 4.9 but issue remains still. :(


    Does anybody have an idea how to fix or what i could try?


    Thx for your reply


    Regards
    UZI

    Hallo,
    Vielleicht hilft dir ja diese Seite weiter http://troy.jdmz.net/rsync/index.html. Für eine Anmeldung ohne Passwortabfrage muss ein key für das OMV System erzeugt werden und auf der Synology abgelegt werden. Wo. weiss ich allerdings nicht (hab ich mich nicht mit beschäftigt).
    Die Kombination " rsync ssh key" funktioniert allerdings super. Ich synce damit die user Verzeichnisse mehrerer User von einem Mac auf mein OMV System.


    Mein OMV wird allerdings über ein rsync script auf eine Synology gesichert. Dazu wird das Backup Verzeichnis als NFS Mount auf dem OMV verfügbar gemacht, rsync ausgeführt, die Laufzeit berechnet und das Ergebnis (Laufzeit und Backup erfolgreich oder nicht) als Mail versendet. Hintergrund dafür war/ist, ich sicher nur einmal in der Woche von dem OMV auf die Synology.
    Das Skript habe ich irgendwo im Netz gefunden und für meine Bedürfnisse noch leicht angepasst. Mag nicht elegant sein, funzt aber. ICh hab es mal angehängt, vielleicht hilft es.
    Ach ja, ich synce nicht mit rsync -a sondern mit rsync -rlztuvP, da ich mit der Synology mal Probleme mit -a hatte.


    VG
    UZI

    Files

    Dear all,


    since yesterday i've got an issue with virtualbox_plugin. It started that i had no access to phpVirtualbox anymore.
    System is OMV 3.0.59 Erasmus / 4.9.0-0.bpo.1-amd64


    After some serach in OMV forum i decided to reinstall virtualbox_plugin. I performed those steps on CLI:
    1. apt-get purge virtualbox openmediavault-virtualbox virtualbox-extpack-installer phpvirtualbox
    2. apt-get autoremove (as log output indicated to use autoremove)
    3. rm -f /etc/default/openmediavault-virtualbox /etc/default/virtualbox
    4. userdel vbox
    5. reboot
    6. apt-get install openmediavault-virtualbox


    During installation i recognized this logging on CLI:


    Error! Bad return status for module build on kernel: 4.9.0-0.bpo.1-amd64 (x86_64)
    Consult /var/lib/dkms/virtualbox/5.1.8/build/make.log for more information.


    AND


    WARNING: The character device /dev/vboxdrv does not exist.
    Please install the virtualbox-dkms package and the appropriate
    headers, most likely linux-headers-amd64.



    /var/lib/dkms/virtualbox/5.1.8/build/make.log shows:
    #######################################################################################################
    /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeLockUser’:
    /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1053:33: warning: passing argument 4 of ‘get_user_pages’ makes pointer from integer without a cast
    fWrite, /* force write access. */
    ^
    In file included from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0,
    from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
    /usr/src/linux-headers-4.9.0-0.bpo.1-common/include/linux/mm.h:1302:6: note: expected ‘struct page **’ but argument is of type ‘int’
    long get_user_pages(unsigned long start, unsigned long nr_pages,
    ^
    /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1054:33: warning: passing argument 5 of ‘get_user_pages’ from incompatible pointer type
    &pMemLnx->apPages[0], /* Page array. */
    ^
    In file included from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0,
    from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
    /usr/src/linux-headers-4.9.0-0.bpo.1-common/include/linux/mm.h:1302:6: note: expected ‘struct vm_area_struct **’ but argument is of type ‘struct page **’
    long get_user_pages(unsigned long start, unsigned long nr_pages,
    ^
    /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1050:18: error: too many arguments to function ‘get_user_pages’
    rc = get_user_pages(R3Ptr, /* Where from. */
    ^
    In file included from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0,
    from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
    /usr/src/linux-headers-4.9.0-0.bpo.1-common/include/linux/mm.h:1302:6: note: declared here
    long get_user_pages(unsigned long start, unsigned long nr_pages,
    ^
    /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1067:33: warning: passing argument 6 of ‘get_user_pages_remote’ makes pointer from integer without a cast
    fWrite, /* force write access. */
    ^
    In file included from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0,
    from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
    /usr/src/linux-headers-4.9.0-0.bpo.1-common/include/linux/mm.h:1298:6: note: expected ‘struct page **’ but argument is of type ‘int’
    long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
    ^
    /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1068:33: warning: passing argument 7 of ‘get_user_pages_remote’ from incompatible pointer type
    &pMemLnx->apPages[0], /* Page array. */


    In file included from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0,
    from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
    /usr/src/linux-headers-4.9.0-0.bpo.1-common/include/linux/mm.h:1298:6: note: declared here
    long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
    ^
    /usr/src/linux-headers-4.9.0-0.bpo.1-common/scripts/Makefile.build:298: recipe for target '/var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o' failed
    make[4]: *** [/var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o] Error 1
    make[4]: *** Warte auf noch nicht beendete Prozesse...
    /usr/src/linux-headers-4.9.0-0.bpo.1-common/scripts/Makefile.build:549: recipe for target '/var/lib/dkms/virtualbox/5.1.8/build/vboxdrv' failed
    make[3]: *** [/var/lib/dkms/virtualbox/5.1.8/build/vboxdrv] Error 2
    /usr/src/linux-headers-4.9.0-0.bpo.1-common/Makefile:1507: recipe for target '_module_/var/lib/dkms/virtualbox/5.1.8/build' failed
    make[2]: *** [_module_/var/lib/dkms/virtualbox/5.1.8/build] Error 2
    Makefile:150: recipe for target 'sub-make' failed
    make[1]: *** [sub-make] Error 2
    Makefile:8: recipe for target 'all' failed
    make: *** [all] Error 2
    make: Leaving directory '/usr/src/linux-headers-4.9.0-0.bpo.1-amd64'
    #######################################################################################################


    AND finally in OMV when enabling virtualbox_plugin it fails but it's not surprising me anymore :-(


    Does anybody have an idea to fix compilation of virtualbox module?


    Thx in advance


    UZI

    You could use CT SEsam as desktop app but there's a CT Sesam Server too.


    https://github.com/ola-ct/ctSESAM-server/wiki


    The reason why i found it interesting is the different approach to store passwords
    =======================================================================
    SESAM — Super Easy & Secure Authentication Management
    Qt-SESAM is a user-friendly application that enables you to generate strong passwords. You can use them for all the services you're using, e.g. websites, accounts, or apps.
    The passwords are generated in realtime from service name, user name, a randomly shuffled salt and the master password. For services which don't allow passwords to be changed (e.g. credit cards) Qt-SESAM can also store fixed passwords.
    Qt-SESAM has a unique feature which lets you choose the complexity (vertically) and length (horizontally) of the password in a colored widget
    You can share Qt-SESAM's settings across your computers via a dedicated synchronisation server and a file located on a cloud drive like OwnCloud, Google Drive, Microsoft OneDrive or Dropbox.
    This is secure because all of your settings are AES-encrypted with a 256 bit long key and a 128 bit long IV derived from your master password with PBKDF2.
    Qt-SESAM supports Windows, Linux and Mac OS X. An Android app compatible to Qt-SESAM is underway.
    ========================================================================
    https://github.com/ola-ct/Qt-SESAM