T0a

Das 32GB ECC Modul von Kingston ist wirklich super preiswert. Ich habe für den gleichen Preis vor einem Jahr ein ECC Modul mit nur 16GB von Samsung erworben. Solltest du viel mit Virtualisierung machen, bietet es sich an zeitnah ggf. ein zweites Modul zu erwerben. Ich habe zu Beginn den „Fehler“ gemacht nur ein günstiges ECC RAM Modul zu kaufen und habe zu einem späteren Zeitpunkt ein zweites Modul teurer nachgekauft. Unabhängig davon sind 32GB RAM natürlich auch für viele Szenarien ausreichend. Ich frage mich, ob der Preis mit der Einführung von DDR5 Speicher zusammenhängt oder mit einem anderen Ereignis in Verbindung steht (siehe Update) Viel Spaß beim Zusammenbauen. —— Preisverfall bei RAM (notebookcheck.com) Prognose über steigende RAM Preise (pcgameshardware.de)

I have observed some work regarding this problem in Github. Unfortunately, both changes got reverted. Allow multiple rows in NFS rule (4e25bc8cb158b31e7c5ed36f133713bef2d4e35c, revert) NFS security rule: change input to textarea, which allows more input (d6b67b44aa6909ed72b75d4238055eddc89ddf99, revert) I really hope Limetech will tackle the problem in one of their next releases.

Did you upgrade your Container to v1.10.0 around the the time you observed the problems? Can you please try to update your instance to the latest bug fix version v1.10.1 and check whether the problems persist? Make sure to do a backup before upgrading though. I assume this has nothing do to with the Unraid template per se as it hasn't changed recently.

Hi 👋, I did some experiments in this area I would like to share with you. Having the ability to provision VMs automatically within Unraid given user-specific seed configurations would be awesome. Here is what I did: Disclaimer: Do not experiment with your productive environment. The commands listed are not complete neither fully tested. The setup is a proof of concept. Execute at your own risk. Read the 'Open Issues' section first. The setup utilizes the vagrant libvirt plugin with a local vagrant installation. The Vagrantfile configures a libvirt based base box with Unraid like KVM options (attention: the configuration is incomplete and has side-effects. See below.). Native plugin installation on Ubuntu 22.04. There is also a docker container having all dependencies included already. # See: https://vagrant-libvirt.github.io/vagrant-libvirt/installation.html $ sudo apt-get purge vagrant-libvirt $ sudo apt-mark hold vagrant-libvirt $ sudo apt-get install -y qemu libvirt-daemon-system ebtables libguestfs-tools $ sudo apt-get install -y vagrant ruby-fog-libvirt $ vagrant plugin install vagrant-libvirt # Create the VM on the remote Unraid server $ vagrant up # Destroy the VM. Note the image remains in /var/lib/libvirt/images! $ vagrant destroy The Vagrantfile below configures only a small portion of what the original Unraid template contains e.g. the network configuration is missing entirely. Unraid lists the VM after bootstrapping in the VM section. You can also verify this by executing the command "virsh list --all". Right now, we cannot access the VM via the internal VNC viewer because the libvirt plugin does not support the websocket attribute (yet!). I am working on contributing this feature to the project. For now, you can manually edit the XML template and add the attribute "websocket = '5600'" to the graphics tag. Open Issues: The VNC viewer does not work, because the vagrant libvirt plugin does not support the websocket attribute (working on a contribution) Vagrant stores the image in "/var/lib/libvirt/images/" which is the default libvirt storage location. This configuration option comes from "/etc/libvirt/storage/default.xml". Changing the default storage location to "/mnt/user/domains" involves probably the Unraid team. Creating another storage pool and referencing it with "storage_pool_name" in the Vagrantfile is possible, but does not survive a reboot. I haven't touched the network configuration yet. At the moment, the proof of concept creates a dedicated network 'vagrant-libvirt' (see "virsh net-list --all") Discussion: After I did these initial tests, I don't know if it is worth the effort. It may be simpler to keep a golden master VM and copy its disks and VM template. There are also not a lot of libvirt vagrant boxes publicly available. In the end, I am still looking for a better solution to provision new VMs in a cloud like manner (with seed configuration) within Unraid. I would love to hear your ideas or solutions.

Duplicate of

