Fresh install of OMV and receiving errors

I've just installed OMV again due to some issues. It is a fresh install on SSD and am receiving the following errors in the GUI:

: Missing 'required' attribute 'params'.

OMV\Json\SchemaValidationException: : Missing 'required' attribute 'params'. in /usr/share/php/openmediavault/json/schema.inc:625

Stack trace:

#0 /usr/share/php/openmediavault/json/schema.inc(399): OMV\Json\Schema->checkProperties()

#1 /usr/share/php/openmediavault/json/schema.inc(289): OMV\Json\Schema->validateObject()

#2 /usr/share/php/openmediavault/json/schema.inc(261): OMV\Json\Schema->validateType()

#3 /usr/share/php/openmediavault/rpc/proxy/json.inc(129): OMV\Json\Schema->validate()

#4 /usr/share/php/openmediavault/rpc/proxy/json.inc(50): OMV\Rpc\Proxy\Json->validate()

#5 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()

#6 {main}

Please could someone advise what has happened. I have not configured anything as of yet.

I tried but am on a Mac so used a fresh browser and problem solved!!

I've now started with a fresh build. I've been trying a lot of things over the past few weeks, I'm not a Linux expert so am learning the ropes. I've had a few issues with shares not being removed from existing drives and then issues when trying to unmount. I had to remove the shares and some other things from config.xml and it ended up breaking some things.

Learning all the caveats, hopefully on this new build I will be able to get everything working now. Disk encryption is one of my requirements and I'm interested to know how the N100 performs with a RAID1 array using LUKS!

Quote from ryecoaaron

You are doing things very wrong if you are editing config.xml.

Yes, I am a beginner with Linux. Things are going to go wrong, however I am here to learn.

Quote from ryecoaaron

The idea is just to refresh or clear the browser cache. cmd-shift-R is what should work on a mac but I don't use macos. Clearing your browser cache would work.

Quote from ryecoaaron

I understand but editing config.xml should not be happening at the early learning level.

Before touching config.xml I made some mistakes with the filesystem which caused mount points to show as 'missing' in OMV. Also share folders were deleted without removing references to them and some other issues happened as a result of shares existing from an older build of OMV.

The issues did not seem to be resolvable in the GUI so after reading a post on this forum I decided to follow the instructions on that post and remove the mount points and shares from config.xml. This worked and fixed all of those issues, but later I encountered another issue.

I decided at that point to rebuild the system as it was my first attempt. Now I have learnt useful skills and hopefully it should be better with the knowledge gained..

Quote from chente

Removing the services that point to those file systems is enough to be able to remove the missing file systems. Or point those services to another existing file system.

What has happened is the SMB references pointed to a given folder. The folder was deleted via CLI in error. The SMB reference was then removed, however the folder itself still has 'reference' ticked in the shared folders section. This prevents me from deleting the folder in OMV GUI. Unfortunately I've made this mistake again today as I am still learning how to do this.

I cannot see a way of removing the shared folder in the GUI because it is still 'referenced'. The only way I managed to fix this was to modify config.xml to remove the now deleted shared folders.

If you have any other ideas it would be helpful! Thanks

Quote from ryecoaaron

You must have missed a reference to the sharedfolder. If you install the resetperms plugin, it would show you what else is referencing it.

Thanks