MAM59

Na ja, "Hilfe" ist das nicht gerade, aber, wenn Du doch die Plattenkonfiguration kennst, kannst Du doch mit wenigen Mausklicken ein neues Array erstellen und alles sollte wieder funktionieren ?!?!?
Nur bei der Paritätsplatte musst Du aufpassen.
Da gibts den Trick, die Platten einzeln mit Unassigned Devices versuchsweise zu mounten, normale Datenplatten sollten funktionieren, die Paritätsplatte nicht, da sie kein Filesystem hat.
Danach aus den gefundenen Datenplatten das Array zusammenklicken, ersmal ohne Parität (damit nicht aus Versehen was überschrieben werden kann).
Wenn die Daten ok aussehen, die Parität hinzuschalten und neu aufbauen lassen (sollte zwar noch stimmen, aber sicher ist sicher...)

Die SSDs Pools mit altem Namen wieder anlegen, da sollte gar kein Problem enstehen.

(ich hoffe, Du hast nicht so paranoide Einstellungen wie "verschlüsselte Dateisysteme" gehabt, dann würde es echt happig...)

try "mover stop" (at your own risk!)

Then ZFS-RAID will be best for you I think. You may even try the designated SATA SSD as "cache" but there are good chances that it wont be needed and can be used for other issues instead.

But of course, do not forget that you need an external means for "backup". Neither RAID or parity is a substitute for a real offline backup...

in 99% this can be seen with bad cable (or too long one). But I agree, it is very hard to track because they wont tell you the truth if you buy one.
Look at the cable, if there is something written on it like "rawcable", through it away. 10G only works almost stable with real cable and plugs at the ends.
If you cant make it out (I gave up after 6months of depressing tries), switch to fiber and you are done.

I would consider everything >5m lenght as a potentional source of evil. They say 30m would be fine, they lie...

Also ich verstehe ja die Idee hinter diesem Bond, allein, sie funktioniert so nicht. Es ist recht unschlau Karten mit unterschiedlichen Geschwindigkeiten in einem Bond zusammenzufassen. Der Kernel weiss dann nicht so genau, wie schnell er die Pakete loswerden kann und die Queue Berechnung kommt durcheinander. Das ist dann Stottern bis hin zu Blockaden mit Abbrüchen.

Also:
deaktiviere den Bond auf beiden Karten
geh in die Netzwerkregel und vertausche die MAC Adressen in den Listboxen (eth0 und eth1 tauschen dann die Karten, die Mellanox ist dann die "Haupt"karte)
das Defaultgateway sieht richtig aus, allerdings sorgt die Metrik von 1008 (oder so), dafür, dass es unter Umständen gar nicht zum Zug kommt. Hier gehört eine "1" rein

hmm... strange...
maybe it is best for you to disable the onboard nics in BIOS?

(maybe one of them is not really meant to be used as a general purpose network interface, but for management access only? Or could it be an ISCSI port or something?)

likely you are a victim of the famous "2.5G needs Flow Control" issue.
See if flow control is enabled on both ends and in the switch.
if not, a new connection often pick the wrong sending window and it is not received by the other side. After a timeout it is retried within a different window. This can slow down a connection up to 75% (but usually it is only 50%)

there is no need for <32G anymore. The restriction went away some Windows Versions earlier already.
Now you can create an (ex)FAT Partition with more then 32Gb and modern PCs can boot from it (keep your BIOS recent!)

But one thing from the old video still is important:
put the stick into an USB2.0 port even if it is a 3.x one! This will slow it down and cool it down too. It will last much longer in 24/7 operations
Boot speed will be faster slightly in 3.0 port, but you will regret it if the stick wears out quite fast. Boot Time is not really important, after the boot UNRAID runs from RAM, with full speed.

no, if you set this, you cannot make new assignments, it will keep the old config then.

actually it is
stop array
goto new config
do NOT preserve current assinments (you could keep pools if you like, but NOT the array)
put in new disks (the slots do not matter, so no need to move around all of them)
make new assignments
start array
new parity will be generated automatically

