Startup notification: Monitoring restart -- Does not exist rootfs

[Jip-Hop]

Upon startup I receive the following email notification:

The system monitoring needs your attention.

Host:        nas
Date:        Sat, 02 Apr 2022 17:56:03
Service:     rootfs
Event:       Does not exist
Description: unable to read filesystem '/' state

This triggered the monitoring system to: restart

—
You have received this notification because you have enabled the system monitoring on this host.
To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.

However the system seems to function normally. What is causing this warning? What are the consequences?

[Jip-Hop]

Related to https://github.com/openmediavault/openmediavault/issues/73 or perhaps a stale entry in /etc/monit/monitrc?

[randellhodges]

I don't know if this is related, but I saw these entries over and over in my boot log. Always a group of 4

2022-05-22T08:25:13-0500 storage-next monit[1745]: filesystem statistic error: cannot read /proc/spl/kstat/zfs/rpool/io -- No such file or directory
2022-05-22T08:25:13-0500 storage-next monit[1745]: Filesystem '/' not mounted
2022-05-22T08:25:13-0500 storage-next monit[1745]: 'rootfs' unable to read filesystem '/' state
2022-05-22T08:25:13-0500 storage-next monit[1745]: 'rootfs' trying to restart

Not sure if the first 2 lines about filesystem statistic error are related to the rootfs line. Like I said, always these same 4 entires.

While searching the kstat/zfs/rpool line, I found: https://bitbucket.org/tildeslash/monit/issues/1021/filesystem-statistic-error-with-zfs-211 https://bitbucket.org/tildeslash/monit/commits/52a5fa6e0f53

Which looks like a fix was merged in monit 5.31.0, but the version of monit on the latest omv (6.0.27-1 (Shaitan)) is 5.27.2

[l-Legacy-l]

M