Thank you for your feedback. After disabling the vm custom icon container the icon appears: $ ls -l /usr/local/emhttp/plugins/dynamix.vm.manager/templates/images/ total 120 -rw-r--r-- 1 root root 1007 Aug 31 2018 arch.png -rw-r--r-- 1 root root 3185 Aug 31 2018 centos.png -rw-r--r-- 1 root root 3604 Aug 31 2018 chromeos.png -rw-r--r-- 1 root root 3945 Aug 31 2018 coreos.png -rw-r--r-- 1 root root 2487 Aug 31 2018 debian.png -rw-r--r-- 1 root root 1138 Aug 31 2018 default.png -rw-r--r-- 1 root root 3193 Aug 31 2018 fedora.png -rw-r--r-- 1 root root 5405 Aug 31 2018 freebsd.png -rw-r--r-- 1 root root 1746 Aug 31 2018 libreelec.png -rw-r--r-- 1 root root 3404 Aug 31 2018 linux.png -rw-r--r-- 1 root root 3683 Aug 31 2018 openelec.png -rw-r--r-- 1 root root 4693 Aug 31 2018 opensuse.png -rw-r--r-- 1 root root 3081 Aug 31 2018 redhat.png -rw-r--r-- 1 root root 4495 Aug 31 2018 scientific.png -rw-r--r-- 1 root root 4430 Aug 31 2018 slackware.png -rw-r--r-- 1 root root 4407 Aug 31 2018 steamos.png -rw-r--r-- 1 root root 2080 Aug 31 2018 ubuntu.png -rw-r--r-- 1 root root 1097 Sep 6 2018 unraid.png -rw-r--r-- 1 root root 3677 Aug 31 2018 vyos.png -rw-r--r-- 1 root root 1634 Aug 31 2018 windows.png -rwxr-xr-x 1 root root 727 Sep 28 2021 windows11.png* -rw-r--r-- 1 root root 4022 Aug 31 2018 windows7.png -rw-r--r-- 1 root root 4342 Aug 31 2018 windowsvista.png -rw-r--r-- 1 root root 3221 Aug 31 2018 windowsxp.png It looks like I run into this issue here. Note that the windows11.png file permissions differ from the other files. Maybe they wrongly added the executable bit, while creating the new release bundle. Anyway, the original problems is resolved. Thank you.

I just upgraded from Unraid 6.10.3 to 6.11.2. Up until now, I couldn't discover any issues. I leave my upgrade steps here in case someone finds it useful:

How is your experience with the spice-html5 client? For an outsider, the client library looks like a tech preview and hasn't really received a lot of updates in the past. The only other relevant project I could find is this flexVDI/spice-web-client. I don't know how it compares. Don't get me wrong, I am just curious and want to hear your feedback.

Hi 👋, meine Liste wie folgt: vim tmux screen iperf3 powertop python-setuptools Unklar, ggf. eine Abhaengigkeit python2 Benoetigt fuer "Virtual Machine Wake On Lan" Plugin python 3 Unklar, ggf. eine Abhaengigkeit perl Benoegtigt, um ueber "update-ca-certificates" ein custom wildcard Zertifikat zu installieren (referenz)

It looks like your request has been addressed in the prerelease 6.11.0-rc2.

Hi 👋, vielen Dank fuer deinen Hinweis. Habe mir eines als Ersatz fuer mein Fujitsu D3644-B bestellt. Da CPUs in der Regel wesentlich langlebiger sind als Mainboards, ist es immer eine gute Idee bei alter Hardware fuer Ersatz zu sorgen. Eine alte CPU findet man mit groesserer Wahrscheinlichkeit auf dem Gebrauchtmarkt als ein passendes Mainboard wenn es um alte Hardware-Revisionen geht.

I would love having the ability to add custom root CA certificates as well. In my case, I have services available via HTTPS with a custom wildcard certificate on another Host. When I want to query the services with CURL from my Unraid box, I always have to add the "-k" flag to allow for insecure requests. @ddumont I suggest to use this Perl version for the latest Unraid version, which is based on Slackware 15.0. Right now, you install Perl from Slackware 14.x. That shouldn't be a problem in general, but can cause problems in certain situations with certain packages. I wonder if there is a problem executing your /boot/config/fix-ca-certificates script from within the USB stick. Didn't Unraid prevent you from executing scripts from the USB stick directly or am I wrong here?

This will allow everyone in my network to access the NSF shares, right? I would rather try to avoid that. As of now, only certain IP addresses have access to the shares. However, I cannot apply the options to these IP addresses as the rule input field has a size limit.

Indeed that solved the problem. Thank you so much! For reference, I clicked on the tab shares and selected the backup share. Then, under "Nfs Security Settings", I modified the existing rule to "<ip>(sec=sys,rw,insecure,anongid=100,anonuid=25699,no_root_squash)", where <ip> is the address of the Linux client. Update: Is there a way to set the options globally for NFS instead of per rule and IP for all shares? The rule field seems to have a length restriction. Thus, I cannot technically add the same options to all IPs.