Mount Errors piling up

Hi, I'm setting up a new OMV6 with plans to migrate data from an OMV4 system. I have checked the logs and found there are several thousand of these error messages...

******************************

10/27/2023, 5:53:36 PM
monit[996]: 'filesystem_srv_dev-disk-by-uuid-221CA3181CA2E64F' unable to read filesystem '/srv/dev-disk-by-uuid-221CA3181CA2E64F' state

10/27/2023, 5:53:36 PM
monit[996]: Filesystem '/srv/dev-disk-by-uuid-221CA3181CA2E64F' not mounted

10/27/2023, 5:53:06 PM
monit[996]: 'mountpoint_srv_dev-disk-by-uuid-221CA3181CA2E64F' status failed (1) -- /srv/dev-disk-by-uuid-221CA3181CA2E64F is not a mountpoint

10/27/2023, 5:53:06 PM
monit[996]: Filesystem '/srv/dev-disk-by-uuid-221CA3181CA2E64F' not mounted

10/27/2023, 5:53:06 PM
monit[996]: 'filesystem_srv_dev-disk-by-uuid-221CA3181CA2E64F' unable to read filesystem '/srv/dev-disk-by-uuid-221CA3181CA2E64F' state

10/27/2023, 5:53:06 PM
monit[996]: 'mountpoint_srv_dev-disk-by-uuid-221CA3181CA2E64F' status failed (1) -- /srv/dev-disk-by-uuid-221CA3181CA2E64F is not a mountpoint
*****************************************

Looking at my disks, the file systems and shared folders, I cannot find what this refers to.... Any ideas? Is there any way to stop this?

When viewing this huge and continuously expanding "daemon" log file, there is a "download button, but I do not see a "clear" or erase button or some way to clear out this bloated file.... How to clear the logs?

It is a backup drive used for USB backup. Are you saying it has to be linux for backup USB drive? Is that new in OMV 6. My older OMV 4 works fine with your everyday backup drives....

EDIT... how do I clear the log file? No "clear" button is shown in the interface?

The drive referenced in the errors is the backup drive that was attached to the server for USB backup. The errors are referring to that drive which is now unmounted and disconnected.

I made changes to the openmediavault-filesystem.conf by commenting out the references to checking and mounting the missing filesystem...

*************************************************************************

# Alert if disk space of root filesystem gets low

check filesystem rootfs with path /

if space usage > 85% for 5 times within 15 cycles

then alert else if succeeded for 10 cycles then alert

check filesystem filesystem_srv_dev-disk-by-uuid-e81ad6ef-c175-45b4-a2f4-1f954ebd3b7b with path "/srv/dev-d>

if space usage > 90% for 5 times within 15 cycles

then alert else if succeeded for 10 cycles then alert

# Try to auto-mount a filesystem if it is missing. Alert if the filesystem

# is still missing after a given time period.

check program mountpoint_srv_dev-disk-by-uuid-e81ad6ef-c175-45b4-a2f4-1f954ebd3b7b with path "/bin/mountpoi>

if status != 0

then alert

if status != 0 for 2 cycles

then exec "/usr/bin/mount '/srv/dev-disk-by-uuid-e81ad6ef-c175-45b4-a2f4-1f954ebd3b7b'"

#check filesystem filesystem_srv_dev-disk-by-uuid-221CA3181CA2E64F with path "/srv/dev-disk-by-uuid-221CA31>

# if space usage > 85% for 5 times within 15 cycles

# then alert else if succeeded for 10 cycles then alert

# Try to auto-mount a filesystem if it is missing. Alert if the filesystem

# is still missing after a given time period.

#check program mountpoint_srv_dev-disk-by-uuid-221CA3181CA2E64F with path "/bin/mountpoint '/srv/dev-disk-b>

# if status != 0

# then alert

# if status != 0 for 2 cycles

# then exec "/usr/bin/mount '/srv/dev-disk-by-uuid-221CA3181CA2E64F'"

***********************************************************************************************

This stopped the continuous errors... However after restarting monit, i am getting these errors every 8 minutes....

systemd[1]: dev-disk-by\x2duuid-221CA3181CA2E64F.device: Job dev-disk-by\x2duuid-221CA3181CA2E64F.device/start failed with result 'timeout'.

10/28/2023, 5:40:38 PM
systemd[1]: openmediavault-usbbackup-7eac253a9287f0b89e3543980fec1ca4.service: Job openmediavault-usbbackup-7eac253a9287f0b89e3543980fec1ca4.service/start failed with result 'dependency'.

10/28/2023, 5:40:38 PM
systemd[1]: Dependency failed for Execute the rsync backup jobs when /dev/disk/by-uuid/221CA3181CA2E64F is plugged in.

10/28/2023, 5:40:38 PM
systemd[1]: Timed out waiting for device /dev/disk/by-uuid/221CA3181CA2E64F.

10/28/2023, 5:40:38 PM
systemd[1]: dev-disk-by\x2duuid-221CA3181CA2E64F.device: Job dev-disk-by\x2duuid-221CA3181CA2E64F.device/start timed out.

***********************************************************************************

The USB backup interface has been configured with this particular drive as the "external storage device". So is this eight minute cycle normal to look for the connected USB device for backup?

