If the variable is not in that file (/etc/default/openmediavault), it means, that the default setting will be used. If you want to change the setting, add the variable and the desired setting to that file.
https://docs.openmediavault.or…l#environmental-variables
Will try that instead. Thank you.
No that is not correct. That files stores environmental variables an their settings.
But no mention of btrfs scrub in that file. I need to disable it since it interferes with my current setup.
Where are:
OMV_BTRFS_SCRUB_ENABLED
OMV_BTRFS_SCRUB_PRIORITY
OMV_BTRFS_SCRUB_READONLYI am looking at openmediavault and openmediavault.dpkg-dist in:
/etc/defaultUpdate:
Was looking in the wrong place. Found this:
/etc/cron.weekly/openmediavault-scrub_btrfsThere is mentioned:
OMV_BTRFS_SCRUB_ENABLED=${OMV_BTRFS_SCRUB_ENABLED:-"yes"}
OMV_BTRFS_SCRUB_PRIORITY=${OMV_BTRFS_SCRUB_PRIORITY:-"-c 2 -n 4"}
OMV_BTRFS_SCRUB_READONLY=${OMV_BTRFS_SCRUB_READONLY:-"no"}Will attempt to modify yes into no.
Hi,
I am also using btrfsmaintenance script for many months without any problems. Now there are two things running on my nas that perform maintenance. How will they interact with each other? Does one take precedence over another? My scrub jobs run once a month which is the recommended amount according to various sources. It also does it when ''idle'' not in ''normal mode'' because that uses high cpu an IO. How is this handled by omv in the latest update? And what parameters are used for weekly scrubs regarding dusage and musage?
I've also read in another thread on this forum that modifying /etc/default/openmediavault will revert every time when omv gets updated. That means that changes made in that file are temporarily and need to be modified over and over again so it doesn't conflict with the btrfsmaintenance script.
My suggestion to the omv team would be to undo previous update regarding the scrub and balancing function and use the btrfsmaintenance script as a base to make it function as part of the gui. For example under system menu or storage menu create a submenu called maintenance where you can configure defrag, balance, scrub and error scan with optional parameters like idle, normal, dusage, musage, when and email notifications. Perhaps also include the option to start a manual job. I believe truenas already incorporated such a method. By adding this to omv it would make it a more complete storage solution. Not having the option to configure it according to ones need or tailor it to what is considered best practice is a missed opportunity imho and maintenance of disks and therefore data should be an integral part of the functionality of an nas os .
Don't interpreted this as an attack. I think omv is a great nas os. 
Best regards.
It worked. Thank you. By the way I believe there was a option in omv5 under extras that had such a functionality... If I'm not mistaken.
Hi,
Kindly requesting some help/insight on the following. Under system update a message appears that kernel updates are available for 5.18 etc. When trying to install it wont install. Have a look at the attached screenshots. How do I install these updates?
Thank you.
hi,
I have been playing around with said docker combinations. Have a look:
I did encounter a unresolved issue which I am still investigating.
Regaring the ram+cpu hog question, on recent hardware that's not something to worry about. You can look at the attached pictures in my post. I'm running on a j4105 quadcore with 16Gb dual channel.
Will have a look.
Thanx
Update:
Dashboard 193 seems to work fine. Will compare json's to find out what's the difference.
Hello,
Can someone help me with the following problem? I have deployed a prometheus+node exporter+cadvisor+grafana stack with portainer to monitor a fresh OMV6 install and running containers using 2 youtube tutorials:
The problem is that the graph that suppose to show memory usage and memory cached for running containers displays 0 B. I have search the forum and the internet but I'm still stuck. In the grafana webgui I have imported dashboards 14282 (below image) and 1860.
I've have added port 9100 to ''node exporter section'' since it was not accessible through the browser at first. Here is my own cooked up docker compose:
version: '3'
volumes:
prometheus-data:
driver: local
grafana-data:
driver: local
services:
prometheus:
image: prom/prometheus:latest
container_name: prometheus
ports:
- "9090:9090"
volumes:
- /etc/prometheus:/etc/prometheus
- prometheus-data:/prometheus
restart: unless-stopped
command:
- "--config.file=/etc/prometheus/prometheus.yml"
grafana:
image: grafana/grafana-oss:latest
container_name: grafana
ports:
- "3000:3000"
volumes:
- grafana-data:/var/lib/grafana
restart: unless-stopped
node_exporter:
image: quay.io/prometheus/node-exporter:latest
container_name: node_exporter
ports:
- "9100:9100"
command:
- '--path.rootfs=/host'
pid: host
restart: unless-stopped
volumes:
- '/:/host:ro,rslave'
cadvisor:
image: gcr.io/cadvisor/cadvisor:latest
container_name: cadvisor
ports:
- "8080:8080"
volumes:
- /:/rootfs:ro
- /var/run:/var/run:ro
- /sys:/sys:ro
- /var/lib/docker/:/var/lib/docker:ro
- /dev/disk/:/dev/disk:ro
devices:
- /dev/kmsg
restart: unless-stoppedHere is my etc/prometheus/prometheus.yml file:
GNU nano 5.4 /etc/prometheus/prometheus.yml
global:
scrape_interval: 15s # By default, scrape targets every 15 seconds.
# Attach these labels to any time series or alerts when communicating with
# external systems (federation, remote storage, Alertmanager).
# external_labels:
# monitor: 'codelab-monitor'
# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
# The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
- job_name: 'prometheus'
# Override the global default and scrape targets from this job every 5 seconds.
scrape_interval: 5s
static_configs:
- targets: ['192.168.1.100:9090']
# Example job for node_exporter
- job_name: 'node_exporter'
static_configs:
- targets: ['192.168.1.100:9100']
# Example job for cadvisor
- job_name: 'cadvisor'
static_configs:
- targets: ['192.168.1.100:8080']All dockers are running, are accessible through the browser. When I browse to node exporter on 192.168.1.100:9100 the following is listed (amongst many others) :
# HELP node_memory_Cached_bytes Memory information field Cached_bytes.
# TYPE node_memory_Cached_bytes gauge
node_memory_Cached_bytes 1.372033024e+10So all the memory data including memory_cached is being gathered right?
When I browse to cAdvisor on 192.168.1.100:8080 and look at the ''docker containers'' section all is listed and when selecting qbittorrent a new page appears with the following metrics:
* On a side note. For those who want to try it out but have already a container running that uses port 8080 like qBittorrent should change the torrent container to something else like 8081 since I was not able to change port 8080 in the above stack successfully. It resulted in cadvisor not being accessible in the browser.
Thanks in advance.
Yesterday and just now mail notification that balance took place. Soproblem persists argh
update
So my nas booted up this morning. No mail this time. All seems ok now I guess.. Thanks for the help.
root@openmediavault:~# journalctl | grep 'cron.weekly'
dec 08 08:48:39 openmediavault anacron[917]: Will run job `cron.weekly' in 10 min.
dec 08 09:43:57 openmediavault anacron[917]: Job `cron.weekly' started
dec 08 09:43:57 openmediavault anacron[12722]: Updated timestamp for job `cron.weekly' to 2021-12-08
dec 08 09:44:05 openmediavault anacron[917]: Job `cron.weekly' terminated (mailing output)
dec 08 09:44:05 openmediavault postfix/smtp[12696]: 4201047: replace: header Subject: Anacron job 'cron.weekly' on openmediavault: Subject: [openmediavault.localdomain] Anacron job 'cron.weekly' on openmediavault
root@openmediavault:~#Mail output from yesterday:
/etc/cron.weekly/btrfs-balance:
Before balance of /srv/dev-disk-by-id-ata-ST4000VN008-2DR166_ZDH9L27R
Data, RAID1: total=2.48TiB, used=2.47TiB
System, RAID1: total=32.00MiB, used=384.00KiB
Metadata, RAID1: total=3.00GiB, used=2.73GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
/dev/sda 4,1T 2,8T 1,3T 68% /srv/dev-disk-by-id-ata-ST4000VN008-2DR166_ZDH9L27R
Done, had to relocate 0 out of 2546 chunks
flock: getting lock took 0.000004 seconds
flock: executing btrfs
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=10
Done, had to relocate 0 out of 2546 chunks
flock: getting lock took 0.000004 seconds
flock: executing btrfs
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=15
Done, had to relocate 0 out of 2546 chunks
flock: getting lock took 0.000003 seconds
flock: executing btrfs
Done, had to relocate 0 out of 2546 chunks
flock: getting lock took 0.000004 seconds
flock: executing btrfs
Dumping filters: flags 0x6, state 0x0, force is off
METADATA (flags 0x2): balancing, usage=10
SYSTEM (flags 0x2): balancing, usage=10
Done, had to relocate 1 out of 2546 chunks
flock: getting lock took 0.000003 seconds
flock: executing btrfs
After balance of /srv/dev-disk-by-id-ata-ST4000VN008-2DR166_ZDH9L27R
Data, RAID1: total=2.48TiB, used=2.47TiB
System, RAID1: total=32.00MiB, used=384.00KiB
Metadata, RAID1: total=3.00GiB, used=2.73GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
/dev/sda 4,1T 2,8T 1,3T 68% /srv/dev-disk-by-id-ata-ST4000VN008-2DR166_ZDH9L27R
Before balance of /srv/dev-disk-by-id-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N1LL838J-part1
Data, single: total=2.14TiB, used=2.13TiB
System, DUP: total=32.00MiB, used=272.00KiB
Metadata, DUP: total=3.00GiB, used=2.37GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
/dev/sdc1 3,1T 2,4T 647G 79% /srv/dev-disk-by-id-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N1LL838J-part1
Done, had to relocate 0 out of 2196 chunks
flock: getting lock took 0.000005 seconds
flock: executing btrfs
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=10
Done, had to relocate 0 out of 2196 chunks
flock: getting lock took 0.000003 seconds
flock: executing btrfs
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=15
Done, had to relocate 0 out of 2196 chunks
flock: getting lock took 0.000004 seconds
flock: executing btrfs
Done, had to relocate 0 out of 2196 chunks
flock: getting lock took 0.000003 seconds
flock: executing btrfs
Dumping filters: flags 0x6, state 0x0, force is off
METADATA (flags 0x2): balancing, usage=10
SYSTEM (flags 0x2): balancing, usage=10
Done, had to relocate 1 out of 2196 chunks
flock: getting lock took 0.000003 seconds
flock: executing btrfs
After balance of /srv/dev-disk-by-id-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N1LL838J-part1
Data, single: total=2.14TiB, used=2.13TiB
System, DUP: total=32.00MiB, used=272.00KiB
Metadata, DUP: total=3.00GiB, used=2.37GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
/dev/sdc1 3,1T 2,4T 647G 79% /srv/dev-disk-by-id-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N1LL838J-part1In a few hours the problem will repeat itself. My nas however didn't powered off last night because of uploading files so... We will see in a moment what will happen.
Update.
No mail received today. Will ensure that nas shuts down tonight and see what happens tomorrow.
root@openmediavault:~# ls -la /var/spool/anacron
totaal 12
drwxr-xr-x 2 root root 100 sep 15 19:14 .
drwxr-xr-x 7 root root 160 sep 15 19:14 ..
-rw------- 1 root root 9 dec 8 09:43 cron.daily
-rw------- 1 root root 9 nov 10 18:31 cron.monthly
-rw------- 1 root root 9 dec 8 09:44 cron.weeklyScrub (monthly) hasn't run yet as explained earlier.
Received the notification mail on 9:44. Yesterday at 9:31. My server does shuts down at midnight and starts at 9:00 with autoshutdown plugin. Maybe it thinks it missed a run and tries it again?
okay so now i am getting daily(?) notifications per email:
[openmediavault.localdomain] Anacron job 'cron.weekly' on openmediavaultSo a balance is run every day which is strange since it is configured to run weekly.
I miss my msx haha.
No errors, that's the strange part. Paid close attention. Maybe switching kernels? Anyway will keep my eye out coming weeks.
As I suspected:
root@openmediavault:~# ls /etc/cron*
/etc/crontab
/etc/cron-apt:
action.d config config.d errormsg.d logmsg.d mailmsg.d mailonmsgs syslogmsg.d syslogonmsgs
/etc/cron.d:
anacron mdadm openmediavault-powermngmt openmediavault-userdefined sysstat
e2scrub_all openmediavault-mkrrdgraph openmediavault-rsync php
/etc/cron.daily:
0anacron dpkg openmediavault-cron-apt openmediavault-pending_config_changes quota
apt-compat logrotate openmediavault-flush-mailq openmediavault-samba-recycle samba
bsdmainutils openmediavault-check_locked_users openmediavault-mdadm passwd sysstat
/etc/cron.hourly:
/etc/cron.monthly:
0anacron
/etc/cron.weekly:
0anacron openmediavault-update-smart-drivedbThere is no entry under cron.monthly and cron.weekly. Didn't I follow all the required steps above?? Shouldn't the following command prevent the above problem:
./btrfsmaintenance-refresh-cron.shGreetings.
Update. I ran above refresh command again and now:
root@openmediavault:~# ls /etc/cron*
/etc/crontab
/etc/cron-apt:
action.d config config.d errormsg.d logmsg.d mailmsg.d mailonmsgs syslogmsg.d syslogonmsgs
/etc/cron.d:
anacron mdadm openmediavault-powermngmt openmediavault-userdefined sysstat
e2scrub_all openmediavault-mkrrdgraph openmediavault-rsync php
/etc/cron.daily:
0anacron dpkg openmediavault-cron-apt openmediavault-pending_config_changes quota
apt-compat logrotate openmediavault-flush-mailq openmediavault-samba-recycle samba
bsdmainutils openmediavault-check_locked_users openmediavault-mdadm passwd sysstat
/etc/cron.hourly:
/etc/cron.monthly:
0anacron btrfs-scrub
/etc/cron.weekly:
0anacron btrfs-balance openmediavault-update-smart-drivedbStrange that it didn't take effect before. I remember clearly that I ran that refresh command multiple time to be shure...
I am checking up on scrub jobs and found this:
root@openmediavault:~# btrfs scrub status /dev/sdb
scrub status for 3f95b8a7-a00d-4467-aa8d-21e7ea955134
no stats available
total bytes scrubbed: 0.00B with 0 errorsThis means that not a single scrub have taken place since installing btrfsmaintenance script right? Do you have a similar output? What am I doing wrong?
Thank you.
Hi,
Again I've run into some problems and request kindly your assistance resolving this. The goal is to put the server to either S3 (suspend to RAM) or S4 (hibernate). Around midnight autoshutdown will put the server to S3. The following morning when the WakeAlarm is triggered the server spits out a load of error messages and the system is unusable:
ext4-fs error ext4 find entry:1536: inode #.....comm nginx, comm cron, comm smartd, com master, comm monit: reading directory lblock blablablablaWhen I try to put the server to standby via the webgui and wakeup using magic packet this message appears:
acpi hardware changed while hibernated, succes doubtfull!The above is with Restore on ac power loss disabled and S3 on auto in the bios.
The setup:
- Asrock J5040-ITX
- Samsung Fit usb flasdrive 64GB. Resized the ext4 part to aprox half and left that unpartitioned for overprovisioning. Had to move the swap partition to the left a bit so that the unpartitioned space is on the right
- S3 is set to auto in the bios
- Restore on ac power loss is set to enabled
- Deep sleep S5 is set to disabled in the bios
- Swap is enabled, however swappiness is set to 10 default 60
- 16GB ddr4 installed
- Autoshutdown en flash plugins are installed. No error messages during install.
- System is up to date.
I have to cold reboot the server in order to get it to work again. I have tried the following:
- In the plugin select S3 and S4
- Set Restore on ac power loss enabled and disabled
- Scan the flashdrive for errors (inode), which are found after a bad wakeup
- Removed the entries in fstab, noatime and nodiretime / Removed the flashplugin/reboot and the following morning the same error happened
- Restore on ac power loss enabled/disabled
I have searched the forum and could not find any solution. Any help is appreciated.
Kind regards
-Update-
Did a clean install. This time I choose a different source mirror. Don't know if that was the problem. Most likely an error during system update in the past. So far running as it should.
New problem:
The following security packages have been installed automatically.
CRON-APT RUN [/etc/cron-apt/config]: Mon Sep 13 07:38:52 CEST 2021
CRON-APT SLEEP: 2033, Mon Sep 13 08:12:45 CEST 2021
CRON-APT ACTION: 5-openmediavault-security
CRON-APT LINE: /usr/bin/apt-get --option quiet=1 --option APT::Get::List-Cleanup=false --option Dir::Etc::SourceList=/etc/apt/sources.list --option Dir::Etc::SourceParts="/dev/null" --option DPkg::Options::=--force-confold dist-upgrade --yes --option APT::Get::Show-Upgraded=true
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up openmediavault-clamav (5.0.13-1) ...
Updating service units ...
Updating configuration database ...
ln: failed to create symbolic link '/usr/bin/clamonacc': File exists
dpkg: error processing package openmediavault-clamav (--configure):
installed openmediavault-clamav package post-installation script subprocess returned error exit status 1
Processing triggers for openmediavault (5.6.14-1) ...
Updating locale files ...
Updating file permissions ...
Purging internal cache ...
Restarting engine daemon ...
Errors were encountered while processing:
openmediavault-clamav
E: Sub-process /usr/bin/dpkg returned an error code (1)When I check in gui dashboard both dots are not green. I have to re-enable it manually. For some reason autoshutdown plugin stops working to. Need to re-enable it the same way. 
update.
On my ovm6 vm it is working now. Next I tried it on my real nas running ovm5 from flash drive with flas plugin and that is working now too. Green lights accross the board.
Very strange... I have no explanation why it suddenly has no errors when enabling... I haven't changed anything or doing something new.