Vvei_61

Thanks, that's exactly the answer I was hoping for. Good to know that Vault backs up the active Unraid configuration when using Internal Boot. Thanks for clarifying! Frank

Hi, I have a question regarding the Flash/Unraid configuration backup. My Unraid installation uses Internal Boot, so Unraid boots from an internal drive. The USB flash drive is only used for the license/GUID identification. How does Vault handle the Flash Backup in this configuration? Does it back up the actual Unraid configuration from the internal boot device, or does the Flash Backup specifically back up the physical USB device? My main concern is disaster recovery: I want to make sure the relevant Unraid configuration is backed up, not just the USB device containing the license identification. Thanks, Frank

Possible bug with User Scripts after reboot Hi hernandito, I think I found a bug in Quick Favorites when launching scripts from the CA User Scripts plugin. After an Unraid reboot, Quick Favorites cannot launch a User Script that has not yet been executed by CA User Scripts since that reboot. Steps to reproduce: 1. Reboot Unraid. 2. Add a User Script to Quick Favorites that is NOT configured to run at "At Startup of Array". 3. Try to run it from Quick Favorites. 4. Quick Favorites tries to execute: /tmp/user.scripts/tmpScripts/SCRIPT_NAME/script 5. The script does not exist there yet, so execution fails with: No such file or directory 6. Run the same script once manually from CA User Scripts. 7. CA User Scripts now creates the script under /tmp/user.scripts/tmpScripts/. 8. From this point on, launching it from Quick Favorites works correctly until the next reboot. I tested this with several scripts. Scripts configured as "At Startup of Array" work immediately after boot because their entries in /tmp/user.scripts/tmpScripts/ are created automatically during startup. I also noticed another related issue: When using "Run Script (Background)", Quick Favorites can display: Now starting the script in the background even though the script does not exist in tmpScripts and therefore is not actually started. It looks like Quick Favorites relies on the temporary copy created by CA User Scripts. Could Quick Favorites perhaps check/create the temporary script first, or launch the User Script from its persistent location instead? Thanks for the plugin! Frank

Hi Robin, I seem to be seeing the container stop issue that has already been reported here a few times. In my case it occasionally happens with my BOINC container: Stopping Boinc... Error while stopping container 'Boinc'! Code: - trying 'docker stop' method That seemed to work. The backup itself completes successfully afterwards, verification is successful and the container starts again. I was curious why this happens and did some digging. A normal manual stop of the container works fine: time docker stop Boinc Boinc real 0m7.176s My Unraid Docker timeout is set to 90 seconds: DOCKER_TIMEOUT="90" I then had a look at what Appdata Backup is doing. It first calls: $dockerClient->stopContainer($container['Name']); In Unraid's DockerClient.php this uses the configured DOCKER_TIMEOUT, so in my case it calls the Docker API with a 90 second timeout. What I found interesting is that getDockerJSON() communicates with /var/run/docker.sock using stream_socket_client(). PHP on my system reports: default_socket_timeout = 60 In the Appdata Backup log there are about 64 seconds between the initial stop attempt and the fallback message. After that, Appdata Backup uses: docker stop Boinc -t 30 and that works. So I was wondering if this could be related to the PHP socket timing out after 60 seconds while DockerClient is actually waiting for a Docker stop timeout of up to 90 seconds. I don't know if this is the actual cause, but the 60/90 second difference and the timing in the log looked interesting, so I thought I'd mention it. Thanks! Frank

Looking at the top screenshot, your settings actually look correct already - Primary = Cache, Secondary = Array, Move action = Cache → Array. Did you start the mover manually? It won't run automatically unless scheduled. And did you get any error message when you ran it? Frank

You need both storages set: Primary = Cache, Secondary = Array, and Move action = Cache → Array. With Secondary set to "none" the mover has nowhere to send the files. Make sure to do this on all shares that use the failing cache drive, then run the mover. Frank

The Unraid 7.3 correlation is interesting and worth keeping an eye on. But Unrecovered Read Errors in the SMART log are written by the drive itself, not by Unraid. Software can't generate those entries. For moving data off the cache: yes, editing the share settings is the easiest way. Set the Use Cache option to "No" or "Prefer Array" on your shares, then run the mover. Everything will transfer to the array automatically.

Your drive is failing. The self-test passing doesn't mean it's healthy – it only checks if the drive responds, not whether all sectors are readable. Look at the SMART error log: 399+ Unrecovered Read Errors, all pointing to the same LBA range. That's permanent bad sectors. Back up your data now, this can fail completely without any further warning. Frank

Ich denke mal ich bleibe bei den Stick. Mit TPM ist es nicht mehr so einfach auf einen anderen Server umzuziehen. Für mich wäre der Königsweg vom Laufwerk zu booten und den Stick nur als Lizensgeber zu nehmen. Vielleicht kommt ja sowas mal. Glück Auf Frank

Das hat schon Mal wunderbar geklappt. Vielen Dank Frank

Kann ich bei einer kompletten Neuinstallation mit dem USB Creator meinen Stick nehmen mit dem ich zur Zeit Unraid boote? Frank

Moin, bis vor kurzen hatte ich lokal vom Rechner immer eine sichere Verbindung auf meinen Unraid Server. jetzt ist die Verbindung nicht mehr sicher. Wenn ich mich über unraid.net einloggen will bekomme ich die Meldung: Warning: This server is not verified by Unraid Wie verifiziere ich meinen Server jetzt wieder? Frank

Da habe ich vor Kurzen schon mal was gelesen. Ich meine du musst die automatische Verlängerung für Updates deaktivieren. Bei mir habe ich das so und mir wird das Update das Update von Unleashed auf Lifetime angeboten. Glück Auf aus dem Ruhrgebiet Frank

Hallo, ja danke Dir. 5 Minuten kommt wohl gut hin. Mich hat dieses "update_services: queue new job 1, wait for 20s" etwas irritiert. Glück Auf aus dem Ruhrgebiet Frank

Hallo, beim Booten bleibt Unraid ztw. lange an einer Stelle stehen. update_services: no queued job present update_services: queue new job 1, wait for 20s Beim googeln haben ich etwas gefunden was sich auf Wlan bezieht. Wlan im Bios ab oder anschalten zeigt aber das gleiche Verhalten. Kann man da was dran ändern? Ich benutze Unraid Version 7.2.2 Gruß Frank