Monitoring alert -- Filesystem flags changed

greg77 · Mar 30th 2024

Hi,

I received a notification email from OMV yesterday:

Subject:

[omv] Monitoring alert -- Filesystem flags changed filesystem_srv_dev-disk-by-uuid-9b905237-9d8a-4a60-b86a-8eab1bce9483

Body:

The system monitoring needs your attention.

Host: omv

Date: Fri, 29 Mar 2024 09:07:42

Service: filesystem_srv_dev-disk-by-uuid-9b905237-9d8a-4a60-b86a-8eab1bce9483

Event: Filesystem flags changed

Description: filesystem flags changed from 'rw,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group' to 'ro,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group'

This triggered the monitoring system to: alert

After the alert email the filesystem became Read-Only.

This is a LUKS partition. No other issues were detected. No recent reboots or a power issues. No recent SMART alerts.

A reboot helped to solve the problem, but can someone explain why it happened and how to avoid this kind of issues in a future?

I use OMV since version 5.x (use LUKS since ver 6.x - around 1.5-2 years) and it has never happened to me before.

Many thanks

macom · Mar 30th 2024

The description states that the filesystem flag has changed from rw (read-write) to ro (read-only). Probably the kernel has detected an issue and mounted the filesystem as ro.

You can check the logs for any error just before the date mentioned in the mail.

greg77 · Mar 30th 2024

Thank you. Yes, noticed the description. Which log would it be? Syslog or kernel log available from the admin panel doesn't have anything around that date. I SSHed and checked older logs (kern.log.1, faillog, dmesg from previous sessions) and also couldn't find anything from that date. All I can find is either today's reboot or a previous boot weeks ago.

macom · Mar 30th 2024

you can try journal

greg77 · Mar 30th 2024

I did try journal. That was the "dmesg from previous sessions" mentioned in my previous email.

Command journalctl -o short -k -b -1 gives me this result (showing only a few lines):

Code

Mar 15 08:51:19 omv kernel: vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4])
Mar 15 08:51:19 omv kernel: vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4])
Mar 15 08:51:19 omv kernel: vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops [vc4])
Mar 15 08:51:19 omv kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1
Mar 15 08:51:19 omv kernel: vc4-drm gpu: [drm] Cannot find any crtc or sizes
Mar 15 08:51:19 omv kernel: vc4-drm gpu: [drm] Cannot find any crtc or sizes
Mar 15 08:51:19 omv kernel: vc4-drm gpu: [drm] Cannot find any crtc or sizes
Mar 15 08:51:20 omv kernel: Bluetooth: hci0: BCM: features 0x2f
Mar 15 08:51:20 omv kernel: Bluetooth: hci0: BCM43455 37.4MHz Raspberry Pi 3+-0190
Mar 15 08:51:20 omv kernel: Bluetooth: hci0: BCM4345C0 (003.001.025) build 0382
Mar 30 12:58:15 omv systemd-journald[283]: /var/log/journal/104fcb2b14ab4bf4a6df289113fe6cbb/system.journal: Journal file has been deleted, rotating.
Mar 30 12:58:15 omv systemd-journald[283]: Failed to write entry to /var/log/journal/104fcb2b14ab4bf4a6df289113fe6cbb/system.journal (27 items, 663 bytes), rotating before retrying: Identifier removed
Mar 30 12:58:15 omv kernel: watchdog: watchdog0: watchdog did not stop!
Mar 30 12:58:15 omv systemd-shutdown[1]: Using hardware watchdog 'Broadcom BCM2835 Watchdog timer', version 0, device /dev/watchdog0
Mar 30 12:58:15 omv systemd-shutdown[1]: Watchdog running with a timeout of 10min.
Mar 30 12:58:15 omv systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 30 12:58:15 omv systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Mar 30 12:58:15 omv systemd-journald[283]: Received SIGTERM from PID 1 (systemd-shutdow).

Display More

The alert was from the 29th of March, but nothing in the log above as you can see.

macom · Mar 30th 2024

Quote from greg77

Mar 30 12:58:15 omv systemd-journald[283]: /var/log/journal/104fcb2b14ab4bf4a6df289113fe6cbb/system.journal: Journal file has been deleted, rotating.

No idea why the file has been deleted. Maybe it is related to the issue. Might be best, just to see if it happens again. Hopefully not.

Monitoring alert -- Filesystem flags changed

Participate now!

Similar Threads

What does this mean. (The system monitoring needs your attention.)