mgutt

Of course. Finally you could create the output of any OS. Maybe we then see a main difference between those and Unraid.

There is a chance. Log the output of lspci as for example: lspci -vv >/mnt/user/lspci_unraid.txt Do the same with truenas. Then upload the files and we compare which pcie devices / bridges have aspm enabled and active. We then could try to set aspm through a script. Several people posted a this solution in this thread with other hardware setups.

Maybe your problem is the Realtek 2.5Gb Ethernet Controller. Not sure how the current state is regarding the realtek driver and low power states. I checked a bigger photo of your board and maybe it helps to disable the aura chip (led controller, check the bios) as well.

Did you try while docker service is disabled? If you can verify that powertop is able to display them, you could then try to stop one container after another to find the "bad" ones. For example java based applications are really bad for packages states as of my experience.

Throw the error lines into an ai chat. I'd say it's broken. Not sure what to try next. Did you probably set appdata to use both, array and cache? Maybe something got corrupt while moving files.

Strange, should work. Key is set the same? (Name is irrelevant, it's only a description of the var) Usually the logs changes while an upgrade to the following lines: 2025-03-23 11:02:38+01:00 [Note] [Entrypoint]: Starting mariadb-upgrade The --upgrade-system-tables option was used, user tables won't be touched. Major version upgrade detected from 11.6.2-MariaDB to 11.7.2-MariaDB. Check required! Phase 1/8: Checking and upgrading mysql database Processing databases mysql mysql.column_stats OK mysql.columns_priv OK mysql.db OK mysql.event OK mysql.func OK mysql.global_priv OK mysql.gtid_slave_pos OK mysql.help_category OK mysql.help_keyword OK mysql.help_relation OK mysql.help_topic OK mysql.index_stats OK mysql.innodb_index_stats OK mysql.innodb_table_stats OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.proxies_priv OK mysql.roles_mapping OK mysql.servers OK mysql.table_stats OK mysql.tables_priv OK mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.transaction_registry OK Phase 2/8: Installing used storage engines... Skipped Phase 3/8: Running 'mysql_fix_privilege_tables' Phase 4/8: Fixing views... Skipped Phase 5/8: Fixing table and database names ... Skipped Phase 6/8: Checking and upgrading tables... Skipped Phase 7/8: uninstalling plugins Phase 8/8: Running 'FLUSH PRIVILEGES' OK 2025-03-23 11:02:49+01:00 [Note] [Entrypoint]: Finished mariadb-upgrade And after (so the variable can be used permanently): 2025-04-01 04:01:23+02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.7.2+maria~ubu2404 started. 2025-04-01 04:01:24+02:00 [Note] [Entrypoint]: MariaDB upgrade not required Documentation: https://hub.docker.com/_/mariadb

A comment regarding this: Never use auto update in combination with :latest containers. It's a guarantee for incidents. At least you should limit it to a major version like :10 so you won't hit the most alpha release of an upgrade which often contains bugs. That's the reason why I'm still not using Unraid 7 😉

Delete the container. Then check for orphaned containers. Delete them, too. Finally re-add the container through "add container" and select the container's template from the dropdown.

Do you have this variable? If not, create it:

And at which step do you get the error? For me it sounds like you don't edit the container, instead you try to add the same container, which obviously is not possible.

Do you still have this error message? The I would say stop/start the array to force stopping all containers.

Enable advanced view. I think there will be a list of unused containers which use the same image. Delete them first.

Bei fehlerfreier Hardware spielt die Menge überhaupt keine Rolle. rsync ermittelt zB die Liste der Dateien und gleich erst mal nur Dateidatum / Größe ab und kopiert dann eine Datei nach der anderen und das auch immer nur blockweise (ich meine 128 kbyte pro Block). Natürlich kann eine instabile Netzwerkverbindung unerwartete Ergebnisse auslösen, aber deswegen sollte niemals ein Server abstürzen.

Im syslog notifies Skript gibt es diese Zeile: /usr/local/emhttp/webGui/scripts/notify -i "alert" -s "syslog $(echo "$errors" | grep -ioP "($words)" | tr '[:upper:]' '[:lower:]' | sort -u | xargs)" -d "${errors:1}" Das was nach dem "-s" kommt ist der Betreff der E-Mail. Wie man sieht gebe ich da das Wort aus, was den Treffer aus unserer Liste erzeugt hat: # words that should cause a notification words="corrupt|error|fail|tainted" Denkbar wäre nun, dass du die geloggte Fehlermeldung änderst. Statt: logger -t Devices "Error: $path ($type) uses $usage of $size and only $free ($percent) are left!" Machst du es so: logger -t Devices "DevErr: $path ($type) uses $usage of $size and only $free ($percent) are left!" Und im Notify Script ergänzt du das wort: words="corrupt|error|fail|tainted|deverr" Statt "deverr" kannst du natürlich alles mögliche nehmen zB auch dein "Speicherwarnung" oder was auch immer.

Das halte ich für ziemlich Quatsch. Kein USB Stick geht von ein paar Bytes an Logs kaputt. Und ohne Logs stehst du halt dumm da, wie du siehst. Also zumindest bis dein Problem behoben ist, solltest du die Logs permanent sichern. Standardmäßig informiert Unraid nicht über Fehler, die im Syslog gespeichert werden. Daher meine Empfehlung mit dem anderen Skript. Viele Fehler stehen auch nicht im direkten zeitlichen Zusammenhang zum Freeze, sondern tauchen schon deutlich früher in den Logs auf (wenn noch Netzwerk besteht). Wie kannst du wissen, dass die CPU verrückt spielt, wenn du den Server nicht mehr erreichen kannst? Jedenfalls ist ein Freeze nicht normal. Ohne Logs zu prüfen, gingen folgende Schritte: - Memory Test - Array/Pool in Wartungsmodus und alle Dateisystem aller Datenträger prüfen / reparieren lassen - Prüfen, ob das Skript den Freeze auch beim lokalen Kopieren zB zwischen Array und Pool auslösen kann oder es immer nur passiert, wenn es nach extern geht

Wie hast du verifiziert, dass es einen Freeze gibt? Hast du am Server Tastatur und Monitor und reagiert er dort dann auch nicht mehr auf Eingaben? Du solltest auch davon absehen das Skript im Vordergrund im Browser zu starten. Dein Browser unterbricht irgendwann die Verbindung und das Skript stoppt dann, während der rsync gerne im Hintergrund weiterläuft. Das kann zur mehrfachen parallelen Ausführung führen. Das User Scripts Plugin ist dahingehend schlecht umgesetzt. Also wenn im Hintergrund ausführen oder per Cron. Mit "aktuell" meinst du nach dem Freeze? Das wäre nutzlos. Auf dem Stick befindet sich evtl noch syslog_previous. Das wäre interessanter Das Skript spielt dabei überhaupt keine Rolle. Das kopiert einfach nur Dateien. Wenn der Server dabei abschmiert, dann hat das andere Gründe. Ich kann dir noch das Skript empfehlen, um dich per E-Mail über Fehler zu informieren (vorausgesetzt du hast E-Mail-Benachrichtigung in Unraid aktiviert): Der Vorteil daran ist, dass das regelmäßig per Cron aufgerufen wird und sollte der Server tatsächlich nicht eingefroren sein und noch Netzwerk haben, würdest du zumindest von typischen Fehlern erfahren.

I already tested this. No problem so far as those QVO SSDs have a low power consumption and in addition the default airflow keeps them already cool enough. But I repeat the test next week as then 6 additional SSDs will be connected since the last test. Is there a specific reason why the Auto Fan plugin does not use the CPU temps? I would like to use all temp sensors.

After disable and enable the first sensor it works as expected again. Settings: I would say the plugin does not recognize hot swapped disks?!

The Auto Fan Control plugin does not recognize the correct maximum temperature?! EDIT: Ok, this is really bad:

Das kommt an den WiFi Slot.

Bei Mindfactory sollte man nur noch inkl Käuferschutz bestellen: https://m.winfuture.de/news/149728

The primary reason to outsource container components is less maintaining. In addition the user can decide which component he uses (in case of a database mariadb, PostgreSQL, etc). I don't think the devs really think about the amount of containers you are using to use their application. And the efficiency does not really suffer as databases are optimized on multi-threading. This means they already create as many processes/caches depending on the amount of databases and queries. Of course there will be more main processes, but I don't think they cause measurable more cpu load compared to a single main process. And i you ever face a problem as described in my last post (I already did twice), you have a much better ways in solving issues, monitoring performance and doing custom mariadb configurations. An example: After having 5 applications using the same database. Which of them causes high ram usage? Which of them causes high cpu usage? Which of them cause reaching the thread pool limit (has much more queries compared to others)? Which of them use how much storage space? And talking about restoring backups. You need to backup each database with sql commands or you are not able to roll-back a single application. I only need to copy the directory of the applications database, which is backed up by the usual backup routine. So yeah, there are maybe a handful more backgrounds processes, but efficiency can mean many things.

I recommended to run each database in its own container. By that you can fully control the used version (maybe one of your applications does not support an mariadb update in the future), you are able to roll-back per database (maybe one of your application updates got broken and you need to roll-back your appdata backup), ram and cpu usage can be monitored on database/application basis, you have multiple logs per database, more parallel threads/performance, etc.

Did you use a Windows editor? Probably wrong new lines.

In the meantime I prefer as script, which gets execute by the users scripts plugin on array start. By that the server is not dead on every reboot if the go file contains a mistake (for example you can boot in safe mode without any plugins and it will start).