Received this notification: Filesystem flags changed. should i be worried?

Good day all,

Just received below notification from my server through mail. Can anyone tell me what it means? Should i be worried?

The system monitoring needs your attention.

Host: omvserver
Date: Fri, 23 Sep 2022 17:52:59
Service: filesystem_srv_dev-disk-by-label-Katerina
Event: Filesystem flags changed
Description: filesystem flags changed to ro,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group

This triggered the monitoring system to: alert

—
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.

Zitat von macom

probably it change from read/write to read only (unless you mounted it read only for some reason)

you should check the filesystem, which needs to done from the CLI

Thank you for your quick reply.

I have not done anything, i am at work now.

Can you specify the command in CLI to check this?

I have read that, if the drive is an SSD, this would mean that the drive needs replacement. In my case it is an HDD, does this mean that i will have to start looking for a replacement drive? for this drive, i have not received any alerts from hdd monitoring tool (scrutiny)

Zitat von macom

You can try a reboot first.

It might fix the issue or it might start the checking.

You can also check the SMART values.

my docker containers stopped working, although i can ping the web address. is this behavior to be expected with the above alerT?

Zitat von macom

If the containers have their configuration and/or data on that filesystem, yes. They cannot write data to that filesystem, only read data.

I see. the containers have their configuration files on this drive. When i go hoe i will do a reboot and i will inform. Thank you for your time.

Zitat von macom

If the containers have their configuration and/or data on that filesystem, yes. They cannot write data to that filesystem, only read data.

alright, after rebooting two times the system is back to normal. carried out long test and I have the following errors:

Error 67 [18] occurred at disk power-on lifetime: 13197 hours (549 days + 21 hours)

Error 66 [17] occurred at disk power-on lifetime: 12598 hours (524 days + 22 hours)

Error 65 [16] occurred at disk power-on lifetime: 12598 hours (524 days + 22 hours)

Error 64 [15] occurred at disk power-on lifetime: 12598 hours (524 days + 22 hours)

Error 63 [14] occurred at disk power-on lifetime: 12597 hours (524 days + 21 hours)

Error 62 [13] occurred at disk power-on lifetime: 12431 hours (517 days + 23 hours)

Error 61 [12] occurred at disk power-on lifetime: 12431 hours (517 days + 23 hours)

Error 60 [11] occurred at disk power-on lifetime: 12431 hours (517 days + 23 hours)

for the time being, scrutiny as well as built in OpenMediaVault SMART shows very low fail probability ,around 5%. This drive has been working for almost five (5) years, maybe I should be looking for its replacement ?? the drive is WDC WD40EFAX-68JH4N0

Zitat von macom

post the output of

smartctl -a /dev/sdx

change the x accordingly

=== START OF INFORMATION SECTION ===

Model Family: Western Digital Red (SMR)

Device Model: WDC WD40EFAX-68JH4N0

Serial Number: WD-WX22D2021D59

LU WWN Device Id: 5 0014ee 21261f4a1

Firmware Version: 82.00A82

User Capacity: 4,000,787,030,016 bytes [4.00 TB]

Sector Sizes: 512 bytes logical, 4096 bytes physical

Rotation Rate: 5400 rpm

Form Factor: 3.5 inches

Device is: In smartctl database [for details use: -P show]

ATA Version is: ACS-3 T13/2161-D revision 5

SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)

Local Time is: Sun Sep 25 17:34:06 2022 EEST

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

General SMART Values:

Offline data collection status: (0x82) Offline data collection activity

was completed without error.

Auto Offline Data Collection: Enabled.

Self-test execution status: ( 33) The self-test routine was interrupted

by the host with a hard or soft reset.

Total time to complete Offline

data collection: (59760) seconds.

Offline data collection

capabilities: (0x7b) SMART execute Offline immediate.

Auto Offline data collection on/off support.

Suspend Offline collection upon new

command.

Offline surface scan supported.

Self-test supported.

Conveyance Self-test supported.

Selective Self-test supported.

SMART capabilities: (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability: (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: ( 2) minutes.

Extended self-test routine

recommended polling time: ( 190) minutes.

Conveyance self-test routine

recommended polling time: ( 2) minutes.

SCT capabilities: (0x3039) SCT Status supported.

SCT Error Recovery Control supported.

SCT Feature Control supported.

SCT Data Table supported.

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 1

3 Spin_Up_Time 0x0027 207 203 021 Pre-fail Always - 2650

4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 93

5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0

7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0

9 Power_On_Hours 0x0032 079 079 000 Old_age Always - 15390

10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0

11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0

12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 93

192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 42

193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 2315

194 Temperature_Celsius 0x0022 093 086 000 Old_age Always - 54

196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0

197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0

198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0

199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0

200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0

SMART Error Log Version: 1

No Errors Logged

SMART Self-test log structure revision number 1

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

# 1 Extended offline Interrupted (host reset) 10% 15365 -

# 2 Short offline Completed without error 00% 8711 -

# 3 Short offline Completed without error 00% 8543 -

# 4 Short offline Completed without error 00% 8376 -

# 5 Short offline Completed without error 00% 8208 -

# 6 Short offline Completed without error 00% 8207 -

# 7 Short offline Completed without error 00% 8039 -

# 8 Short offline Completed without error 00% 7885 -

# 9 Short offline Completed without error 00% 7717 -

#10 Short offline Completed without error 00% 7549 -

#11 Short offline Completed without error 00% 7381 -

#12 Short offline Completed without error 00% 7213 -

#13 Short offline Completed without error 00% 7045 -

#14 Short offline Completed without error 00% 6879 -

#15 Short offline Completed without error 00% 6711 -

#16 Short offline Completed without error 00% 6571 -

#17 Short offline Completed without error 00% 6551 -

#18 Short offline Completed without error 00% 6383 -

#19 Short offline Completed without error 00% 6216 -

#20 Short offline Completed without error 00% 6081 -

#21 Short offline Completed without error 00% 5914 -

SMART Selective self-test log data structure revision number 1

SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS

1 0 0 Not_testing

2 0 0 Not_testing

3 0 0 Not_testing

4 0 0 Not_testing

5 0 0 Not_testing

Selective self-test flags (0x0):

After scanning selected spans, do NOT read-scan remainder of disk.

If Selective self-test is pending on power-up, resume after 0 minute delay.

Zitat von macom

These seem to be results of different drives.

Maybe these instances occurred in different time intervals?