I will try to help a little but I need a break from thinking - brain is fried.
I would use deltacopy to sync from windows to your OMV box with rsyncd enabled/modules created. Then I would rsnapshot the shared folders on the OMV box. I guess you could run snapraid on both boxes.
No need for a warning now. Only plugins that work with the latest OMV 3.x are in the repo. Hopefully this prevents the problems.
I have purged all non-ported plugins from all OMV 3.x omv-extras repos.
I have purged all non-ported plugins from all OMV 3.x omv-extras repos.
The site didn't disable.
rm /etc/nginx/sites-enabled/openmediavault-nginx
service nginx restart
nginx_dissite openmediavault-nginx
service nginx restart
omv-firstaid to restore to port 80
Change omv web interface to 8042 or whatever
nginx_ensite openmediavault-nginx
service nginx restart
You didn't pick one of my options. I still don't know what you mean by "disk". Here is a the post explaining how the plugin works and how to restore. It isn't easy.
Disable the other service using port 80 until you can get the omv web interface working and change the port then.
I hate to say it but the letsencrypt plugin has not been ported yet either. I guess I just need to start deleting repos since there is no good way to keep people from installing plugins that aren't ported.
Looks like the only way to fix is get a new bios (due to bios bug) or disable acpi. If you never turn off your server, disabling acpi might work. If you are compiling your own kernel and you don't use ATA, you could try disabling libata/ata. That would take some experimenting on your part.
Fixed in repo now.
Not enough details... Are you running an RPi1? What is the output of: dpkg -l | grep openm Some plugins are not ready for the latest version of 3.x.
Try omv-firstaid
Try omv-firstaid now.
By burn to a disk, do you mean burn to a DVD or restore to a hard drive?
IF you had to install a gui or kodi or anything graphical (I always recommend against this), OMV 3.x is better than OMV 2.x.
It is true. I install OMV 3.x multiple times per day most days. There are harmless errors that people worry too much about. Commercial NASes just hide the errors. Whenever you install a php or nginx update, nginx and/or php5-fpm need to be restarted. This generates communication errors until the service is restarted. This is almost impossible to avoid but harmless.
As for the plugins, that is my fault. I have left the plugin not compatible with OMV 3.0.13+ in the repo because quite a few users are still using OMV < 3.0.13. That is why I said it is stable with the ported plugins. The list is always changing hence the lack of a list. OMV 3 is still developing. I have been using it for months but my systems are setup and not changing much.
It is very easy to remove/uninstall plugins from the shell. Remember OMV is just a frontend for shell commands. I posted the remove command in the other thread - apt-get purge openmediavault-wol
I really think you just need to be more patient. Once a server is setup and working, very little needs to be changed and that is when it shines. If you are installing things all the time, stability is reduced. This happens on all server - Linux, Windows, etc.
The plugin only works with OMV. There is no way for it to work with docker. Sorry.
Try clearing the browser cache. Otherwise, try:
omv-mkconf nginx
omv-mkconf php5fpm
systemctl restart nginx
systemctl restart php5-fpm
See your other post. OMV 3.x itself is stable. Some of the plugins that haven't been ported will not let omv-engined run making you think OMV is not stable.
Patience... You installed the openmediavault-wol plugin. It has not been ported to datamodels (OMV 3.0.13+). If you remove it, everything should work. apt-get purge openmediavault-wol OMV 3.x is good as long as you are careful which plugins you install.