Be cautious not to assign old data drive as parity, else content would be lost. But in your case you have to pick one of the 12Tb drives as parity, they are empty, so it does not matter

You dont have a static IP if you have got it over DHCP.

You may have a pseudo static IP if the DHCP server is configured to send out always the same IP if the request comes from a certain MAC, but that is not the same as "static ip".

Ok, so far not helpful, I know :-)
I guess your firewall/DHCP server has undergone some changes due to recent updates or something. He does not find the old assignment anymore, so he issues a new address (the old one is still in the tables, so it should complain about double assignments somewhere, check the logs)

can't be. look at the screenshot
first comes the error message, a few lines later "executing go script"

Anyway you have pointed me into the correct direction, thanks.

"go" was just a fix for an error an update produced long long ago.
The "Dynamix System Temp" Plugin once detected the NCT6755 driver, which does not exist anymore. But on every reboot it wanted to load it.
No Temps and no fans anymore.
I've searched around and found the 6775 as the followup and added it to "go".

To fix it, open the settings in system temp, and just click on "detect". It will find the new driver and update the stored value.
(something that was missing at that UNRAID update long time ago)

Msg gone, fans and temp working

yes, this is normal if you ever updated UNRAID from early ZFS to current one.
You need to do "zpool update" once (will be necessary for further versions too maybe, so keep an eye open).
BUT BEWARE! once done, you cannot go back to older versions of UNRAID anymore! The disks will not be readable then!!!

On the other hand, this is only an INFO, it just says: "there are new features available that are currentlic not enabled yet, waiting for your approval."
You can also ignore it for the next decades, but of course, you will not get any benefit from the new features anymore too.

What HAS changed should be documented somewhere, you may compare the output of zpool-features on an "old" and a "new" filesystem and then decide if you want it or not.

But if you never plan to downgrade UNRAID, just do it and dont think about it.

