Well still trouble shooting as I would like to understand why it is not working. What I saw is that the new drive never gets added in the config.xml which is strange as I can access it through CLI under /srv/ just cannot get it to be referenced and be used as a shared or parity drive.
The backup idea is not so bad, you could have said it in less words 
So I had a file system (ext4) on my new drive /dev/sdc1 under the tab File Systems. When I tried to use it for my parity drive it doesn't show up in the SnapRAID plug-in. I unmounted it, deleted it (all under the GUI) and then rebooted the system. During the boot up script it hangs for 1m30s still looking for sdc1 (a start job is running for .....) so I am assuming it has not been deleted correctly even if it doesn't show up anymore in the GUI under the File Systems tab.
Now I unmounted and deleted the file system. At reboot it hangs for a while as in the boot sequence it searches for the file system I have just deleted (a start job is running for .....) . It looks like the delete is not being correctly applied. At no point during the unmount or deletion was I asked to save the changes in the GUI.
I guess this means that I have an issue with my omv config file somewhere?
My main goal is trying to add this new drive as a parity drive in snapraid. In addition to mounting the drive do I need to do any additional steps in order to see the drive appear in the drop-down list of the snapraid plugin?
I don't remember having to do anything else when I first set up snapraid.
Thanks.
As the subject mentions, I installed a new drive, created a new file system (ext4), mounted it, all via the GUI. I can access it when I SSH into the install but the drive doesn't show up in the shared folders or snapraid drop down. I want to add it as an additional parity drive.
I did get the below error when mounting it but it seems related to the mergefs file system created and nothing to do with the new drive which is /srv/dev-disk-by-label-Parity1
Anyone has any ideas? Thanks
file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_9ff94b2d-2899-4b76-bf70-51d7a377d751 for file /etc/fstab was charged by text Started: 22:16:37.388216 Duration: 0.572 ms Changes: ---------- ID: mount_filesystem_mountpoint_9ff94b2d-2899-4b76-bf70-51d7a377d751 Function: mount.mounted Name: /srv/dev-disk-by-label-Parity2 Result: True Comment: Target was already mounted Started: 22:16:37.388852 Duration: 39.298 ms Changes: ---------- umount: Forced remount because options (acl) changed ---------- ID: create_filesystem_mountpoint_6ba42e94-adb6-4845-b3b1-ba162972280a Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_6ba42e94-adb6-4845-b3b1-ba162972280a for file /etc/fstab was charged by text Started: 22:16:37.428281 Duration: 0.621 ms Changes: ---------- ID: mount_filesystem_mountpoint_6ba42e94-adb6-4845-b3b1-ba162972280a Function: mount.mounted Name: /srv/dev-disk-by-label-Parity1 Result: True Comment: Target was already mounted Started: 22:16:37.428965 Duration: 38.899 ms Changes: ---------- umount: Forced remount because options (acl) changed ---------- ID: create_unionfilesystem_mountpoint_2abfed19-0612-4158-832c-5df513c28671 Function: file.accumulated Result: True Comment: Accumulator create_unionfilesystem_mountpoint_2abfed19-0612-4158-832c-5df513c28671 for file /etc/fstab was charged by text Started: 22:16:37.467998 Duration: 0.568 ms Changes: ---------- ID: mount_filesystem_mountpoint_2abfed19-0612-4158-832c-5df513c28671 Function: mount.mounted Name: /srv/dad6d43e-9384-4139-871f-e08aadb6cb04 Result: False Comment: Unable to unmount /srv/dad6d43e-9384-4139-871f-e08aadb6cb04: umount: /srv/dad6d43e-9384-4139-871f-e08aadb6cb04: target is busy.. Started: 22:16:37.468628 Duration: 25.446 ms Changes: ---------- umount: Forced unmount and mount because options (direct_io) changed ---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: No changes needed to be made Started: 22:16:37.496094 Duration: 2.014 ms Changes: Summary for OMVtest ------------- Succeeded: 18 (changed=9) Failed: 1 ------------- Total states run: 19 Total run time: 556.664 ms
There is a new plugin called mergerfsfolder see if you can install maybe can push the error away. Keep posted here how it goes. This is probably a bug the union fs backend.
Thanks. That did the trick. Should I use to mergerfsfolder plugin going forward instead of the union filesystems?
Hi,
OMV 5 was running well and I just installed the update that was under "Update Management". It is now running 5.2.3-2(Usul) however I am now getting the error stated in the subject "The data model 'conf.service.mergerfsfolders.folder' does not exist." It pops up randomly or when I select certain options.
The drives are all appearing in Storage - Disks but if I click on Storage - File System I get the error and no file systems are listed. Same thing if I click on Shared folder. Under the Snapraid tab i see all my setup.
What is strange is that my merged drives are still accessible via the network so everything seems to be ok on that front. Portainer also still running. Content of the drives is also available via the terminal session so all is being well mounted. I am guessing the config file must have gotten corrupted somehow.
The detailed error message I am getting is:
Error #0:
OMV\Exception: The data model 'conf.service.mergerfsfolders.folder' does not exist. in /usr/share/php/openmediavault/datamodel/manager.inc:149
Stack trace:
#0 /usr/share/php/openmediavault/config/database.inc(68): OMV\DataModel\Manager->getModel('conf.service.me...')
#1 /usr/share/php/openmediavault/system/filesystem/backend/unionabstract.inc(64): OMV\Config\Database->get('conf.service.me...')
#2 /usr/share/php/openmediavault/system/filesystem/backend/manager.inc(280): OMV\System\Filesystem\Backend\UnionAbstract->enumerate()
#3 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(821): OMV\System\Filesystem\Backend\Manager->enumerate()
#4 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(71): OMV\System\Filesystem\Filesystem::getFilesystems()
#5 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->enumerateFilesystems(NULL, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#7 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(322): OMV\Rpc\ServiceAbstract->callMethod('enumerateFilesy...', NULL, Array)
#8 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->getList(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('getList', Array, Array)
#11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatuscK...', '/tmp/bgoutputvk...')
#12 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#13 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(471): OMV\Rpc\ServiceAbstract->callMethodBg('getList', Array, Array)
#14 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->getListBg(Array, Array)
#15 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#16 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getListBg', Array, Array)
#17 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('FileSystemMgmt', 'getListBg', Array, Array, 1)
#18 {main}
Any help would be appreciated as I do not want to reinstall everything. Thanks
Hi,
Completely lost here. I searched the forum but still cannot find the solution. Running a clean OMV 2.X and cannot get sabnzb to run even after searching the entire forum for "Failed to get configuration (xpath=//services/sabnzbd)".
This is a clean install (yesterday) of OMV after running it for 2y + without issues.
After installing it from the GUI I get "Failed to get configuration (xpath=//services/sabnzbd)".
If I run apt-get -f install I get the following:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up openmediavault-sabnzbd (1.0.5) ...
sabnzbd user already exists.
dpkg: error processing openmediavault-sabnzbd (--configure):
subprocess installed post-installation script returned error exit status 4
Processing triggers for openmediavault ...
Restarting engine daemon ...
Errors were encountered while processing:
openmediavault-sabnzbd
Creating index of upgradeable packages ...
Creating index of openmediavault plugins ...
E: Sub-process /usr/bin/dpkg returned an error code (1)
Still get the same error message from the GUI
Error #3003:exception 'OMVException' with message 'Failed to get configuration (xpath=//services/sabnzbd)' in /usr/share/openmediavault/engined/module/sabnzbd.inc:57Stack trace:#0 /usr/share/openmediavault/engined/rpc/services.inc(63): OMVModuleSabnzbd->getStatus()#1 [internal function]: OMVRpcServiceServices->getStatus(Array, Array)#2 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)#3 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getStatus', Array, Array)#4 /usr/sbin/omv-engined(500): OMVRpc::exec('Services', 'getStatus', Array, Array, 1)#5 {main}
OKHide details
Any ideas? Thanks.
