Posts by auanasgheps

  • openmediavault-snapraid-aio

    Uhm, a first issue arises during the command line installation for dependencies.

    It warns are missing, but are not installed.


    To install, I had to run apt --fix-broken install

    Don't know why.

    Feedbacks:

    Notification Settings

    This section of the script actually uses postfix configuration from OMV, so the user doesn't have to configure anything manually.

    Since the user has already configured Notification options, I would inherit those values. (simplicity)


    Check for script Updates

    Please disable the option and remove it: the user will not be in control of updates since we'll manage them via package updates


    Healthchecks

    Healtchecks UUID and Healtchecks URLs should be grayed out if "Use Healthchecks.io" is disabled, which is by default. If enabled, they are mandatory fields.


    Apprise

    The same applies with Apprise: the URL field should be grayed out if the main option is disabled, mandatory if enabled.


    I think some options clashed between Apprise and Apprise Notifications.


    Can you make two distinct sections?


    Apprise Notifications

    Use Apprise Notifications

    Apprise Attach report

    Apprise URL



    Apprise Email notification

    Use Apprise Notifications

    Apprise Attach report

    Apprise URL


    NOTE: this is an advanced setting, not super relevant to OMV the average user. The main benefit for OMV users is the attachment feature not available in postfix.


    Telegram and Discord

    These are legacy integrations before I developed the Apprise integration. Please hide them. The Discord integration is very unreliable. Apprise is much superior, I don't want new users to go for these old features.





    Log SMART Info


    SMART_LOG_NOTIFY requires SMART_LOG to be enabled first.


    Run 'snapraid status'

    SNAP_STATUS_NOTIFY requires SNAP_STATUS to be enabled first.


    SnapRAID configuration file

    This should be instead a dropdown menu with a list of the available configuration files.


    Please note that the script can be used for multiple configuration files, creating a separate AIO config for each SnapRAID script.

    Honestly I don't know how many users do multiple SnapRAID configurations, but since it's a feature, we should probably follow the same approach and make the AIO configurations for each SnapRAID configuration.


    Docker and service management

    Since we removed remote Docker management, now "Manage local Docker Containers" is redundant since the user would have already selected "Manage Docker containers / services".


    Can you hide the entry but still enable it if the user enabled "Manage local Docker Containers"?


    Lables and titles

    I will take care of this.

  • openmediavault-snapraid-aio

    I wanted to test it right now but my testing VM has OMV7 and the plugin requires OMV8. Is there a dirty way to upgrade to OMV8/Debian 13?
    I would not do this in real world, it just to get it up and running quickly.

  • openmediavault-snapraid-aio

    Yes, I think it would make sense to only pull running containers. Those are the ones that need to be stopped/paused.


    I also think we can discard the "Remote Docker Management" section, since it's for very advanced uses where SnapRAID and Docker are not running on the same host.

  • openmediavault-snapraid-aio

    Quote from ryecoaaron

    I was really hoping to hand this off. I can help but I don't use snapraid or the script. So, it is really hard for me to test. I also don't really know how the script should be used. Creating this initial plugin was about all of my available time for a while which was much less work than getting the current plugin to stop using the old script and start using the new one.

    I really appreciate it.
    I've delayed my help for an official integration because I wanted to make changes to the script, but I hadn't had time until recently.


    The logic is always the same: automate all SnapRAID routine actions. Some of these things are very specific to the SnapRAID world. However, the description I've added to each field in the configuration file should be enough to explain every option, at least for a SnapRAID user.


    In addition to the core SnapRAID actions, the script does some nice things.


    An example is the Docker management. When SnapRAID is running, no application should write any data to the array.

    To resolve this problem, my script stops or pauses containers during the execution.


    Currently, a user has to enter the containers manually. Could we pull containers names so they can be selected with a dropdown list?

  • openmediavault-snapraid-aio

    Hi ryecoaaron, thanks for the initial effort on this!

    Please note that I've been working a lot on the dev branch.

    Most of the changes are done, I just need to merge a PR.


    I had a quick look and it seems that you used the master as a reference.


    Therefore, regarding the configuration reference and descriptions which needs to be exposed in the UI, please refer to this: https://github.com/auanasgheps…ob/dev/script-config.conf


    What's the "logic" of the plugin? I would expect it to expose most/all configuration options and push them to the config files. If it's only this, the testing shouldn't be too much hard.


    A nice to have would be to install automatically the dependencies. The script handles this automatically, but I think would be best to integrate them in the install phase.

    Required:

    - curl

    - jq

    - bc

    - python3-markdown


    Optional: Pipx + Apprise for enhanced notifications.




     

  • [HowTo] SnapRAID in OMV

    Quote from TOMillr

    Sounds interesting. Care to share some details of what me might expect to see in the update? 8|

    It will include a new notification system which is much more reliable and flexible compared to the previous one. And also a couple of minor changes, plus lots of bugfixes and logic/safeguards improvements.


    Most of what I'm saying is already on Github, and the installation is super easy.

    That's why I haven't focused on the integration with the plugin, but it will happen.

  • BorgBackup Plugin - best way do browse mounted archives?

    Yes, this is a common problem when mounting Borg backups with FUSE, which by default limits the access to the mount user.


    When executing the command, if done via the CLI, you can add the allow_other option.


    Otherwise you can adjust FUSE configuration (/etc/fuse.conf) and add the option there.


    And yes, it will be available via SMB!

  • Postfix Problems

    Postfix wasn't fully working yet with the test version.
    You have to add a specific service to the systemd file.

    I fixed the issue by adding a new line

    Code
    Before=postfix@-.service


    More info here.


    I have solved both Postfix and nginx doesn't exist/exist emails, while sending a test email to verify Postfix is alive.

  • Postfix Problems

    Thanks again to wenzhuo for the help. You are a master!


    I have tested it and this this fixes two issues:

    • Postfix getting stuck (worked around with a scheduled service reboot after system boot)
    • Email about nginx does not exist/exists (which I could not workaround)


    Edit the folder2ram_startup.service systemd: systemctl edit folder2ram_startup.service --full


    Add the following to the [Unit] section

    Code
    RequiresMountsFor=/var
