MAM59

Paying for updates is nothing bad. You cannot expect any company to work for free for you for decades. They have to pay their employees, the rooms, the hardware... This does not work by selling licenses anmore after a time. The market is satuated somedays and improvements are hard to be built in after a while. So a wise company thinks about opening "new markets" long before they become bankrupt. If "once a year" is too much (I look at Adobe Elements, which are resold every year but the addons are marginally or do not help you at all), "once every major version" will be much less frequent (until they run low on money and just bump up the version number someday...). You with your old version are in a quite nice position, you will get unlimited updates for the old version, can take a look at them and decide later on, if you need them for the new server too (aka, spend the money AFTER you have reviewed it).

this usually means that you have combined more than one lan card into a "bond" (aka port aggragation, aka trunk), set this to something else than "active backup" and connect these cards to either the same switch without configuring the switch to support this trunk style, or connect them to different switches that are also connected to each others somehow (switch loop). In rare conditions it also can mean that your lan card is broken or switch are broken and reflect packets that should not. But the first version is much more likely.

Read the f*@king Manual! (of the Mobo) Most recent Motherboards are "overequipped", they contain more devices/connectors that they can handle at the same time (like "SATA5-8 only work if you do not use PCIe Slot #3" or "NVMe #3 only works if you turn off Wifi" (in BIOS)). So be sure to read the special sections and recheck if you did not accidentally created a non working combination. Although modern boards look very promising, the limits can drive you crazy. And Intel CPUs are always low on lanes, so it is more likely to run out of them.

move the data first, add parity later. this will be much quicker than the other way round. And NEVER try to do both things at the same time, it will come to an halt!

Thats not a PSU, thats a china joke. Totally unstable with spikes and so on. Get a real one (and a better case too as stated above).

I would say, heat is not your problem but the power supply maybe too small to handle all devices.

yeah, but thats also only half of the job. Normal plugins also need updates now and then...

Nice to know but not helpful too. Usually "checking for updates" is the only daily thing I do on UNRAID. So I go to App Page, wait, and wait, and wait... until I think "this should be enough now".

There is one thing that I dont like at CA, maybe someone can fix it someday: When you open the APP Page, CA scans installed VMs and Dockers for updates and show "update required" (or something alike, currently no update pending :-))) ) on the left menu under the "home" section. Thats fine, but also the problem. Yeah, we know that the background check is running and we know there will be a message if there is something to update. BUT, if there is no update, you never are informed that the check is done and you can leave the page! So you sit there, wait and wait and after a while you give up and do something else... Wasted Lifetime :-))) (gets valuable once you come into my region of age 🙂 ) So, my wish would be: just add a message "nothing to do" when the check is done and no updates could be found.

Don't know that card. I have no 8x slot available in any pc (hmm, the new gaming pc could... but this would reduce the grafics slot to 8x too and the mobo has already a 10G card onboard... but I still use the Mellanox on this one too, much more reliable)

Get a used Mellanox X3 card (warning! there are different versions with 8x2.0 or 4x3.0 PCIe slot demand! look at your mobo which one will fit. DONT run these cards with less than 4 or 8 lanes!!!). Microtik has CAT modules for 10G speed in stock, they are rather expensive and, worst of all, they get seriously HOT!. But if you run only one of them, this should work. But keep an eye on the temperature, if it gets too high, the switch turns the port OFF... BTW, your CAT6 cable is not the problem, the plugs on both ends are! Usually they are NOT CAT6, therefor they can produce a lot of problems. Also, lenghts >10m can be problematic! Be prepared for Link losses, Line Drops and Port resets... you have been warned. Better go for fiber or Direct Attach if possible.

Patience 😁 What you see is the difference between gross and net. You HAVE a 10G connection, but depending on the files you transfer, you do not reach the upper end. Small files will be slow because the overhead needed to adjust the folder content. Try to transfer a 1G+ file (a movie for instance). Also note that heavy load on UNRAID (like dockers or VMs) can slow down the whole machine. To be sure that all connections are ok, take a look at the status & error pages of the CRS305. If errors sum up a lot, there is a problem and if there are a lot of timeouts on the stats page, you know that something slows down the net (don't panic if this port connects to the 2.5G switch, it is totally normal that it stops the 10G line quite often, the cheap switches do not handle speed correction themselfs, they put the load onto the upper switch) Also keep in mind that high speeds only can be achived when writing NEW files to UNRAID only. File on and from the array are limited to real disk speeds. Better you create a new share ("TEST") directly and only on the NVME and use it for speed tests. This should work in both directions. But do not expect to see 1,1Gb/s, 700-900Mb/s are ok.

Du musst das in Relation zu Deiner LAN Geschwindigkeit sehen. Der Cache wird nur beim Schreiben von NEUEN Dateien benutzt, er sollte möglichst den ankommenden Daten standhalten können. Bei einem 1G LAN schafft das eine SATA SSD locker, bei einem 10G LAN kommen auch einfache NVMe SSDs ins Schwitzen. Für Docker und VMs sind NVMe deutlich besser, denn hier erfolgt der Zugriff ja lokal, ohne LAN Bremse. Ob man wirklich RAID1 braucht, muss jeder selber wissen. Auf jeden Fall halbiert sich dadurch die Schreibrate in den Cache sofort...

Falls es nochmals passieren sollte, empfehle ich erneute Löschung und vielleicht auch das "Einfrieren" auf die stabile Version 2.9.2. Damit hatte ich noch nie Ärger (mit Nachfolgern aber reichlich). Also mal im Hinterkopf behalten...

Ich benutz den npm (official) hab aber die Version auf 2.9.2 eingefroren