Mounting File System thows error but eventually comes back on line

billyp1970 · 8. März 2023

FIrst I looked and seached in the Forums and couldn't find what I was looking for so if this is covered somewhere else I aplogize as I didn't find it.

I'm running OMV6 with the latest patch (as of 3/8/2023), For the last few days any time I start or reboot my system I get several emails...

The first one that comes is this...

Code

The system monitoring needs your attention.

Host:        XXXXXXXserv
Date:        Wed, 08 Mar 2023 16:04:21
Service:     filesystem_srv_dev-disk-by-uuid-4f7e6f67-f219-4aa9-837d-bf83b98d0f05
Event:       Does not exist
Description: unable to read filesystem '/srv/dev-disk-by-uuid-4f7e6f67-f219-4aa9-837d-bf83b98d0f05' state

This triggered the monitoring system to: restart

Followed by (x2):

Code

The system monitoring needs your attention.

Host:        XXXXXXXserv
Date:        Wed, 08 Mar 2023 16:04:51
Service:     mountpoint_srv_dev-disk-by-uuid-4f7e6f67-f219-4aa9-837d-bf83b98d0f05
Event:       Status failed
Description: status failed (1) -- /srv/dev-disk-by-uuid-4f7e6f67-f219-4aa9-837d-bf83b98d0f05 is not a mountpoint

This triggered the monitoring system to: alert

Then...

Code

The system monitoring needs your attention.

Host:        XXXXXXXserv
Date:        Wed, 08 Mar 2023 16:05:51
Service:     filesystem_srv_dev-disk-by-uuid-4f7e6f67-f219-4aa9-837d-bf83b98d0f05
Event:       Exists
Description: succeeded getting filesystem statistics for '/srv/dev-disk-by-uuid-4f7e6f67-f219-4aa9-837d-bf83b98d0f05'

This triggered the monitoring system to: alert

Then finally (x2)..

Code

The system monitoring needs your attention.

Host:        XXXXXXXserv
Date:        Wed, 08 Mar 2023 16:06:21
Service:     mountpoint_srv_dev-disk-by-uuid-4f7e6f67-f219-4aa9-837d-bf83b98d0f05
Event:       Status succeeded
Description: status succeeded (0) -- /srv/dev-disk-by-uuid-4f7e6f67-f219-4aa9-837d-bf83b98d0f05 is a mountpoint

This triggered the monitoring system to: alert

I'm still very much a nubie, so I'm not sure what logs are needed for further troubleshooting by whomever is able to help. I do have the SMART monitoriting on. All the markers which are read on my disks read "GOOD".

My system is as follows:

Version
6.3.3-1 (Shaitan)

Processor
AMD Ryzen 5 3400G with Radeon Vega Graphics

Kernel
Linux 6.0.0-0.deb11.6-amd64

RAM

16 Gig

Video Card

Nivida P600 (for Plex Transcoding)

Storage

3 - 6TB Ironwolf Harddirves Using a RAID 5 configuration

1 - 250G SSD

If anyone is able to tell me why it takes so long for my system to see my disks as mounted or what I need to do to fix it I will be most grateful. Looking at the email above, I can tell you that it actually takes longer than what the time stamps suggest above.

Dudesplace · 9. März 2023

I’d double check your drive cables,

Both power and data.

And are you using hardware or software RAID?

billyp1970 · 9. März 2023

I will check the cables, but the server hasn't moved or been apart in the time this started.

I'm using OMV6's software RAID, I've not had issues until recently

EDIT:

I opened the server up and reseated both the power and data cables (data cables on both ends) and had the same issue.

billyp1970 · 10. März 2023

I've run cat /etc/fstab and got the following code. I don't know if this helps.

Code

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=c16ccf95-4630-4f12-a0dc-34a6dc3804d9 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=2AB0-EAA1  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/nvme0n1p3 during installation
UUID=a1cf8f13-af99-4917-8c13-72f9da092148 none            swap    sw              0       0
# >>> [openmediavault]
/dev/disk/by-uuid/4f7e6f67-f219-4aa9-837d-bf83b98d0f05          /srv/dev-disk-by-uuid-4f7e6f67-f219-4aa9-837d-bf83b98d0f05      ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
# <<< [openmediavault]

Alles anzeigen

Mounting File System thows error but eventually comes back on line

Jetzt mitmachen!

Tags