Wants=tmp.mount
Before=monit.service rrdcached.service minidlna.service nginx.service nmbd.service

    It should look like this


    Code
    [Unit]
Description=folder2ram systemd service
After=local-fs.target
After=blk-availability.service
DefaultDependencies=no
RequiresMountsFor=/var
Wants=tmp.mount
Before=monit.service rrdcached.service minidlna.service nginx.service nmbd.service

    Save and reboot.

    ENJOY!

  • How to disable BTRFS Scrub report?

    Hi,

    Yesterday I received a scrub report notification for each of my disks:


    Code
    Scrub report of the file system mounted at /srv/dev-disk-by-uuid-7e5bf71c-c945-4bea-8f96-6ebe8545198d [UUID=7e5bf71c-c945-4bea-8f96-6ebe8545198d]

Scrub device /dev/sda (id 1) done
Scrub started:    Sat Jun 14 11:46:18 2025
Status:           finished
Duration:         5:44:44
Total to scrub:   4.73TiB
Rate:             239.40MiB/s
Error summary:    no errors found

    I've previously set the variable OMV_BTRFS_SCRUB_ENABLE to NO, but it still ran.


    Code
    omv-env get | grep OMV_BTRFS
OMV_BTRFS_SCRUB_ENABLE=NO


    What should I do to disable it?


    I am using SnapRAID which has built-in scrub feature, that's why I don't want another one.


    Thanks!

  • Notification emails not sending, until reboot

    Quote from keeks12

    did anyone find a fix for this? I run two OMV7 servers on similar but slightly different hardware. One of my servers send email notifications fine, the other one hangs and does not send notifications until I run `sudo systemctl restart postfix` and then I get a flood of emails.


    The only thing that is really different (and how I started noticing it) was I run this snapraid script https://github.com/auanasgheps/snapraid-aio-script by auanasgheps but I am not sure if that is the cause of the issue.


    any help is appreciated, happy to provide further information.

    My script only uses the current OMV Postfix configuration, so it doesn't make any changes regarding email.


    I am seeing the same issue with postfix (emails not being sent) , because I'm running the flashmemory plugin. If you are too, unfortunately this is to be expected with OMV7 (don't know why, OMV6 worked flawylessly with this plugin).

    More info can be found here.

    The workaround for me is to set a cron job on restart to 60 seconds:


    Code
    sleep 60 && systemctl restart postfix



    To be honest I'm evaluating the replacement of my USB thumb drive with a USB SSD so I can discard the plugin.