Posts by

    My HP Microserver is getting too old to properly run the photoprism docker that will replace my gPhoto account (expecially because of the AI running face recognition)

    Once miniITX mb were quite common and the default option for a small NAS (up to 6 bays)

    Nowadays many more even smaller form factor have drained the interest from this one (NUC, etc)

    But still thank to connection standards like oculink you can really get a lot form this form factor

    Unfortuatelly it looks like there are only industrial boards (with the little room wasted for serials ports and so on and with awkward Atom cpus

    I'd like a modern miniITX sporting a Zen3 based cpu (V3xxx) embedded (as far as the embedded cpus have a lower TDP), with 1-2 10GBe ports, oculink for the storage, hdmi/vga poutput for thoubleshouting and installation, an eSata or usb3.1 for external backup, ngff NVMe slot for the baremetal hypervisor

    Any suggestions?

    I'm running OMV on a ESXi server based on a HP Microserver N54L.

    Latelely I've killed a few VMs so I have more ram I can assign to OMV (it was 3GB, now I can go up to 12GB) ((yes this edition of the microserver was advertised to support up to 8GB, but indeed it could accempt even 16GB, the limit is in the number of the chip module, so the bigger the module the more the ram, at least up to 2x 8GB for sure)

    The cpuis a very little performance.

    The matter is the are no Ryzen V3xxx mini ITX board on the market with the oculink and needed features (es Realtek nNIC do not work with the latest ESXi) I'm tring to have this microserver keep on working more than its supposed lifetime


    is there a way I can force OMV to use this extra ram to enhance performances despite the cpu ?


    Based on my limited understanding the following changes are needed:

    1) wireguard needs to be provided by 5.10 kernel

    2) Plex and UrBackup-server will need to be run insider a docker container

    1: GREAT, no more kernel upgrades breaking WG

    2:this would be a real pain.....I already estimated the possible issue of implementing docker to handle shared folders accessed by several services both on host and continers......and I guess the best way to handle it would be IDMAPPED, coming with kernel 5.12.....what kernel is the latest OMV5 running on? (I don't want to to mess up with backports)

    H, I'm going to use your script to upgrade 4to5

    My OMV4 (latest) runs the following services:

    smb (configured via OMV gui)





    docker (openVPN-AS, ShadowSocks).

    Is there anything I should do before running your script?

    is there anyrhing that won't work with OMV5?

    I guess I'll need to manually reinstall headers and kernel mod for wireguard (unless the new kernel is higher than 5.4)

    Now I'm with OMV 4.1 and kernel Linux OPENMEDIAVAULT 4.19.0-0.bpo.8-amd64

    but in the same repo I can see the kernel 5.6

    given this year it's the second time there is something that brakes the wireguard-dkms module (error on compile)

    the 5.6 kernel would be precious

    Can I upgrage just the kernel (and stay on OMV4.1 ?



    I guess soon OMV5 will feature the kernel 5.6

    I'm interested cause sometime the OMV update breaks the wireguard module (the headers are not automatically downloaded, not always at least)

    that could not look like a big deal, but it is for me cause I live 400km away from my OMV server

    This shouldn't happen anymore on kernel 5.6 has far as the wireguard support is built-in

    I have a OMV4 I'd like to upgrade to OMV5

    I've checked this post from ryecoaaron

    What I am concerned about is my urbackup installation, config and files

    Would the omv-urbackup purge command....purge only the plugin or the urbackup server config as well?


    thank you
    it was I was looking for
    I rum OMV as a VM on ESXi6 on an 8y old HP Microserver and I cannot properly run a 2ns emulation level
    So docker is out of my otions

    in effetti è vecchiotta, ma quelle basate sui nuovi Celeron con core Gemini Lake sono tutte limitate a 16GB di ram massima e solo 1 ethernet (Giga)

    a questo punto credo che siano piu vantaggiosi i nuovi Ryzen Embedded V1000 con core Ryzen_2 a basso consumo
    Cerco sempre delle miniITX con cpu embedded perchè hanno consumi minori e volumi (del dissipatore passivo) compativili coi case Nas 4 bay
    e dovrebbero avere 2 ethernet

    sono diventato vecchio e pigro, non vado oltre l'aggiunta di ram e unità disco
    in realtà di case come il vostro non è difficile trovarne su siti appositi
    sto facendo facica a trovare le mb con cpu embedded
    Quindi ne approfittavo per fare un acquisto unico

    in realtà sono indirizzato a queste soluzioni perchè offrono un elevato rapporto prestazioni consumi sulla fascia di consumo che ritengo accettabile per le mie esigenze
    e perchè i chipset sono appositamente dedicati ad uso nas/networking (2-4 ethernet, almeno 4-16 porte sata, etc)
    Ovvio che in questo caso mi basterebbe la varsione base da me indicata, piu che sufficiente a saturare i bay forniti dal case identificato
    Trattandosi di soluzioni dedicate al settore nas/networking mi aspetto che Linux sia il primo Os a supportarle pienamente.
    OMV gira tranquillamente su Debian, quindi non vedo problemi
    tra l'altro da alcune recensioni lette prima dell'estate Linux supporta già i chip dedicati all'offload delle operazione di crypt/decrypt per ssl.
    Quindi direi che il supporto almeno lato Intel sia piu che completo

    Ciao scrivo in italiano perchè immagino la potenziale clientela sarebbe italiana
    Da tecnico IT uso OMV princcipalemtne in ambiente domestico o soho (oppure per il remote backup della PMI fatto a casa della proprietà)
    Credo che un hardware tipo Hp Microserver sarebbe ideale per dare il giusto mix di espandibilità, consumi, ingombri,
    purtroppo HP monta hardware custom, ma finalemente sono entrate in commercio diverse soluzioni interessanti di motherboard mini-ITX con cpu embedded (meno ingombri e meno consumi)
    peso sia alla serie INTEL atom C3xxx fino a 16 core
    che alla serie AMD Ryzen embedded (V1xxx)

    una mb con 2 porte gigabit (o addirittura 10Gbit per poter essere spinto anche in ambito aziendale/homelab)
    uscita video hdmi (per chi volesse metterlo in soggiorno direttamente collegato al tv
    4-6 porte sata con relative bay hot swap (tipo il MicroServer di HP)
    magari uno slot per ssd pci-E
    una porta usb interna (io per esempio ci tengo esx)
    e supporto fino almeno 64GB di ram (per chi vuole usare piu machine virtuali oppure usa ZFS)

    una macchina che riesca ad essere al tempo stesso economica, ma aperta ad usi che vanno dal domestico al semiprofessionale
    al homelab per motivi di studio

    Ho visto sul sito che avete un case 4 bay che assomiglia molto
    mancano pero tutte le specifiche sulla MB/pcu e sul prezzo

    my fault, you were right

    I had to give up about the MS Linux container on Windows (Ubuntu 18.04 lts app from MS store) as far as believe it or not....there were not the kernel headers in the repo (being is a Ms 4.4 kernel and having the repo just 4.15 kernels)
    SO I went with the TunSafe Client for Windows, thus the Wireguard's author strongly advises against it
    Now there is a networking issue
    How does wireguard pushes the default route?
    I found misleading how-to on the internet
    At the beginning I thought the AllowedIPs = was meant to be an extra check about the client identiy and to better categorize them
    but someone is writing that this is the mask that will be pushed to the routing table
    What if I want the VPN to be used ONLY to reach the server LAN and not to route all of the traffinc?
    Do I have to forge the virtual lan subnet to be supernetted with the remote lan subnet?
    This was not a issue on OpenVPN, I mean I can have a remote LAN and a VPN subnet and everything was used to work

    Is it something I have to write on the client or on the server wireguard config file (or both)?

    I have want to pay some credit to this guy as far as I found it the more clean and complete how-to about wireguard configuration
    expecially for those who want to set up the typical environment of a VPN server + many road warrior clients…eguard-vpn-typical-setup/

    Hi, I'm running OMV since 1.x as a VM on a lovely Hp microserver gen7 running ESXi (now 6.5)
    I upgraded and tweaked bot the hardware (ssd, 8TB drivers, etc) and the sofware (esxi 6.5, OMV4.x) always looking to get better performance from such a limited hardware
    Since my OMV4. runs OpenVPN as a server and WireGuard recently jumped to general news....
    I've been astonished by the promised througput and little cpu overhead

    I was tring to install in on the OMV4.x (Debian Strecht based) and in an Windows Linux container (the Ubuntu 18.04 LTS from the MS Store)

    I've installed the wireguard packages, and filled the config files on both the Debian server and the ubuntu client
    but once I try to add the interface running command

    ip link add wg0 type wireguard

    I get the following error messages:

    on Omv4.0 -debian

    RTNETLINK answers: Operation not supported

    on Ubuntu 18.04 (win 10 container)

    RTNETLINK answers: No such device

    kernel info UBUNTU client

    Distributor ID: Ubuntu
    Description:    Ubuntu 18.04 LTS
    Release:        18.04
    Codename:       bionic
    Linux HP-840 4.4.0-43-Microsoft #1-Microsoft Wed Dec 31 14:42:53 PST 2014 x86_64 x86_64 x86_64 GNU/Linux

    kernel info Debian (OMV server)

    Distributor ID: Debian
    Description:    Debian GNU/Linux 9.4 (stretch)
    Release:        9.4
    Codename:       stretch
    Linux OPENMEDIAVAULT 4.16.0-0.bpo.2-amd64 #1 SMP Debian 4.16.16-2~bpo9+1 (2018-06-26) x86_64 GNU/Linux

    Searching on the internet there is still very little documentation given the WireGuard project is still a BETA and it's kernel support is quite new