If your NAS has Wi-Fi too, just disable it and let Windows automatic route metric feature handle the rest. Also make sure you don't have a faulty cable that degrades Ethernet link speed. You can use the route print command to look up route metrics.
Posts by wenzhuo
-
-
Why? Then journalctl --rotate would never run.
Because persistent journal and syslog live in /var/log only. Also, it doesn't seem to make sense to do rotation in start.
-
It should only run logrotate once and journalctl rotate once
On line 811 and 832, log rotation should be done for /var/log only
-
With the above fixed shutdown unit, sync on shutdown works for me now. But I bumped into another problem of folder2ram. It rotates logs too many times on one invocation.
Code
Display Morewenzhuo@omv:/var/log$ ls -lrt php8.2-fpm.log* -rw------- 1 root root 76 Aug 12 14:43 php8.2-fpm.log.12.gz -rw------- 1 root root 76 Aug 12 14:43 php8.2-fpm.log.11.gz -rw------- 1 root root 76 Aug 12 14:43 php8.2-fpm.log.10.gz -rw------- 1 root root 117 Aug 12 14:49 php8.2-fpm.log.9.gz -rw------- 1 root root 141 Aug 12 14:50 php8.2-fpm.log.8.gz -rw------- 1 root root 76 Aug 12 14:50 php8.2-fpm.log.7.gz -rw------- 1 root root 76 Aug 12 14:50 php8.2-fpm.log.6.gz -rw------- 1 root root 76 Aug 12 14:50 php8.2-fpm.log.5.gz -rw------- 1 root root 116 Aug 12 14:57 php8.2-fpm.log.4.gz -rw------- 1 root root 141 Aug 12 14:59 php8.2-fpm.log.3.gz -rw------- 1 root root 76 Aug 12 14:59 php8.2-fpm.log.2.gz -rw------- 1 root root 56 Aug 12 14:59 php8.2-fpm.log.1 -rw------- 1 root root 56 Aug 12 14:59 php8.2-fpm.log wenzhuo@omv:/var/log$ ls -lrt syslog* -rw-r----- 1 root adm 1190 Aug 12 14:59 syslog.4.gz -rw-r----- 1 root adm 2448 Aug 12 14:59 syslog.3.gz -rw-r----- 1 root adm 327 Aug 12 14:59 syslog.2.gz -rw-r----- 1 root adm 373 Aug 12 14:59 syslog.1 -rw-r----- 1 root adm 41321 Aug 12 19:55 syslog -
I know you are trying to fix things but even the changes already made have broken other systems. Testing on just your system is not enough.
That's exactly why I post it here.
-
Expected result:
Code
Display Morewenzhuo@omv:~$ journalctl -b -1 -u folder2ram_shutdown.service Aug 12 12:37:54 omv systemd[1]: Starting folder2ram_shutdown.service - folder2ram sync before unmount... Aug 12 12:37:54 omv systemd[1]: Finished folder2ram_shutdown.service - folder2ram sync before unmount. Aug 12 12:44:44 omv systemd[1]: Stopping folder2ram_shutdown.service - folder2ram sync before unmount... Aug 12 12:44:45 omv folder2ram[3794]: will now stop all mountpoints Aug 12 12:44:45 omv folder2ram[3794]: stop /var/log Aug 12 12:44:48 omv folder2ram[3794]: stop /var/lib/openmediavault/rrd Aug 12 12:44:48 omv folder2ram[3794]: stop /var/spool Aug 12 12:44:49 omv folder2ram[3794]: stop /var/lib/rrdcached Aug 12 12:44:51 omv folder2ram[3794]: stop /var/lib/monit Aug 12 12:44:51 omv folder2ram[3794]: stop /var/cache/samba Aug 12 12:44:52 omv systemd[1]: folder2ram_shutdown.service: Deactivated successfully. Aug 12 12:44:52 omv systemd[1]: Stopped folder2ram_shutdown.service - folder2ram sync before unmount. Aug 12 12:44:52 omv systemd[1]: folder2ram_shutdown.service: Consumed 4.490s CPU time. wenzhuo@omv:~$ journalctl --list-boots IDX BOOT ID FIRST ENTRY LAST ENTRY -1 d3b3cb6679f542bbbcd98b6566ab0475 Tue 2025-08-12 12:37:53 CST Tue 2025-08-12 12:44:55 CST 0 87a32e7b0969470189c3955471b2c0b7 Tue 2025-08-12 12:45:44 CST Tue 2025-08-12 13:06:01 CST wenzhuo@omv:~$ journalctl -b -u folder2ram_shutdown.service Aug 12 12:45:47 omv systemd[1]: Starting folder2ram_shutdown.service - folder2ram sync before unmount... Aug 12 12:45:48 omv systemd[1]: Finished folder2ram_shutdown.service - folder2ram sync before unmount. -
Make sure to re-enable the service if you've tried the unit file in comment#14: sudo systemctl reenable folder2ram_shutdown.service
-
Code
Display More# /etc/systemd/system/folder2ram_shutdown.service [Unit] Description=folder2ram sync before unmount DefaultDependencies=no Before=umount.target Conflicts=umount.target After=local-fs.target [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/true ExecStop=/sbin/folder2ram -umountall [Install] WantedBy=multi-user.targetAfter rebooting, verify it's working using command journalctl -b -1 -u folder2ram_shutdown.service, also check:
- journalctl -xe for journals of previous boots
- OMV webif | Diagnostics | Performance Statistics
-
There are a number of issues with folder2ram_shutdown.service I'm trying to fix. Please test this:
Code
Display More# /etc/systemd/system/folder2ram_shutdown.service [Unit] Description=folder2ram systemd service Before=umount.target blk-availability.service Wants=umount.target [Service] Type=oneshot RemainAfterExit=yes ExecStart=/sbin/folder2ram -umountall [Install] WantedBy=umount.targetCodesudo systemctl edit folder2ram_shutdown.service --full sudo systemctl daemon-reload sudo systemctl reenable folder2ram_shutdown.service sudo folder2ram -syncall sudo rebootAfter rebooting, verify the following
Codejournalctl -u folder2ram_shutdown.service journalctl -xe -
After=local-fs.target can be added too.
-
Tested
Code
Display Morewenzhuo@omv:~$ cat /etc/systemd/system/folder2ram_shutdown.service [Unit] Description=folder2ram systemd service Before=umount.target Wants=umount.target [Service] Type=oneshot RemainAfterExit=yes ExecStop=/sbin/folder2ram -umountall [Install] WantedBy=multi-user.targetwenzhuo@omv:~$ wenzhuo@omv:~$ diff -w /lib/systemd/system/folder2ram_shutdown.service /etc/systemd/system/folder2ram_shutdown.service 3,4c3,4 < After=blk-availability.service < BindsTo=blk-availability.service --- > Before=umount.target > Wants=umount.target -
Above change already tested before posting. Wants=umount.target should be added too.
-
sudo systemctl edit folder2ram_shutdown.service --full:
Code
Display More# /etc/systemd/system/folder2ram_shutdown.service [Unit] Description=folder2ram systemd service Before=umount.target [Service] Type=oneshot RemainAfterExit=yes ExecStop=/sbin/folder2ram -umountall [Install] WantedBy=multi-user.target -
The $systemd_shutdown_service_file unit should happen before umount.target. ryecoaaron
-
But clamav still doesn’t start at boot with the flashmemory plugin
Codecd /etc/systemd/system/ sudo mkdir folder2ram_startup.service.d echo -e '[Unit]\nBefore=clamav-daemon.service clamav-freshclam.service' | sudo tee folder2ram_startup.service.d/clamav.confReboot, and you should be good to go
-
That also rules out any power topics, since that SSD got its power only via the USB connector.
Unfortunately, you still cannot rule out the possibility. The USB power draw problem is more prevalent and complex than you think.
Have you tried booting up the 16/64GB OMV flash drives on a computer? Also, why not get a powered USB 3.0 hub to rule out the possibility?
-
I am pretty sure that the core OS is also largely living in RAM but is not serviced by the flashmemory plugin.
The core OS largely lives in the storage. So does /var/lib/docker by default setting. It is a bad idea to put /var/lib/docker in RAM. To reduce wear on the eMMC module, you'd better put it in external storage.
-
Docker container should run as an unprivileged user whenever possible.
-
ZFS ARC memory usage in one of my Intel NUC (8GB)
-
htop has ZFS meters available in its F2 setup screen. You can enable them to find out detailed ZFS ARC memory usage
