Posts by klorinczi

    I need to configure the cron to execute a job every X hours.

    Unfortunately the GUI allows only hourly, daily execution, but not every X hours.

    I can set the cron.d file openmediavault-userdefined to use */2 but in this case cron is not executed at all.

    Could be possible to add the "every X hours" feature into the GUI?

    Konrad Lorinczi

    I get "Unexpected size change at file" error messages in cron email from coming from SnapRaid Sync for a lot files, which is changing often.

    How to avoid getting SnapRaid sync error messages for often changing files?

    Unfortunately I get the same result if I use the WebUI ACL dialog.

    I checked myuser to have RW permission.
    Also did set "myuser" as owner with RWX, and "users" as group with RWX, and "none" as others permission.

    Applied Recursively.

    Now it looks like:

    root@omvnas:/srv/12345678/home# ls -la
    total 24
    drwx--S--- 5 root root 4096 Apr 23 2018 .
    drwxr-xr-x 15 root root 4096 Jan 2 12:05 ..
    drwxrws---+ 2 myuser users 4096 Oct 3 2017 myuser
    root@omvnas:/srv/12345678/home# login myuser
    $ ls -la "/srv/12345678/home/myuser/"
    ls: cannot access /srv/12345678/home/myuser/: No such file or directory

    I accidentally changed owner of my shared directories.
    Now I can not regain access to a folder using myuser.

    sudo -u myuser ls -la "/srv/12345678/home/myuser/"
    ls: cannot access /srv/12345678/home/myuser/: No such file or directory

    I have access to the directory as root, but not as myuser.

    root@omvnas:/srv/12345678/home# ls -la
    total 24
    drwx--S--- 5 root root 4096 Apr 23 2018 .
    drwxr-xr-x 15 root root 4096 Jan 2 12:05 ..
    drwxrws---+ 2 root Users 4096 Oct 3 2017 myuser

    How to get access to it as myuser?

    So, it is ok to add 50 files to the plugin that would be doing the exact same thing as the extra options box that don't seem to cause anyone else problems? The rsync arguments have barely changed since I wrote this plugin and no one has ever had problems with socket files. I also don't want to have every little exclusion in the plugin. That is why I added the extra options box.
    And it wouldn't be 50 excludes. You would probably only have to add --no-specials --no-devices to the extra options box. I would add those options to the plugin but years worth of no problems tells me that could introduce other problems.

    See this:…les-during-rsync-transfer

    I had a problem, that not all files were showed from miniDLNA.
    I checked the files, but all files were on their place, none were missing.
    I checked the permissions of share, but they were right.

    All clients had the same problem, so I started to think, the problem comes from miniDLNA.

    Finally I tried this solution & worked:
    from Putty SSH client I tried this:

    service minidlna stop
    cd /var/cache/minidlna
    mv files.db files.db.old
    service minidlna start

    The files.db was recreated, and all the files were showed in all DLNA clients.

    I hope this will help other users, if they have the same problem.

    Sorry for the multiple posts.
    It seems Tapatalk have some problems with this forum.

    - OpenMediaVault v3.0.99 (Erasmus)
    - OpenMediaVault-Backup plugin v3.11
    - using EXT4 fs everywhere.

    You could exclude these files with extra options field.

    Extra options field is not the right way to exclude 50+ files...

    The plugin doesn't need to be fixed.

    The plugin should have option to ignore making backup of socket files...

    I made a backup of OpenMediaVault with backup plugin.

    But now I get the following errors in email:

    Could be possible to fix the backup plugin to avoid socket files, while doing backup?
    Can it cause problem, if these socket files are missing?


    I use OpenMediaVault server v3.0.99 (Erasmus) with Snapraid plugin for OpenMediaVault v3.7.3 installed (using snapraid v11.2 ). Debian GNU/Linux v8.10 (jessie).
    Using union filesystems plugin for OpenMediaVault v3.1.17 to merge the 4 data disks.
    Using 500GB to 1000GB hdds 4 data, 2 parity (aka RAID6 mode).
    Parity drives are both 1000 GB.
    All data drives have at least 9 Gb free space.

    I execute
    snapraid sync
    then stops with the following error:

    1%, 13808 MB, 107 MB/s, CPU 13%, 2:04 ETA
    Saving state to /srv/dev-disk-by-label-SR1D1/snapraid.content...
    Saving state to /srv/dev-disk-by-label-SR2D2/snapraid.content...
    Saving state to /srv/dev-disk-by-label-SR3D3/snapraid.content...
    Saving state to /srv/dev-disk-by-label-SR4D4/snapraid.content...
    Error writing the content file '/srv/dev-disk-by-label-SR3D3/snapraid.content.tmp' in sync(). Input/output error.

    I can not find anything about it on Google.

    Any idea how to fix it?

    @klorinczi, how are you proceeding the plugin? i'd also love to see this in OMV, especially with the new html report feauture. in the meantime i used cronjob to run hdsentinel periodically and generate a report, which I am reaching over a dedicated port via the nginx plugin. not the most elegant way, and also does not give me proactive alerts but serves the purpose.

    molnart: I had no time to work on it.

    I would be interested in your solution.
    Is it a shell script, which executes HD Sentinel?

    Sent with Tapatalk from my Samsung Galaxy Note 3 N9005.

    Using OpenMediaVault v3.0.88 (Erasmus), openmediavault-syncthing 3.10 plugin, Syncthing v0.14.38, Linux (64 bit).

    Added a folder “0_internal” and I see: Error folder path missing

    I checked through SSH, that the directory exists, owner is my user, permission is rw for my user.

    I also changed GUI username & password in advanced settings through GUI. However entering username & password for GUI pops up the authentication window again & again.

    But somehow later I entered into the GUI.

    When restarting the Syncthing I get the following error log:

    Log: 2017-10-01 14:48:55: Creating directory for “0_internal” (shareid): mkdir /srv/driveid/Backup/MOBILE: permission denied

    2017-10-01 14:48:55: Creating folder marker: mkdir /srv/driveid/Backup/MOBILE/2017 - Samsung Galaxy Note3 N9005/0_internal/.stfolder: no such file or directory

    2017-10-01 14:48:55: Stopping folder “0_internal” (shareid) - folder path missing

    2017-10-01 14:49:00: [Inotify] Failed to install inotify handler for 0_internal: lstat /srv/driveid/Backup/MOBILE/: no such file or directory

    Any idea how to fix?

    Sent with Tapatalk from my Samsung Galaxy Note 3 N9005.

    Further possibility:
    If I execute a task from GUI, it should:
    - pass command from GUI to server
    - server starts execution, and writes result buffer continuously to a session log file until it is finished successfully or finished with error.
    - GUI should read session log file, when requested by the user from GUI (by pressing "Command log" button on Storage/File systems page) or display the finished command output in an informational dialog on any current page.

    This is how it should work, IMHO.

    Sent from my GT-I9305 using Tapatalk.

    Great thought but OMV doesn't do magic. Any command run from the command line to query a drive's status will be very slow if it has failed in certain ways. OMV uses these same commands. A commercial NAS vendor can show warnings/failures like this because they always have the same hardware. OMV does not have that luxury. Sleeping drives can also appear to be failed if not given enough time to start.

    I think it is development decision how to react, when timeout happens.
    OMV developer decided to give a fatal error, with a dialog window to be confirmed.

    I think there could be another way to handle such situation.

    Android gives a warning window, when an app is unresponsive, giving some options:
    - wait
    - report
    - close app

    OMV could handle similar way.
    If GUI doesn't get response from the server, should display a dialog window with multiple choices:
    - wait (adds +1 minute timeout before next warning dialog shows)
    - report (do so automatic debug information collection, and report to the developers). The report way should also make possible to preview the debug informations to be sent.
    - close dialog.

    I think this would be a better way to handle such timeout situation.

    Sent with Tapatalk from my SM-N9005

    Probably but I don't know where it is. I think that is avoiding the problem as well. Failing drives mean commands aren't returning in time and that is a timeout not set by OMV.

    I think, that a failing drive should not cause failure of the GUI.

    Furthermore, the GUI should warn & display the drive failure.

    Sent with Tapatalk from my SM-N9005

    Clearly? What is the problem then? The error is a javascript error which means the client is involved as well. This means the browser, networking, and the server are all involved. Why doesn't everyone get the error? Why is the system performing a relatively high resource action in pretty much all of the situations I have seen this involved with? I get that multiple people are seeing this but it is not easy to diagnose especially when it can't be recreated on purpose.

    Yep and it works very well.
    monit stop omv-engined
    omv-engined -df

    At least 2 of 5 HDDs in the server has bad sectors (content moved to reserved space). At least one doesn't pass short SMART test.
    This might be the reason of the error, and the reason why doesn't happen for everybody.

    Can I increase somewhere the javascript gui response timeout?

    I will try the debug mode later.

    Sent with Tapatalk from my SM-N9005