Posts by NAST

    =====================================================================================================
    Latest Update:
    As of Nikolaus Day (2013/12/6) - I did upgrade to OMV 0.5.25 including the latest updates.
    Ownclould could be activated and seem to run ok!

    =====================================================================================================


    =====================================================================================================
    Update: It should not have made it to the repository as Volker seem to be working on it. So for now STAY away from it!
    But it might not show up in your list anyway b/c it got pulled
    It is not ready yet - but Volker is working on it!

    =====================================================================================================
    For now it killed my machine after I tried to remove the plugin and a reboot - be careful
    =====================================================================================================
    Hi there,


    I happen to update my system as of just a few minutes back (N40L x64 64bit system)...and I found a owncloud plugin saying it is based on version 0.5.13. :D
    Enabling went fine -- but it did not show up ... really.


    But when I rebooted the system - it came up quite happily and I found a new 'owncloud' option under the services tab.
    Enabling it there did not go that well:


    Code
    Error #4000: exception 'OMVException' with message 'Failed to execute command 'export LANG=C; invoke-rc.d 'apache2' graceful 2>&1': Syntax error on line 7 of /etc/apache2/openmediavault-webgui.d/owncloud.conf: Wrapper /var/www/owncloud/php-fcgi cannot be accessed: (2)No such file or directory Action 'configtest' failed. The Apache error log may have more information. failed! invoke-rc.d: initscript apache2, action "graceful" failed.' in /usr/share/php/openmediavault/initscript.inc:169 Stack trace: #0 /usr/share/openmediavault/engined/module/apache.inc(59): OMVSysVInitScript->invoke('graceful') #1 /usr/share/openmediavault/engined/rpc/config.inc(198): OMVModuleApache->startService() #2 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array) #3 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array) #4 /usr/share/openmediavault/engined/rpc/config.inc(247): OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array) #5 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array) #6 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array) #7 /usr/share/php/openmediavault/rpc.inc(62): OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array) #8 /usr/sbin/omv-engined(495): OMVRpc::exec('Config', 'applyChangesBg', Array, Array, 1) #9 {main}


    So when I hid enable and then hit apply - the above happens


    So it is some broken?
    I hope it did break any other things...


    NAST


    Supportinfo:

    I just found ownloud as a regular plugin... announced in the updates...


    Anyone tried yet!?


    NAST


    PS. It showed up under services only after a reboot...

    Well, the OwnCloud is one of the bullet point for the 0.5 release - at least the roadmaps says so.
    ;-) !


    Glad to hear that the development was not halted and it is progressing.


    NAST

    Hi there.


    I am also interested in the Owncloud plugin for OMV - I almost thought it was forgotten about. I picked somewhere that 0.6 is expected in early 2014 - is that correct (remember the support runs out for the current debian version soon)?


    So we can be sure to get the plugin before that!?


    Thanks,
    NAST


    Looks like the same I did experience...have a look here:
    http://forums.openmediavault.org/viewtopic.php?f=10&t=3039


    A workaround here might be a manual downgrade (in the command line) ..see if you get it mounted and then upgrade to 0.5.18.
    But this might be only useful if the drive stays connected permanently....
    Otherwise just try the downgrade...w/o a update.


    NAST

    Quote from "x-lette"

    My experience:
    After installing two additional harddrives to my omv box I did see them in the list of harddrives and I also could create a filesystem on them but this filesystem could not be mounted. Reason: no entries in /etc/fstab were created after initialising the filesystem. ...


    Currently running OMV 0.5.18



    I do not think it is related to having edited the fstab - but I am not sure.
    if this does not matter it seems that all are affected by this bug who want to add drives even to an existing setup running 0.5.18.


    NAST

    Quote from "tekkbebe"

    You are not seeing device /dev/sda in filesystems sections of OMV because there is a filesystem on it already. Thus you are seeing /dev/sda1. A storage deivce before it has partitions or filesystems on it will appear like these examples /dev/sda, /dev/sdb. /dev/sdc. One you partition it or put a filesystem on it the have you have names like /sda1, /sda2, sdb1. So if you see anything with a number after the letters you know it has a partition or filesystem on it.


    Even with a file system on there - it should be 'mountable' or am I mistaken?


    Thanks,


    NAST

    Quote from "KM0201"

    Having the same problem on a vbox install.


    I almost thought I be the only one affect - looks like a serous bug for anyone hooking up a disk w/ data to fresh install of OMV.


    Workaround kind'a
    I did - as suggested - downgrade to 0.5.17 with having the drive in place... I could mount it with no problem.
    Then I did the upgrade via the GUI and the drive is still there running 0.5.18.


    So that can serve as a workaround for anyone on a fresh install facing these problems until the problem is fixed.


    NAST

    Quote from "Solo0815"

    Is the version 0.5.17 still existant?
    If no:
    Feature Request:
    After the release of a new version, the old one should be in the repos, so that users like NAST can downgrade.


    I double that... at least the previous version should remain...


    It seems so that the old version vanished from the repo .. at least that is what I get:


    Code
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    E: Version '0.5.17' for 'openmediavault' was not found


    Thanks,
    NAST

    Quote from "votdev"

    Will be fixed in openmediavault 0.5.19.


    So it is a bug!?
    Since I seem not being able to go back to 0.5.18 I need to wait.
    I wonder if I am the only one affected? Can that be!?


    Cheers,
    NAST


    BTW would a disk - empty so it can be formated by OMV - make a difference at all?

    Hi Volker,


    as requested:


    Code
    /dev/sda1: LABEL="Storage" UUID="e8298cfa-9ccf-4efd-836f-47931485c57e" TYPE="ext4"
    /dev/sdb1: UUID="6c37eaf1-1653-47bb-b978-3ff3b00e9483" TYPE="ext4"
    /dev/sdb5: UUID="2541a7b4-97dd-49ea-afa3-d9b7cf4d67e3" TYPE="swap"


    and


    Code
    major minor #blocks name
    8 0 244198584 sda
    8 1 244197376 sda1
    8 16 3948544 sdb
    8 17 3732480 sdb1
    8 18 1 sdb2
    8 21 212992 sdb5


    SDA and SDA1 - are they the same but then not?


    Thanks,


    NAST

    Quote from "Solo0815"

    you can try downgrading

    Code
    apt-get install openmediavault=0.5.17


    ^^^ can't test, if the command works atm, sorry


    Thanks for the reply... I would if I could...


    apt-get install openmediavault=0.5.17 gives me:


    Code
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    E: Version '0.5.17' for 'openmediavault' was not found


    Yes the machine is connectd to the http://WWW...


    Thanks,


    NAST

    Hi there,


    I am pretty new to Linux in general and even more so if it comes to OMV and NAS server. I am facing an odd problem - I think.
    Checking the forum did not help me (the search does not produce any viable output...).


    I own a little N40L and I am testing OMV. Most of the installation went along the lines you can find http://www.och-group.de/2013/0…-und-debian-installieren/.
    Before I get the bashing yes it runs off a USB key - I have tried Microdrive (via USB) etc. before but it stopped working. It is meant for testing and that sort of for now.


    ====================================================================================
    Update: Issue got fxed in 0.5.19
    Thanks Volker
    ====================================================================================


    0.5.17 vs 0.5.18
    The server comes with 250GB harddrive which should pose as the data drive for now. I did use it with a previous installation (0.5.17) and it was recognized and mounted ok - but with
    0.5.18 I see the device but I can not mount it via the GUI. The drive already holds data I do not want to lose.


    /dev/sda VS /dev/sda1?
    As I can see the harddrive in the 'Physical Disks' (/dev/sda) next to the USB stick (/dev/sdb) I can still not mount it in the filesystem section.
    There it shows only a dev/sda1 device - nothing more. When I attempt to mount it - it says ' device not found' which is quite logical as the device I would be expecting here is /dev/sda only.


    Any idea how to fix this?


    NAST


    Here is the support info - if anyone might ask:


    Some more - error details when attempting to mount:

    Code
    Error #6002: exception 'OMVException' with message 'Device '/dev/sda1' not found' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:665 Stack trace: #0 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array) #1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array) #2 /usr/share/php/openmediavault/rpc.inc(62): OMVRpcServiceAbstract->callMethod('mount', Array, Array) #3 /usr/sbin/omv-engined(495): OMVRpc::exec('FileSystemMgmt', 'mount', Array, Array, 1) #4 {main}


    PS. admin: I can not post the support info as it is consideres spam...!??
    search is not working really...



    ====================================================================================
    A workaround - Solution for anyone facing the same problem:
    1. Step : Downgrade to 0.5.17 0 maybe log in your server via SSH (if you can):

    Quote from "ryecoaaron"

    Go here. All the versions are there.


    Code
    wget http://packages.openmediavault.org/public/pool/main/o/openmediavault/openmediavault_0.5.17_all.deb
    dpkg -i openmediavault_0.5.17_all.deb


    2. Step : You should now be able to mount the drives
    If you have just USB drives (not connected permanently - you might want to stay with 0.5.17 though) [?]
    3. Step : Update the system to 0.5.18 - the drives will be still there and mounted!



    At least it worked for me ;-) !