Posts by jeff0001

  • Is it okay to spin down an HHD to save energy?

    I'm by no means an expert at all, but I've not been able to find any research that draws a conclusion either for or against letting drives spin constantly. Obviously it seems to make sense that starting and stopping wouldn't be good for them and your spin down time would significantly impact any data points, but does anyone have any links to research on the topic?


    For my use case, my drives will have 6-10 hours between activity so I do have them spin down and my snapraid parity drive is only in use for a few minutes per week so that's spun down pretty quickly. However, as mentioned by others, their disks might be in use constantly and need to have minimal latency when accessing so it makes sense to keep them running.

  • Can't Disable FTP from UI

    I am receiving an error when trying to disable FTP from the UI. I'm on the latest version of OMV and have installed FTP via the plugin section. I've tried removing and reinstalling but am always met with the same error below when disabling FTP and have to either remove the plugin to stop it or kill the service and stop monit from restarting it.


    I am thinking it is related to this commit, or at least the originating bug, as the error message I received is the exact same one mentioned by Volker (I think). https://github.com/openmediava…7d7bad12bdb04bc153f878bec


    Error:

    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color proftpd 2>&1' with exit code '1': debian:

    Data failed to compile:

    ----------

    Cannot extend ID 'start_proftpd_service' in 'base:omv.deploy.proftpd.modules.20mod_wrap'. It is not part of the high state.

    This is likely due to a missing include statement or an incorrectly typed ID.

    Ensure that a state with an ID of 'start_proftpd_service' is available

    in environment 'base' and to SLS 'omv.deploy.proftpd.modules.20mod_wrap'


    OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color proftpd 2>&1' with exit code '1': debian:

    Data failed to compile:

    ----------

    Cannot extend ID 'start_proftpd_service' in 'base:omv.deploy.proftpd.modules.20mod_wrap'. It is not part of the high state.

    This is likely due to a missing include statement or an incorrectly typed ID.

    Ensure that a state with an ID of 'start_proftpd_service' is available

    in environment 'base' and to SLS 'omv.deploy.proftpd.modules.20mod_wrap' in /usr/share/php/openmediavault/system/process.inc:220

    Stack trace:

    #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()

    #1 /usr/share/openmediavault/engined/rpc/config.inc(174): OMV\Engine\Module\ServiceAbstract->deploy()

    #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)

    #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)

    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusIC...', '/tmp/bgoutputui...')

    #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))

    #7 /usr/share/openmediavault/engined/rpc/config.inc(195): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)

    #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)

    #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)

    #11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)

    #12 {main}

  • OMV without nfs v4 server

    If I'm not mistaken, since the pseudo root directory of nfsv4 share is already /export then you wouldn't mount /export/xyz/, just connect to the ip and port of your server then the shared directory.


    The way you're trying to mount is basically server/export/export/NFS_TEST which would be interpreted as an NFS v3 path by the client/server... I think


    So you should connect like server/NFS_TEST