Zitat von macom

Check if you find the uuid of that filesystem in

/etc/openmediavault/config.xml

The uuid is 221CA3181CA2E64F

If you find it, post here.

If you do not find it, run omv-salt deploy run monit.

After that the message should stop.

Alles anzeigen

thank you for your help. Here are the excerpts from config.xml where "221CA3181CA2E64F" occurs....

<mntent>

<uuid>70b35bbd-8756-4d0a-9c25-3a8cc93f068e</uuid>

<fsname>/dev/disk/by-uuid/221CA3181CA2E64F</fsname>

<dir>/srv/dev-disk-by-uuid-221CA3181CA2E64F</dir>

<type>ntfs</type>

<opts>defaults,nofail,big_writes</opts>

<freq>0</freq>

<passno>2</passno>

<hidden>0</hidden>

<usagewarnthreshold>85</usagewarnthreshold>

<comment></comment>

</mntent>

<job>

<uuid>d5a38152-cbc2-4e64-8ba4-0d1c71b19e58</uuid>

<enable>1</enable>

<mode>push</mode>

<sendemail>1</sendemail>

<comment></comment>

<devicefile>/dev/disk/by-uuid/221CA3181CA2E64F</devicefile>

<sharedfolderref>5d992499-1e38-4b75-9737-384533a7beb2</sharedfolderref>

<usesubdir>1</usesubdir>

<optionrecursive>1</optionrecursive>

<optiontimes>1</optiontimes>

<optiongroup>1</optiongroup>

<optionowner>1</optionowner>

<optioncompress>0</optioncompress>

<optionarchive>1</optionarchive>

<optiondelete>0</optiondelete>

<optionquiet>0</optionquiet>

<optionperms>1</optionperms>

<optionacls>1</optionacls>

<optionxattrs>1</optionxattrs>

<optionpartial>1</optionpartial>

<extraoptions></extraoptions>

</job>

<job>

<uuid>fac37491-809e-4b8f-973a-0cfbd6549b8c</uuid>

<enable>1</enable>

<mode>push</mode>

<sendemail>1</sendemail>

<comment></comment>

<devicefile>/dev/disk/by-uuid/221CA3181CA2E64F</devicefile>

<sharedfolderref>b2bab7a8-b05a-40cd-b24a-f80f58271b9d</sharedfolderref>

<usesubdir>1</usesubdir>

<optionrecursive>1</optionrecursive>

<optiontimes>1</optiontimes>

<optiongroup>1</optiongroup>

<optionowner>1</optionowner>

<optioncompress>0</optioncompress>

<optionarchive>1</optionarchive>

<optiondelete>0</optiondelete>

<optionquiet>0</optionquiet>

<optionperms>1</optionperms>

<optionacls>1</optionacls>

<optionxattrs>0</optionxattrs>

<optionpartial>1</optionpartial>

<extraoptions></extraoptions>

</job>

Zitat

From "SOma"...

It depends on how you set the plugin.

If you only use the plugin on the GUI (run the backup when you click "START", the look-up for the drive will only happen then)

If you made any conf to run at specific times, it will look-up always (or some time before)

PS: just saw that it can be that it runs automatically once the drive is plugged in.

If you don't have the drive plugged and get errors that it's missing, it looks that you have a scheduled created that is looking for it.

It depends on how you set the plugin.

If you only use the plugin on the GUI (run the backup when you click "START", the look-up for the drive will only happen then)

If you made any conf to run at specific times, it will look-up always (or some time before)

PS: just saw that it can be that it runs automatically once the drive is plugged in.

If you don't have the drive plugged and get errors that it's missing, it looks that you have a scheduled created that is looking for it.

Alles anzeigen

Thank you for your help. I am using the USB backup rsynch that operates when the external drive is plugged in. This is not configured with any scheduled event. My issues probably started when I first plugged the drive in, and my clumsy initiation and config for the plugin. I think i understand the premise and operation of this service, but i just did something wrong in the setup... Thanks again...

I have two shared folders enabled for backup to this designated external drive in the USB Backup plugin interface. My assumption is that this service would only be initiated when the external drive is plugged in. Am i wrong?

I configured the external storage device as "/dev/disk/by-uuid/221CA3181CA2E64F" when the device was connected and this shows on the main USB BACKUP page...However, The external device in the "edit" interface is greyed out when the external drive is not connected.

So, if i trash these enabled backup configs in the main USB Backup interface, will my shared folders still be backed up when connecting the external dive?

So, I'm good to go with config (?), but I guess I can live with the repeated error for the missing external device. As long as I get the backups, which seems to be working.... I will keep my eyes out for issues.

Is there any way to clear the error logs. I can't find an obvious way or button to do this.... Omv 4 had a simple "clear" button. I don't see this in OMV6/

Thanks for your time and help...

Zitat von macom

When you run the backup, is the filesystem unmounted automatically?

Just tested with 16gb new files to the server, they transferred correctly from another server... Then connected the backup drive by USB, it was mounted quickly and the rsynch backup proceeded to the USB drive, then the drive was UNMOUNTED. Shown as "online" but not mounted...

Looking good!