Why dont you Just follow my Guide?
Woops, I definitely read that you mentioned you wrote a guide, but completely forgot after reading the rest of the replies. Your guide looks like exactly what I need. Thank you!
Link for others who come across this post: https://forum.openmediavault.o…7148-HowTo-Kernel-Update/
From Source: https://forum.openmediavault.o…ernel-on-OMV-from-Source/
I do get a virtualbox error during the installation of the headers:
Setting up linux-headers-5.3.2-050302-generic (5.3.2-050302.201910010731) ...
/etc/kernel/header_postinst.d/dkms:
Error! Bad return status for module build on kernel: 5.3.2-050302-generic (x86_64)
Consult /var/lib/dkms/virtualbox/5.2.16/build/make.log for more information.
dpkg: dependency problems prevent configuration of linux-image-unsigned-5.3.2-050302-generic:
linux-image-unsigned-5.3.2-050302-generic depends on linux-base (>= 4.5ubuntu1~16.04.1); however:
Version of linux-base on system is 4.5.
dpkg: error processing package linux-image-unsigned-5.3.2-050302-generic (--install):
dependency problems - leaving unconfigured
Setting up linux-modules-5.3.2-050302-generic (5.3.2-050302.201910010731) ...
Errors were encountered while processing:
linux-image-unsigned-5.3.2-050302-genericIs is this just not compatible because I have virtualbox? Or is there an update I need to do for virtualbox first?
EDIT: I found this patch: https://www.virtualbox.org/ticket/18783
Not sure how to apply it though
From my understanding this patch is also included in the latest test builds: https://www.virtualbox.org/wiki/Testbuilds
Would these be safe to install? I remember it was a hassle installing virtualbox in OMV in the first place,although that was over a year ago.
I saw that Kernel 5.3 was released and had significant improvements to SMB performance which I would like to benefit from.
My system is:
Version: 4.1.26-1 Arrakis
Kernel: Linux 4.17.0-0.bpo.1-amd64
Would following this guide to compile and install Kernel 5.3 on debian work with OpenMediaVault?
https://www.cyberciti.biz/linu…ere-is-how-to-install-it/
Thanks!
Try this:
https://github.com/Red5d/docker-autocompose
This looks promising as well (paid):
https://opsani.com/skopos/docker-compose-generator/
This can be removed.... Ended up reinstalling from scratch
I noticed (bug?) that when I modify docker containers, if any errors come up during the saving modifications, it will destroy the container.
Basically after the initial error for something such as 'duplicate mount points' it takes you back to modify but any changes from then on display anothe rerror message "Error 0 -"
When you click cancel to get out of the modify modal, the container will now have disappeared and youll have to recreate it from the image again... This is extremely annoying and sometimes docker-plugin will occasionally throw errors just modifying an existing container, which causes you to lose the whole thing....
does fstab still have to be manually changed?
I installed docker plugin on a fresh OMV 4.x install, when i go to enable it,or do anything else in the plugin I get this message:
Running 'systemctl status docker.service' gives this output:
Relevant portions of SYSlog:
I think this line may be the most informative:
Mar 18 15:48:44 nas dockerd[5041]: Error starting daemon: error while opening volume store metadata database: no such device
Not sure where that path is set though...
Ive also tried the docker-ce plugin as well and gotten the same error :(. Any help would be greatly appreciated!
Ive also gotten the exact same result on a fresh OMV 3.x install...
1st problem:
I did a clean install to OMV 3.x after using OMV 2.x. Some of my data drives showed up while others did not. I have 2 that show up in Physical Drives but they dont show up in filesystems page. They have data on them.
Ah perfect! That worked! I also cleared my browser cache with helped.
Thanks alot!
So I had an openmediavault 2.x system with a mergerfs pool setup using unionfs plugin. I decided to do a fresh install to openmediavault 3.x. I wiped the OS drive and installed 3.x . However I didnt unsetup the drive pool before I did this...
Now I went into OMV 3.x and installed the unionfs plugin and when I go to ADD in the plugin to add a pool, no drives appear in the list and I get this error:
Are my previous drives recoverable? Is there anything you guys recommend I do?
I would also like top know the answer, I am having this issue as well.
I am trying to use the union file systems plugin to create a pool but it does not work at all. I tried aufs, mhddfs and mergerfs and they all had the same result:
when creating the pool It says "saving...." followed by an error saying: gateway timeout..
If I go back into the plugin to see if it was created it says "loading..." for a while and then "communication failure" and then no pools are displayed. The same things happens if I click on the filesystems page as well. No filesystems are listed anymore.
When I try to recreate the pool and use the same name it says "pool name exists" even though I cannot see the pool at all.
I have reinstalled Openmediavault 3 times and only installed omv-extras and the union file systems plugin as well as update all packages. The very first time I was able to successfully create a mhddfs pool but then I deleted it and tried to make a mergerfs pool instead. This is when everything started to go wrong... Are there any logs I can check to see whats going wrong here?