Posts by QSx

    Not sure if relevant but here goes anyways:

    For Windows 10 users - Microsoft silently disabled SMB 1.0 in latest Win 10 patches (because of previous cryptolocking crap spreading that way)...

    I find it somewhat weird that Win 10 machine needs several attempts to "get it to work" when using only SMB 3.X (RDMA or Samba Direct).

    Which Samba is OMV 3.X using?

    When I reenable SMB 1.X support it works right away...

    P.S. (All of the previous instructions were applied)

    Just a quick question - since I haven't found a direct answer reading previous stuff:

    Should I use Docker or Docker CE repo from OMV-Extras?

    I'm using 3.0.90 ATM with 3.4.29 extras

    I'm planning to use UniFi and possibly nextcloud


    Yeah, very nice change - too cozy (spacing-wise) and grey though...

    Heavier/darker font and less spacing would be perfect, but great job nonetheless!


    I got impatient and reinstalled my system from bare metal. I just have a quick question:

    Upon first run (after installing amd64 3.0..58 iso), we are offered a ton of packages related to backports, also including latest kernel image and omv (no omv-extras or any plugins yet). There's still conflict between firmware-misc-nonfree and firmware-adi/firmware-ralink packages. Unselecting those two however results in nice and clean update, and those two packages never reappear.

    Is that the recommended way of updating new install or should I go around some other way?

    Well, still got trouble here - I think the latest kernel is the culprit or something that has to do with my NIC drivers

    Since eth2 error keep appearing in log i tried omv-firstaid and then manually setting the network

    Again it failed - i got this error (if it helps)

    At this point, I'm considering rolling back on previous kernel (is it possible) or slapping another NIC in that machine until whatever got borked gets fixed...

    For starters, how would I roll back on today update? Booting old kernel from bootmenu only hangs at "Loading folder2ram systemd service..."

    UPDATE: Okay, I disabled onboard chip and slapped on PCI NIC - same crap... any ideas boys?

    (Doubleposting because of 10K character limit)

    I managed to disable UPS/nut - without webui complaining (collectd still fails to start but machine boots normally now)

    Any attempted change of System/Network fails with this error:


    I enabled nut again / network remains stuck at DHCP (still can't change it due to aforementioned error) - I am greeted by similar (monit) error this time:

    In short, after today's update (it was combined web update of over 20 lib*, new kernel and omv-extras + OMV 3.0.65), collectd keeps hanging/cannot start.

    Also there is severe delay in booting (according to log due to network trouble - failure to get ip form dhcp?? - nothing changed on my dhcp, all other machines wired or wireless work fine on my network).

    I have pretty vanilla OMV with omv-extras/plex/nut/torrent/sensors plugins - nothing fancy was done to the machine otherwise (hardware or software-wise)

    Here's the boot log:

    And the syslog (part relevant to collectd):

    Could it be that nut somehow kills collectd?

    I will try to set IP manually & disable nut to see if anything changes

    Not sure of it though,

    the problems started appearing after yesterday (02.02.) update - I didn't notice any omv or plugin specific updates but what it looked like general ones for OS. I'm sorry now I didn't write it down :( I'm pretty sure backport 4.9.0 was among theese.

    Anyways, upon reboot OMV wouldn't connect to phpVirtualBox throwing error:

    Error #0:
    exception 'Exception' with message 'Could not connect to host (' in /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php:220
    Stack trace:
    #0 /usr/share/openmediavault/engined/rpc/ vboxconnector->connect()
    #1 [internal function]: OMV\Engined\Rpc\VirtualBox->getMachines(Array, Array)
    #2 /usr/share/php/openmediavault/rpc/ call_user_func_array(Array, Array)
    #3 /usr/share/php/openmediavault/rpc/ OMV\Rpc\ServiceAbstract->callMethod('getMachines', Array, Array)
    #4 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('VirtualBox', 'getMachines', Array, Array, 1)
    #5 {main}

    Any attempt to disable phpVirtualBox is met with Bad Gateway error and ultimately spits this out:

    This is what syslog says:

    Feb 3 08:09:02 nas systemd[1]: Starting LSB: VirtualBox Linux kernel module...
    Feb 3 08:09:02 nas systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
    Feb 3 08:09:02 nas virtualbox[5456]: Loading VirtualBox kernel modules...No suitable module for running kernel found ... failed!
    Feb 3 08:09:02 nas virtualbox[5456]: failed!
    Feb 3 08:09:02 nas systemd[1]: virtualbox.service: control process exited, code=exited status=1
    Feb 3 08:09:02 nas systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
    Feb 3 08:09:02 nas systemd[1]: Dependency failed for VirtualBox Web Service.
    Feb 3 08:09:02 nas systemd[1]: Unit virtualbox.service entered failed state.

    I also tried removing then installing the plugin again ( the windows way :D:D:D ) with same results - I've since completely disabled it.

    Anyone knows more about this? Looks like borked/missing kernel module?

    Since i've installed omv 3, syslog is getting filled with stuff like this:

    Two lines per minute - it's nothing horrible but makes looking for other stuff more difficult...

    Is this normal behavior or ?


    I've found this

    It appears to be very old bug? But it's supposed to be fixed since 2011something...


    After running omv-update those packages dissapeared :)

    I did notice something else however:

    W: Duplicate sources.list entry jessie-backports/main amd64 Packages (/var/lib/apt/lists/httpredir.debian.org_debian_dists_jessie-backports_main_binary-amd64_Packages)
    W: Duplicate sources.list entry jessie-backports/contrib amd64 Packages (/var/lib/apt/lists/httpredir.debian.org_debian_dists_jessie-backports_contrib_binary-amd64_Packages)
    W: You may want to run apt-get update to correct these problems

    Running apt-get update didn't fix the problem - is it safe to delete one of two entries or is there another way around it?