Posts by Moan

  • Questions about remotemount changes

    Quote from ryecoaaron

    You mean the update from 6 months ago?


    Oh, I thought it was changed on 15th of May (last GitHub commit), but I wasn't updating / changing OMV settings for a while.


    Quote from ryecoaaron

    Yes. systemctl start srv-remotemount-name.mount where name is replaced with the remote mount's name will mount. Using stop will unmount.


    Thank you for that command! It will be useful if I ever decide to use remote shares for something else.


    Quote from ryecoaaron

    I wouldn't use the plugin for this.


    Yeah, I agree. I used to execute rsync from OMV panel a few years ago, but then I moved to a self-made .sh script with more customizations and prompts for the rsync job. I still used remotemount plugin as I thought I would need it for something else. But for now it will be enough to call the `mount -t cifs` command directly from that script.

  • Questions about remotemount changes

    After the remotemount plugin update, there are some (probably expected) changes:


    1. The shares are not longer added to /etc/fstab

    2. The mount passwords are stored as a plain text in /etc/openmediavault/config.xml


    Question 1: Is it possible to mount a remotemount share using some linux command? I use some custom scripts for rsync, and I only used to mount remote shares when it was needed by editing entries in /etc/fstab. Now, I'm not sure how to enable/disable the shares mounting from a bash script directly.


    Question 2: Are plain-text passwords in the config file expected? If I remember correctly, it wasn't this way before.

  • Unable to find the remotemount plugin

    Quote from gderf

    Have you installed omv-extras yet?


    Thread
    OMV-Extras.org Plugin
    Installation of OMV-Extras.org

    Description
    OMV-Extras.org is a plugin which enables you to do several things...
    • Install proxmox kernel
    • Install even more plugins.

    Installation

    From command line as root (preferred method) and only method for OMV6 and OMV7


    wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash

    OR

    From OMV web interface (alternative method)

    • Download the plugin to enable this repository here:
      • For OMV 4.x (arrakis) -
    …
    WastlJ


    Thanks. I was using OMV 5 for around 2 years and the remotemount plugin was available. Then after some apt upgrade the OMV login page didn't load (error 403) so I reinstalled OMV using `apt-get install --reinstall openmediavault` and then the plugin did not show up.


    I didn't have to install omv-extras before as I was using the armbian-config menu. I installed it now by:

    Quote

    wget -O - https://github.com/OpenMediaVa…ckages/raw/master/install | bash


    ...and many more plugins appeared. Thanks for help.


    I'll be upgrading to OMV6 soon, but currently I don't have enough time to prepare for it (backup, tests, etc.), so I decided to wait a bit longer.

  • Unable to find the remotemount plugin

    I've got a problem installing the remotemount plugin on OMV 5.6.26-1 (Usul).

    It's not listed in System - Plugins, and executing apt gives:



    How can I fix it?

  • Problem with the USB Disk performance after setting the Advanced Power Management for the first time

    OK... I think I know the reason of this issue. I missed the "Write cache" option. Since I never touched it, I thought it would be unchanged.. Once I enabled it in OMV settings for this disk, the problem is gone :)


    I understand that this would be hard to determine default options for each disk type, so I guess it's the best the way it is now. Just maybe some switch to disable the overall hdparm for a disk could be useful.

  • Problem with the USB Disk performance after setting the Advanced Power Management for the first time

    Hi guys. I'd like to share my experience with the recently purchased USB disk: WD Elements 18TB.


    After I purchased the disk I set the "Advanced Power Management" and the "Spindown time" in the physical disk performance menu.

    I noticed, that the write speed to this disk (EXT4) was very reduced. I used the following command to test it:

    Quote

    dd if=/dev/zero of=/srv/dev-disk-by-uuid-XXX/nullbytes count=100000 bs=10M

    The writing speed was never more than 80MB/s.

    Shortly after I detected problems I set APM and Spindown to Disabled, in hope to restore the default configuration. The problem was not gone. I flashed a clean Armbian image to my Odroid N2 device, and I noticed that the problem is gone. So I gave up trying to fix it, and I reinstalled everything (clean OS image, set up OMV, and other things from beginning). The writing speed using the same command was 250-270MB/s.


    Today, I wanted to set up the disk spindown time again. Right after I did it in OMV settings, I noticed that the problem with max. 80MB/s returned. After I disabled APM and everything else to Disabled, and rebooted the device - problem persisted. This time I knew that it must be OMV still doing something, so I found the following in `/etc/openmediavault/config.xml`:


    I then tried to set AAM to Max performance in order to fix it, so ended up with the following config:


    But nothing helped. 80MB/s was the max speed I was getting to that disk.


    Due that setting everything to "Disabled" wasn't fixing the problem, I manually edited config.xml and removed `<hdparm></hdparm>`. Then I changed and applied some other settings in OMV panel to update the config. After reboot, the writing speed to the disk is back. So I now get 250MB/s+


    I now use an external cron .sh script to set the spindown time:

    Quote

    /usr/sbin/hdparm -B 127 $DiskInfoElements

    /usr/sbin/hdparm -S 48 $DiskInfoElements


    It seems to work fine, the write speed is 250MB/s+, and the disk goes to the sleep mode after inactivity.

    However, after 1-2 days these settings are reset. I used command `hdparm -I /dev/sdX | grep Advanced` to test it.


    Is it possible that OMV is periodically checking these settings and resets them?


    My OMV version is:


    I think this is a bug that hdparm is still doing something, when it's Disabled in OMV settings.

  • add webdav to remote mount plugin

    For me 5.0.2 breaks OMV Shared Folders tab:


    Code
    Error #0:OMV\Rpc\Exception: Invalid RPC response. Please check the syslog for more information. in /usr/share/php/openmediavault/rpc/rpc.inc:187Stack trace:#0 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('ShareMgmt', 'getCandidates', Array, Array, 3)#1 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()#2 {main}


    Removing the plugin fixes the issue, but... can't use remote-shares.
    I'm on version 5.2.6-1 (Usul).


    I tried reinstalling the plugin. I was able to add Remote Mounts which appeared in /etc/fstab correctly, but I can't add them to Shared Folders.


    syslog:


  • Will OMV5 support the remote-mount plugin?

    Quote from ryecoaaron


    I just fixed the plugin a little bit ago. 5.0.1 is in the repo. Removing the replace line is not the correct fix. It is just supposed to replace spaces with \\040.


    Perfect. Thank you. I don't have shares with spaces in name, that's why my edit didn't cause problems for me.
    I can confirm that after "apt upgrade" everything works as expected.

  • Will OMV5 support the remote-mount plugin?

    Thank you. Unfortunately, for now it doesn't want to work for me:

    Quote

    0 2 +//192.168.1.130/40b40e40r40n40a40d40e40t40a40 /srv/402be38b-a450-4be2-a1f7-6433854231d9 cifs _netdev,iocharset=utf8,vers=2.0,nofail,credentials=/root/.cifscredentials-11a9d9b9-265b-41bf-b8a6-c45da5a6a5f8 0 0 # <<< [openmediavault] Summary for odroidn2 ------------- Succeeded: 10 (changed=5) Failed: 1 ------------- Total states run: 11 Total run time: 911.169 ms


    I noticed that /etc/fstab has:

    Quote

    //192.168.1.130/^@40b^@40e^@40r^@40n^@40a^@40d^@40e^@40t^@40a^@40 /srv/402be38b-a450-4be2-a1f7-6433854231d9 cifs _netdev,iocharset=utf8,vers=2.0,nofail,credentials=/root/.cifscredentials-...


    is "^@40" an expected encoding for the share name?


    When I removed the remote share from the "Remote Mount" page, the configuration saved successfully, so I'm sure it doesn't fail due to any other local mount.


    EDIT:
    (this is the line with new entry)

    Quote

    root@odroidn2:~# mount -a


    mount: /etc/fstab: parse error at line 8 -- ignored


    EDIT2:
    I manually edited file:
    /srv/salt/omv/deploy/fstab/90remotemount.sls


    And replaced:
    {% set share = '//' + mnt.server + '/' + mnt.sharename | replace('', '\\040') %}
    to:
    {% set share = '//' + mnt.server + '/' + mnt.sharename %}


    And the problem is gone.


    Thank you once again for this plugin!

  • Will OMV5 support the remote-mount plugin?

    Quote from ryecoaaron

    If the old server supports rsync, you don't need remotemount.

    Thanks for the explanation!


    The old NAS doesn't support the rsync server, or anything like this. I will just add cifs mounts to /etc/fstab, and will execute the rsync commands manually from terminal. Not a problem. Just wanted to know if this was abandoned or not :)

  • Will OMV5 support the remote-mount plugin?

    Hi. I successfully installed OMV5 BETA on Armbian Buster. Everything seems to work fine :)


    I've got a question about the "remote-mount" plugin which I used on OMV4 for the old NAS backups.
    Will this plugin be available in OMV5? If yes, is there any known ETA for it? I'm asking, because if this plugin was dropped, then I will already try to find an alternative for it.


    Greetings.

  • Remote Mount - randomly wakes up external NAS from the sleep mode.

    Thank you for the answer and confirmation that there is no extra deamon in this plugin running in the background.


    This "WDMyCloud" disk is a "budget" NAS solution. It has no flash memory, and the actual operating system files are stored on the same HDD as shares. It causes problems where any connection to this device starts spinning the disk. For example, my openmediavault has 3 external USB3.0 disks connected. When I'm listing Samba shares on openmediavault - external disks are not "waking up" until I actually access them. When I do the same thing on the "WDMyCloud", it will wake up the disk immediately.


    I suppose Armbian (which has openmediavault installed) might have some background checks for smb shares mounted by fstab. This is a bit strange since USB3.0 disks don't have this problem.


    I will try to check packets with tcpdump. The only issue is, it sometimes starts happening after few days since the Odroid device reboot. So it's not easy to reproduce. Remote Mount shares are not used in any "Services" (SMB, NFS), so Kodi or other programs can't access it. I only noticed that removing this Remote Mount (which is actually rarely used by manual Rsync tasks) prevents that WdMyCloud device from often wake-ups.


    Anyway, I think it's not even worth to focus on this problem that much. The "WdMyCloud" device is a bad construction for using HDD to store OS files. It would probably be easier to install third-party OS on it by chroot on some USB stick.

  • Remote Mount - randomly wakes up external NAS from the sleep mode.

    Hi.
    I've got an old "WDMyCloud" NAS, which is very sensitive to any access, and often wakes up from the sleep mode when there is any access to it.
    I now use openmediavault for different, USB3.0 HDDs and I set manual Rsync jobs.
    For that, I had to mount the Shares from the old NAS using the "Remote Mount" plugin.


    I noticed, that when this plugin is installed, the old WdMyCloud NAS wakes up more often. Those are random wakeups, but sometimes (after longer uptime) they can change into constant wakeups (every 20 minutes and 49 seconds). The constant wakeups are solved by device reboot with openmediavault (currently Odroid N2, but it used to be Odroid XU4 before).


    Does "Remote Mount" plugin issue any commands to check for the remote shares presence or something? If yes, is there anything I could do to configure it to skip those checks?

  • Why is my HDD waking up?

    Quote from mattcony

    Is this the same sort of activity you were seeing @Moan before you disabled SMART ?

    Sorry, I don't remember what it exactly shown, but "Loaded: loaded (/lib/systemd/system/smartd.service; enabled" was displayed as well.
    When I stopped this service it shows disabled. Now disks never wake up when not needed.


    I hope it solved your problem.
    By the way, I store Plex database on the main SD card, not the external disk. If you have a different configuration it can cause those wake ups.

  • Odroid XU4 - can't start OpenMediaVault 4

    Quote from JohnStiles

    Next time, start the discussions with "I have a Chinese SD card"....

    With that logic we shouldn't be using 90% of devices, because they have parts produced in China.
    This "MIXZA TOHAOLL" has many good reviews. After all I did some tests and it seems to work fine. No fake size, no damaged files. Most likely it only had problems to work with kernel 4.9.

  • Odroid XU4 - can't start OpenMediaVault 4

    Thanks. I thought it was already an accessible filesystem :[


    For now I flashed the .img backup of the Chinese card to the new one, because I already set up everything on it.


    I'm happy it was the SD card issue, I was worried that I'll need to replace PSU. It's still strange, because that card seem to work fine, however I'm not gonna risk using it for anything else than tests.


    Once again thanks for help.

  • Odroid XU4 - can't start OpenMediaVault 4

    Hi.
    Today I received a new microSD card (SanDisk Ultra 32GB microSDHC UHS-I A1) and seems like booting from the "OMV_4_Odroid_XU4_HC1_HC2.img.xz" image worked fine.
    My old card is a Chinese "MIXZA TOHAOLL".


    I did some IOPS benchmark using "fio", and results are a bit confusing. Seems like that old card is better at writing. I attached test results if someone is interested:
    ChineseCard_IOResults_2019-02-07-15-13-07.txt
    SanDiskCard_IOResults_2019-02-07-15-33-17.txt


    One thing I'm not sure about is the "/dev/mmcblk1p3" partition:
    Device Boot Start End Sectors Size Id Type


    /dev/mmcblk1p1 8192 139263 131072 64M 83 Linux


    /dev/mmcblk1p2 139264 15500000 15360737 7.3G 83 Linux


    /dev/mmcblk1p3 15500001 61710591 46210591 22G 83 Linux


    I can't see it in Disks -> File Systems. Can it be somehow used, at least for Plex database?

  • Odroid XU4 - can't start OpenMediaVault 4

    Quote from JohnStiles

    If you are not able to force this image from sourceforge to work then just use pure armbian (deb) and add omv. You will have exactly the same thing.

    Yes, this is what I did and it works perfectly fine.


    I still want to try this "OMV_4_Odroid_XU4_HC1_HC2.img.xz" image when I get the new card. It's because I'm curious what's wrong. When something fails that hard only for me and nobody else, then there might be a hardware issue, so I maybe should refund this device.

  • Why is my HDD waking up?

    I had exactly the same issue with external disks waking up every 30 minutes. Both of them at once.
    I'm using "Armbian Stretch 4.14.y" with the newest version of OMV on Odroid XU4.


    I was trying to detect what process accesses my external drives, using the following commands:
    inotifywait -r -m /srv/dev-disk-by-label-EXTERNAL8TB/ /srv/dev-disk-by-label-EXTERNAL4TB/
    lsof -r1 | grep -E '(EXTERNAL8TB|EXTERNAL4TB)'


    But it didn't show anything when disks started spinning up for the next time.
    In OMV Control Panel -> Storage -> S.M.A.R.T, "Enable" switch was off.


    However, smartd was running:
    sudo service smartd status


    So I stopped and disabled it:
    sudo systemctl disable smartd.service
    sudo service smartd stop


    And no more wake-ups :)


    I know it's an old topic, but I hope someone will find this information useful.