There is a link to the wiki I just added in the openmediavault-kernel plugin version 6.4.2 in the repo now.
Posts by ryecoaaron
-
-
Wasn't the plugin already capable of pulling that info?
Not yet.
-
Well, my installation also shows driver version 470.141. But my installation is some months ago.
It was probably upgraded when did an apt-get dist-upgrade. 141 still isn't in backports - https://packages.debian.org/se…es&keywords=nvidia-driver. And you probably didn't have any problems with .103 at the time because you were using an older, supported kernel.
-
I had read that I could use google for dns name resolution, so I set the DNS Server to 8.8.8.8. That's where we are now.
If it is working now, great. If it isn't, that is a network issue that you will need to figure out.
-
I don't combine it with the OMV plugin though. Just by itself via cli.
If I pointed everyone away from plugins, it would save me a lot of time but kind of missing the point of OMV though.
-
I prefer to keep the plugin using just wireguard commands instead of external utilities that might not be plugin friendly.
-
It used to be documented right in the plugin. I lost the ability to add that info when I moved to the datatable. I need to add a link in the plugin to a wiki (which needs to be written).
-
This is a good start - https://forum.proxmox.com/thre…-on-proxmox-ve-6-x.76137/. They don't offer their kernel source in a package like Debian does.
-
-
And I don‘t know why you‘ve installed nvidia-kernel-dkms.
Probably because I said to install it. I'm not following the tutorial because I have done this many times. There are many ways to do this. Your tutorial is a bit dated. You should not use the backports version (it is much older - 470.103 vs 470.141) and you never need to add backports repo manually as your tutorial states (use the button in omv-extras).
Consult /var/lib/dkms/nvidia-current/470.103.01/build/make.log for more information.
If you see 470.103, you are still installing from backports. You need to make sure backports are disabled in omv-extras, remove the existing nvidia packages, run sudo omv-aptclean, and then try again.
-
added `nonempty` to my mergerfs pool options
That could give you odd results since you will never know which copy of a file your system us using.
-
any timeline for it?
Nope. Not the most exciting plugin to write especially since I will have to create some kind of wireguard setup (which I don't use now) to even test basic function.
-
I accidentally moved your post thinking you were asking about the ReComputer. Four ports doesn't necessarily mean router. They could be used for high availability too. The Topton is a little weak to run proxmox with OMV and OpenWRT. You could run OMV on it with openwrt in a VM using the kvm plugin. But, personally I would keep openwrt (or ipfire or pfsense) on a separate device.
-
I can now Add KVM Pools
You could before too. You would just have to type in the path and not use the directory chooser.
is there any configuration lost that i have to reconfigure?
Nope. It only adds one entry to mntent. Did you edit the database? I can't figure out how that entry was deleted.
-
Then something happened to the sharerootfs entry. I would reinstall that plugin.
sudo apt-get install --reinstall openmediavault-sharerootfs
-
That doesn't look like all of it. You can attach a file with the output.
-
root@omv:~# sudo omv-showkey mntent~
You added a ~ to the end that should not be there.
-
You are trying to build nvidia-kernel-dkms from backports which is older than the version in the regular repo. Disable backports in omv-extras and then try again.
-
Should I do this before or after I clean up the mount point?
doesn't matter
Should I just delete the files under pool/ or should I delete the pool folder entirely?
Anything in /srv/mergerfs/pool/ but not /srv/mergerfs/pool.
-
if you are sure this is safe, use the 'nonempty' mount option
Something on your system is writing to the pool mount directory (/srv/mergerfs/pool) when the pool isn't mounted. You will need to clean up those files while the pool isn't mounted. Then it should mount. If you are using docker installed by omv-extras, you should click the install docker button again. It will update the docker override file to tell the service to wait for the filesystems and pool.
