File system mounted to /srv but trying to mount to /media when creating a share

paperhino · 9. Oktober 2018

I have an OMV that started as an OMV 2.? that has been upgraded to OMV 3 and now OMV 4.1.12 in case that matters. As far as I could tell everything was working just fine for about a month. All my drives are present and shares are working. All my plugins work after I reinstalled them.

Yesterday I got a new external hard drive and I formatted and created an EXT4 file system on it through OMV. I can verify that the drive is mounted to /srv and I can create files and such on it. So far so good.

However, when I try to create a share (so far I've tried Apple and NFS) on this drive I get the following error:

Code

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl restart 'sharedfolders-backups.mount' 2>&1' with exit code '1': A dependency job for sharedfolders-backups.mount failed. See 'journalctl -xe' for details. in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1)
#1 /usr/share/php/openmediavault/system/systemctl.inc(160): OMV\System\SystemCtl->exec('restart', NULL, false)
#2 /usr/share/openmediavault/engined/module/sharedfolders.inc(66): OMV\System\SystemCtl->restart()
#3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleSharedfolders->startService()
#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatus9D...', '/tmp/bgoutputQv...')
#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#13 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#14 {main}

Alles anzeigen

When I run journalctl -xe I see the following line over an over from monit: 'mountpoint_media_bb921ad9-1f85-4062-9469-a81004ed2c6a' status failed (1) -- /media/bb921ad9-1f85-4062-9469-a81004ed2c6a is not a mountpoint.

So somehow and somewhere there appears to be a missmatch where the drive is mounted to /srv as it should be in OMV 4 but the rest of the system is looking for it in /media.

When I look in fstab I see that it is indeed configured to mount the drive to media instead of srv.
When I reboot the drive comes back mounted to /srv.
When I unmount the drive in /srv and try to mount /media/bb921ad9-1f85-4062-9469-a81004ed2c6a the command happily runs without error but doesn't mount the drive.

I am far from an expert in OMV.

Is there something I can do to fix this or should I trash it and install OMV 4 from scratch?

Many thanks

Rich

gderf · 9. Oktober 2018

I would search the file /etc/openmediavault/config.xml for the string:

/media/bb921ad9-1f85-4062-9469-a81004ed2c6a

and if it's there post the section it is in.

paperhino · 9. Oktober 2018

I see it in config -> system -> fstab -> mntent

Code

<mntent>
        <uuid>1b16f039-9162-4770-95a7-1fbd7093c047</uuid>
        <fsname>bb921ad9-1f85-4062-9469-a81004ed2c6a</fsname>
        <dir>/media/bb921ad9-1f85-4062-9469-a81004ed2c6a</dir>
        <type>ext4</type>
        <opts>defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>
        <freq>0</freq>
        <passno>2</passno>
        <hidden>0</hidden>
      </mntent>

This the only place and it matches with the information in /etc/fstab.

gderf · 10. Oktober 2018

I'm confused. In your original post I got the idea that this drive was mounted in /srv, but you say you have an entry in fstab that mounts it in /media.

Any chance you have multiple statements in fstab that try to mount the same drive twice?

Also, look again in config.xml and see where else /media shows up.

paperhino · 10. Oktober 2018

Indeed. The drive is being mounted to /srv. fstab has a line for mounting the drive to /media.

/media shows up all over the place as all of the drives that I have configured prior to upgrading to OMV 4 were originally mounted there. It is only the new drive I just added to the system since upgrading to OMV 4 that is having this weird problem. I can't figure out how the new drive is being mounted at all frankly.

Code

rich@fafnir:~   df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            483M     0  483M   0% /dev
tmpfs           100M  7.6M   93M   8% /run
/dev/sda1        15G  2.7G   12G  19% /
tmpfs           499M     0  499M   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           499M     0  499M   0% /sys/fs/cgroup
tmpfs           499M  4.0K  499M   1% /tmp
/dev/sdg1       197M   82K  197M   1% /srv/dev-disk-by-label-EFI
/dev/sdd1       1.8T   79G  1.7T   5% /media/e94f8644-b800-4f57-8101-0a561803af0b
/dev/sdc1       3.6T  851G  2.8T  24% /sharedfolders/media
/dev/sdh1       932G  326M  932G   1% /media/1C066AEA066AC3FC
/dev/sdb1       1.5T   15G  1.5T   1% /media/2e53bcde-c8c6-4f39-8dbe-e46bd6422501
/dev/sdg2       932G  730G  203G  79% /media/6DE5C8E878DBE3BD
/dev/sdf1       7.3T   93M  7.3T   1% /srv/dev-disk-by-label-Backups

Alles anzeigen

The last file system on line 16 is the troublesome one. As you can see it is mounted to /srv.

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).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=3794c3a9-4536-449e-9d32-cd508ffb9dd5 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=22e7d102-a32c-4ae1-90b9-ca76ce0fae13 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
# >>> [openmediavault]
UUID=2e53bcde-c8c6-4f39-8dbe-e46bd6422501 /media/2e53bcde-c8c6-4f39-8dbe-e46bd6422501 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
UUID=9d19966b-a21b-48b4-a4f3-65a770abd12c /media/9d19966b-a21b-48b4-a4f3-65a770abd12c ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
UUID=e94f8644-b800-4f57-8101-0a561803af0b /media/e94f8644-b800-4f57-8101-0a561803af0b ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
UUID=bb921ad9-1f85-4062-9469-a81004ed2c6a /media/bb921ad9-1f85-4062-9469-a81004ed2c6a ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/1C066AEA066AC3FC /media/1C066AEA066AC3FC ntfs defaults,nofail 0 2
/dev/disk/by-uuid/6DE5C8E878DBE3BD /media/6DE5C8E878DBE3BD ntfs defaults,nofail 0 2
/dev/disk/by-label/EFI /srv/dev-disk-by-label-EFI vfat defaults,nofail 0 2
/dev/disk/by-label/Backups /srv/dev-disk-by-label-Backups ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/media/2e53bcde-c8c6-4f39-8dbe-e46bd6422501/home/rich /export/rich-home none bind 0 0
/srv/dev-disk-by-label-Backups/files /export/backup-files none bind,nofail 0 0
# <<< [openmediavault]
tmpfs           /tmp            tmpfs   defaults        0       0

Alles anzeigen

The drive appears in fstab above on line 16 (the id of the drive is the one that starts with "bb").

The path /media appears in config.xml once for each of the above entries. And for all but the drive with the id starting with "bb" that is correct and for all but that drive it is working.

Anyway, I've tried some simple editing of config.xml and I'm convinced at this point that I should probably just go ahead and start with a fresh install of OMV and configure everything again from scratch.

Thanks for the help.

Jetzt mitmachen!