Posts by gderf

    I've only been using it for the last three months and haven't had any trouble with it.


    Am I mistaken, or is the OMV repo currently six days behind?


    plexmediaserver_0.9.12.12.1459 has been available since September 12 on the ninthgate.se repo.

    I have a few data folders aufs mounted to /home/sftp/ which is a chroot for the sftp server. The reason it's on the rootfs is that I need logging within the chroot and I could never get that working when it was off the rootfs.


    I guess I could go thru the trouble to change that setup to use /home/ftp instead which is excluded.


    When this backup plugin is run, does it do versioning and consolidation or is only one version kept and overwritten. How can it be scheduled?

    I make nightly backup images of my entire OMV system drive using dd via cron, and also rotate those backups keeping only the most recent three. The backups are scheduled to take place when the system is not in use by humans, and I don't care if some log files might change during the backup. I have verified that these backup images do actually restore to media that boots and behaves as it should.


    It's pointless to undertake any backup strategy, regardless of its origin, if you don't verify that the backups can actually be successfully restored and operate as intended.

    This is what happens when you install Jessie packages on Wheezy.


    For those who find the cited thread on forums.plex.tv TL;DR. If you are going to use the plex.tv Ubuntu (Jessie) packages, you will need to make a backup copy of the current /etc/init.d/plexmediaserver script before installing the package, then restore it after installing the package.


    And a direct link to the debian package if you are impatient and don't want to wait until OMV pulls the package into their repo:


    http://shell.ninthgate.se/pack…l/main/p/plexmediaserver/

    You could probably figure out what changes to make to the /etc/fstab file to mount that drive at bootup.


    But you have to know what you are doing, and making mistakes inside that file can cause problems, maybe even prevent OMV from booting at all.


    Something you could try that is less risky is to install the usbmount package. I use it and it works for me. But I do not have a USB hub between my drives and OMV box.

    I have three users with folders in /home which is on the system drive.


    /home/fred
    /home/sftp
    /home/extplorer


    The chroot'd user sftp is for chroot'd sftp service.


    Settings in Access Rights Management does not allow the system drive to be selected, only data drive volumes can be selected.


    Here is exactly what I am adding, the stuff for [root] is accepted, the stuff for [sftp] is not.


    [root]
    guest ok = yes
    writable = yes
    public = yes
    path = /
    force user = root


    [sftp]
    read list =
    write list =
    force directory mode = 0755
    store dos attributes = no
    guest ok = no
    create mask = 0755
    hide dot files = yes
    ea support = no
    inherit acls = yes
    writable = yes
    inherit permissions = no
    printable = no
    invalid users =
    path = /home/sftp
    force create mode = 0644
    comment = sftp on omv
    directory mask = 0755
    valid users =

    Add your changes to extra options boxes


    This does not fully work. Some of the things I add to the extra options box do appear in smb.conf, but others do not.


    What I am trying to add is a share for a chroot'd user who has a folder in /home. It works fine if I enter it by hand into smb.conf, but placing it into the extra options box and saving doesn't get it into the smb.conf file.


    This user's files also do not appear in the homes share if enabled.

    I have made manual by hand edits of /etc/samba/smb.conf because the types of shares I wish to offer can not be created in the OMV Services | SMB/CIFS module.


    It would be nice if I could do the types of things I need via the OMV module, but what really gets my goat is that once I have made changes by hand, going back and using the module for other reasons does not preserve those manually made by hand changes. smb.conf is rewritten to reflect only what the module shows and allows. Basically, this eliminates all possible future use of the module by me.


    Can this be fixed?

    I have three WD 3TB reds in my OMV. Looking at the prices you posted, I would take the HGSTs as from what I have read their failure rate is lower.

    When OMV is installed to a drive it takes over the entire disk. OMV plugins are stored on the same drive, and you can install other Debian packages you want on the drive too. What you can't do is change the partition layout, at least not easily. I have 16GB of RAM, but it will run in less.