I would look at an intel n100 system that has a 2.5gbps network adapter with 4tb nvme stick (much faster than raid 5). I think you could do that in your budget.
Beiträge von ryecoaaron
-
-
Hello I want to resurrect this thread to ask if current version OMV7 is SMP compatible, or if the kernel plugin permit to select a SMP kernel.
I have a server Motherboard with 2 CPU, but only one is detected.OMV has always been SMP compatible. There actually is no kernel that doesn't support SMP anymore.
Are you referring to a 2 socket motherboard? For the most part, there is no difference with a 2 socket board because single socket cpus are multi-core. I have run OMV on many 2 socket boards over the years. Even a quad socket once. No need to worry about it being supported. OMV isn't Windows lol.
-
dd is also going to be much slower on a new setup than fsarchiver or borgbackup because it has to copy every single sector on the filesystem.
-
I moved this to a new thread since it wasn't relevant to kvm backup.
Is there a step by step guide to
Backup the OMV drive (mines sata), like a usb to clone to another driveThere are many different ways to do this. The best is to use clonezilla. You could also use the backup plugin or omv-regen.
Reverting quickly is not as easy. I would recommend testing in a VM with snapshots if you want to test.
-
However, I did notice that my command is "0 3 */18 * *".
You must have checked the "Every N day of the month" checkbox. Uncheck that and it will do what you want.
-
Hello, it could be very usefull if you can make a complete tutorial with the exact procedure, i also own a NSA320 and i want to put OMV on him.
Many things have changed in the four years since that was posted. The NSA320 is not a good candidate for OMV since it is very slow and armel. There is no docker support for the most part on armel.
-
Is this okay?
Have you seen any problems? When kvm (not the plugin) tells the VM to shutdown, the docker service is sent the shutdown signal. The docker service shuts down the containers. If they aren't shutdown in the default 10 sec timeout, the containers are forced down. You could change the stop-timeout parameter in /etc/docker/daemon.json. I wouldn't do this unless you are seeing problems.
-
Have a new plugin in the testing location for manual install
wget https://omv-extras.org/testing/openmediavault-scripts_7.0_all.deb -O openmediavault-scripts_7.0_all.deb
sudo dpkg -i openmediavault-scripts_7.0_all.deb
This plugin allows creation and editing of scripts and then scheduling the scripts.
-
The way I did worked was...
That is the normal way. I had assumed you tried it and didn't suggest it. Glad it is fixed.
-
how exactly do I access this "workbench"? I'm not familiar with all of this.
I should've read more. I didn't realize you were trying to fix the web interface. It doesn't look like you have tried omv-firstaid by logging in via ssh as root.
-
The port number setting for OMV/nginx is in System -> Workbench in the web interface.
-
Delete button is not active
Because you had a snapshot.
sudo virsh undefine win10
if that doesn't work,
sudo virsh destroy win10
-
Do you mean you can't reproduce the problem itself or only the UDP thing?
Just the part I quoted. I have no problem mounting via udp with udp enabled and tcp disabled.
-
How Can I remove this VM from the VM tab?
What error do you get when you try to use the Delete menu? I know the Delete + Storage will fail but the other should work.
Is there a reason you didn't delete it from the menu instead of finding the files? Delete + Storage would have done what you are trying to do.
-
I recommend installing the openmediavault-kernel plugin and installing the proxmox kernel.
-
why UDP only works if I enable TCP.
I can't replicate that problem.
-
Disable nfs v4 in the omv web interface and apply changes.
Enable tcp in /etc/nfs.conf.d/99-openmediavault.conf
Restart nfs-kernel-server with sudo systemctl restart nfs-kernel-server
Does everything work then?
-
Run the fix6to7 script.
-
I don't understand why v4 isn't used, maybe the path is not for v4? I have in mind that v4 don't need export I think.
If you want v4, mount it with just the share name: sudo mount.nfs 192.168.1.125:nfstest1 /mnt
-
On line 12, remove the last --nfs-version. Then try sudo apt-get -f install again.