As usual. bonding does not really help, as you can see.
But here it maybe that you have selected the wrong bonding mode. Seems that you have picked "active backup", but your switch wants something else (Static LAG configurations are not supported, only LACP (802.3ad).
So the two do not really talk to each other.
You may either try this mode, or leave the single port version (it is VERY unlikely that you will see a speed increase with the LACP. You need a lot of parallel clients to get benefits. Each single connection will still use only one card)

Send the transceiver back and get a real one directly from MikroTik.
Or at least from 10GTek, they are known to work.
(Beware, the MikroTik one is "10G only!". It does not run with 2,5G or 5G. Or, they have a more modern model available now, dunno. RJ45 is dead for me, only Fiber is used anymore here)
(Update: they now ship a /r2 version that supports different speeds: https://mikrotik.com/product/s_rj10 )

also ersmal schalten wir dann "host access to custom Networks" AN, dann sollte schon mal der Docker erreichbar sein.

Also irgendwas ist da faul...
Deine Kiste redet immer noch mit dem DHCP Server, trotz statischer Adresse!
Kriegt die Adresse 192.168.1.179, wird traurig und löscht alles wieder :-(
Das ist nicht normal!
Und WLAN pfuscht da auch noch mit rein, das ist doch Chaos pur. Allerdings fehlt mir die kriminelle Phantasie wie man sowas hinbekommt.
Du solltest mal besser runterfahren, alles was "network*" heißt aus der config löschen (auf einem anderen Rechner) und neu booten.
Dann kommt er zwar nicht mir Deinen Wunschwerten hoch, aber sollte wieder ordentlich im LAN funktionieren. Die statische Adresse kann man auch noch später (vorsichtig) reinmachen...

These 90 errors are most likely the result of unwritten buffers due to your unclean shutdown.
UNRAID first writes the data, then the parity. So, if interrupted, it is a good chance, that the data is already correct on disk, just the parity is out of sync.

To check (and fix) this (as @trurl already said):
start a parity check with "write corrections"
wait until it is finished (should show the 90 errors again)
start another parity check without corrections
The result of the latter should be 0, this means the data is correct and the parity is back in sync again.

Avoid unclean shutdowns, they will always kill the parity. If you produce them often, consider to tick the "write corrections" mark in the settings to allow direct corrections in the pass that is always fired up after a restart following an unclean shutdown. This CAN cover real errors, but this is very rare. (use at your own risk)

Sep 15 21:34:46 RENZO kernel: igb 0000:06:00.0 eth1: renamed from eth0

He manually has (re)named eth0 to eth1

Be aware that DNS servers and so on are ONLY taken from eth0's config!

So, it is very likely that you now run without any.

Rename it back (in network rules) and you should be up and running again.
(or delete the network.rules file in the config and reboot)

Dunno, keep in mind that most of those articles do not apply to UNRAID, its hard to tell what is correct and what not.
UNRAID's ZFS is still under development, some features are still missing.

So just keep cool and take what is available. Don't fiddle around too much, you may run into surprising problems.
I did not even know what settings I had (just looked them up, its "overlayfs2", whatever it is good for).
It works, thats good.

have you tried to reboot (with power down) or at least pull out the power cable from the drive (and put it back in again after a few seconds) ?

(and check the cables of course, maybe one of them became loose?)

you need to edit the xml file directly
switch to xml view of the vm, locate the part that belongs to the main lan. copy & paste it and modify the names/values.
After saving the xml and starting the vm the additional lan card(s) will show up in the gui too.
(The same is true for other devices like disks and so on)

Be aware that a syntax error in the xml will keep the vm from starting! So be careful with your edits. Save the orginal beforehand!

what gave you the idea that unraid runs a dns server on 127.0.0.1 ?
There is none, so nobody will answer any queries.
Delete the entry for DNS1 and move up all others, then it should work.

No way to tell, I just says that it is this way.
Thats why I usually make a big circle around this Linux stuff (the other disadvantage is that every distribution has its own idea WHERE a file should be and WHAT it does).
and stay with OSs like Free BSD or so. Here the file locations have not changed within 40 yrs and the included man pages really show what is working and how.

UNRAIDs limit have not much to do because it runs in RAM (can other too), it is just "where did it get it base commands from".

I still dont understand your reference and example. Looking for "monday" is faily simple to be done in every cron I know: the last "* is day of the week. Put a "1" here and you are fixed to mondays (in every locale).
Ok, 1st monday of a month... this can be a bit tricky.
I would be lazy and start a script every monday. At the beginning, I would then build up the environment (cronjobs run under their own and often very limited enviroment), and check if the day of week is <7. If not, exit script, done.
They tell you to do the check within the crontab already, this is a bad idea as I have pointed out. Very hard to debug which variables are available and which are not. Better start an own script, grab everything you need and then check. Especially "PATH" is not normal under cron, so take care which programs you are calling or set your own PATH.

Analysis and Solution:

The SQUID proxy server with a standard installation denies access to the above URL. Therefor UNRAID's test always fails and the configured outgoing proxy is never accepted.
THIS IS A BUG!

Workaround:
modify SQUID.conf
Search for "acl SSL_ports port 443"
Add a line below: "acl SSL_ports port 80"
restart squid
(this will allow http access on port 80 too, it still won't work but now the returned status is 200 instead of 403, UNRAID is happy with this)


1748754824.553 1 192.168.0.170 TCP_TUNNEL/200 342 CONNECT www.msftncsi.com:80 - HIER_DIRECT/192.168.0.4 -
1748754824.555 1 192.168.0.170 TCP_TUNNEL/200 342 CONNECT www.msftncsi.com:80 - HIER_DIRECT/192.168.0.4 -
1748754825.195 1 192.168.0.170 TCP_TUNNEL/200 342 CONNECT www.msftncsi.com:80 - HIER_DIRECT/192.168.0.4 -
1748754825.196 0 192.168.0.170 TCP_TUNNEL/200 342 CONNECT www.msftncsi.com:80 - HIER_DIRECT/192.168.0.4 -
1748754831.881 1 192.168.0.170 TCP_TUNNEL/200 342 CONNECT www.msftncsi.com:80 - HIER_DIRECT/192.168.0.4 -
1748754831.882 0 192.168.0.170 TCP_TUNNEL/200 342 CONNECT www.msftncsi.com:80 - HIER_DIRECT/192.168.0.4 -
1748754834.319 1 192.168.0.170 TCP_TUNNEL/200 342 CONNECT www.msftncsi.com:80 - HIER_DIRECT/192.168.0.4 -
1748754834.321 1 192.168.0.170 TCP_TUNNEL/200 342 CONNECT www.msftncsi.com:80 - HIER_DIRECT/192.168.0.4 -
1748754834.798 1 192.168.0.170 TCP_TUNNEL/200 342 CONNECT www.msftncsi.com:80 - HIER_DIRECT/192.168.0.4 -
1748754834.800 0 192.168.0.170 TCP_TUNNEL/200 342 CONNECT www.msftncsi.com:80 - HIER_DIRECT/192.168.0.4 -

(and yeah, i faked that host too. no need here to do external tests, we keep everything in the family (this silences window's clients too at the same time :-) ))

nein, kann man nicht.
Ich hab den Fehler mit dem falschen Tastaturlayout schon seit 2 Jahren bei LT gemeldet, es interessiert offensichtlich niemanden dort 😞
 
(PS: "slim" kenn ich auch nicht, er meint aber wohl die lokale GUI Konsole. Also Tastatur und Monitor anschliessen, dann UNRAID in den GUI Modus booten und sich vor Ort anmelden)
 
PPS: ich meine mich dunkel erinnern zu können (seit ich das Problem kenne sind meine Passwört seeeehr überschaubar und simpel geworden), das es doch einen Trick gibt:
* GUI Konsole starten
* ALT-CTRL-F2 (oder 3,4 oder 5 drücken). Dann schaltet er wieder um auf eine normale Textkonsole
* NUN GEHT DIE DEUTSCHE Tastatur!!!
* allerdings hilft das ersmal nicht weiter um auf die GUI zu kommen... deshalb:
* Per Shell Passwort ändern oder löschen
* abmelden
* ALT-CTRL-F(weis nicht mehr welche, alle durchprobieren, irgendwann schaltet er wieder um auf die GUI Konsole)
* anmelden mit neuem Passwort
* LAUT FLUCHEN!!!
 
Alternative:
* Stick entnehmen und in einen Windoof Rechner stecken
* in der Datei /config/shadow den root Eintrag ändern
root@F:/boot/config# cat shadow root:$6$Q9NuyANLIwDrof8z$X23PbGvpbfO3w2LxjBCU/oXL/IYVKs10Q7p2l6jOGqw.7O7Od/efnv0tFW5h9Q3W//PDkb.ICNUOMeoqczR.:18943:0:99999:7::: * vom ersten "$" zeichen bis vor den nächsten ":" alles löschen (vorher Kopie der Datei anlegen!)
also sieht es dann so aus:
root@F:/boot/config# cat shadow root::18943:0:99999:7::: (da sind noch einige Zeilen mehr, DIE NICHT ANFASSEN!!!)
* Speichern, Stick wieder in UNRAID und booten...
* User "root", Passwort "" (NIX, LEER, nur RETURN drücken)
* später entweder die Originaldatei zurückkopieren oder besser gleich ein "verträgliches" Passwort neu setzen
 

vielleicht doch erstmal ne diagnostics posten, damit man mal genau sieht, welch Hardware da vergraben ist?
 
Ansonsten, die nächsthäufigste Ursache für Symptome wie Deine sind "minderwertige Kabel". Auch wenn man bei 2,5G sagt, man könne bedenkenlos die alten CAT5.e Kabel weiterverwenden, so gibt es da doch oft ein paar Unverträglichkeiten. Besonders bei alten Kabeln in der Wand wäre ich vorsichtig, die Dosen sind oft recht schlampig (Abschirmung) angeschlossen...