OMV 3.0.85 (Erasmus) running on a Raspberry Pi 3 (Jesse)
I have three USB-attached HDDs, no RAID set up. One of the drives has given up the ghost, and OMV no longer shows it under Storage > Physical Disks. This is okay, it was a very old drive and I'm not mourning its passing.
But the device (/dev/disk/by-label/MusicLibMirror) is still displayed under Storage > File Systems, shows as unmounted, and as referenced. There doesn't seem to be a way to delete this entry.
Under Shared Foiders, the share name that referenced a folder on the now-removed drive appears. Selecting it does not un-gray the "Delete" option.
None of this would be a bother to me except that OMV is unhappy if I try to mount a remote share using the Remote Mount plugin. If I Add a new Remote Mount, I am able to put in the remote share location and credentials, etc., and close the dialog box. But when I Apply the change to the configuration I get this:
Could not fetch a matching mount point from the provided fsname: '/dev/disk/by-label/MusicLibMirror' [NOTE, THIS IS THE FAILED AND NOW-DISCONNECTED DRIVE]
Error
#0: exception 'OMV\Exception' with message 'Could not fetch a matching mount point from the provided fsname: '/dev/disk/by-label/MusicLibMirror'.' in /usr/share/php/openmediavault/system/filesystem/backend/remoteabstract.inc:195 Stack trace:
#0 /usr/share/php/openmediavault/system/filesystem/backend/remoteabstract.inc(139): OMV\System\Filesystem\Backend\RemoteAbstract::fetchMountPointFromFstabByFsnameAndType('/dev/disk/by-la...', 'cifs')
#1 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(845): OMV\System\Filesystem\Backend\RemoteAbstract->getImpl('/dev/disk/by-la...')
#2 /usr/share/openmediavault/engined/module/fstab.inc(68): OMV\System\Filesystem\Filesystem::getImpl('/dev/disk/by-la...')
#3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleFsTab->startService()
#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(150): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(528): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatus7X...', '/tmp/bgoutputpY...')
#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(151): 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(124): 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}So, how can I make OMV happy? I'm done with that drive, it is a dead drive. But I need to figure out how to tell OMV to give it up.
I tried manually editing /etc/fstab to remove the mount but that didn't affect anything. used mount -a after editing, and tried a couple of reboots. OMV is stubborn.
