Jump to content

Hiko0

Members
 View Profile  See their activity

  • Posts

    25

  • Joined

  • Last visited

 Content Type 

Posts posted by Hiko0

    [PLUGIN] GPU Statistics

    in Plugin Support

    Posted · Edited by Hiko0

    I have encountered a bug. I don't know if it was introduced in the last update, but for a few weeks, GPU Statistics has shown an empty box in Unraid's dashboard. Clicking the arrow only briefly shows the bars.

     

    CPU is a AMD Ryzen 7 Pro 4750G and I use Safari 17.1 as my browser. It's working in Firefox 121.0.1 but it used to work in Safari before.

     

     

    SCR-20240117-jzek.png

    Using Kopia to backup Unraid shares

    in Lounge

    Posted · Edited by Hiko0

    I managed to get Kopia running via docker (the official one). However, in the template there are no options to mount shares or folders so that I can backup those onto a second Unraid server. Does anyone know the docker variables to mount shares?

     

    Edit: Found the solution myself. Went into the docker configuration and added a path, e.g. to backup comics:

      

    Name: ComicsRoot

Container Path: /shares/ComicsRoot

Host Path: /mnt/user/Comics

     

    This allows the Kopia docker to access the local share in Unraid.

    Erlaubt der neue Linux Kernel stromsparende AMD Server?

    in Deutsch

    Posted · Edited by Hiko0

    On 1/11/2024 at 12:26 PM, Pillendreher said:

     

    grafik.thumb.png.3ea8b50bebd7c770e7a9e0785d5a6da6.png

     

    grafik.thumb.png.da33ae769bbfe39f654dda5ffd3b9b0d.png

     

    Steht nichts besonderes drinnen.

     

    Alter Falter. Es muss ein Formatierungsproblem gewesen sein. Ich hatte nach dem Kommentar von @mgutt direkt nur mit 

      

    amd_pstate=passive

     

    gebootet und es funktionierte nicht. Und dann fing ich an, herum zu probieren. Jetzt, mit allen Bootargumenten in Syslinux config und go-file raus, wie bei Dir, funktioniert es. Kann es daran gelegen haben, dass ich in eine neue Zeile in der Syslinux config begonnen hatte? Naja, egal. Es funktioniert nun und Dein Post ist der erfolgreiche Abschluss einer wochenlangen Odyssee inkl. Bemühen des ASRock-Supports (der übrigens super schnell und gut ist). Danke!

     

    Zeigt Euch Powertop denn mehr als C3 an? Die höheren C-states fehlen bei mir noch, wenngleich nun unter "Frequency stats" sehr viel ausdifferenziertere clock speeds stehen, als zuvor (da waren es nur vier inkl. Idle).

    Erlaubt der neue Linux Kernel stromsparende AMD Server?

    in Deutsch

    Posted · Edited by Hiko0

    On 1/7/2024 at 6:00 PM, Pillendreher said:

     

    Worin äußert sich das denn bei dir? Was zeigt er bei "cpufreq-info" an?

    Egal, was ich eingebe, er lädt trotz des Blacklistings den "acpi-cpufreq" und demnach zeigt er den auch mit "cpufreq-info" an. Den AMD pstate Treiber lädt er entsprechend auch nicht.

    Könntest Du mir mal Screenshots deiner Syslinux cfg und des go-file einstellen? Ich vermute, ich habe die Kommandos trotz mehrmaligem Gegenchecken falsch (Formatierung?) eingegeben.

    [Plugin] CoreFreq

    in Plugin Support

    Posted · Edited by Hiko0

    On 8/9/2022 at 11:54 AM, CyrIng said:

    Indeed blue means capable, and green, enabled.

     

    In your case CPPC is capable but not in function.

    You can enable it in window "Performance Monitoring", item "Collaborative Processor Performance Control"

     

    Remarks:

    CPPC appears to be a firmware implementation, I can't tell what BIOS is going to do when enablement bit is set.

     

    @CyrIng I can't get CPPC to be enabled even though I set it to "Enabled" in the BIOS of my ASRock B550 Taichi. Corefreq shows CPPC as capable (blue). I tried to activate it in Corefreq but it's not possible. I can't change anything in the "Performance Monitoring" window. 

     

    Is there any way for me to force it? I'm really trying hard to force my system to load the AMD_PSTATE driver, however, I think CPPC is the key to this first.

    Erlaubt der neue Linux Kernel stromsparende AMD Server?

    in Deutsch

    Posted · Edited by Hiko0

    @mgutt Wie laufen die Tests mit deinem Testsystem?

     

    Ich bekommen den amd-pstate nicht geladen. Folgende Einstellungen habe ich im BIOS des ASRock B550 Taichi vorgenommen:

     

    PM L1 SS = L1.1

    Global C-state Control = Enabled

    CPPC CTRL = AUTO (bei Enabled kommen EPP Min/Max Range und Perf Limit Min/Max Range Werte, mit denen ich mich nicht auskenne)

     

    In der Syslinux CFG stehen

    Quote

    initcall_blacklist=acpi_cpufreq_init
    amd_pstate=passive

    ich hatte es auch nur mit amd_pstate=passive probiert, bzw. ein anderes command zum blacklisten des acpi-Treibers probiert.

     

    In der go-file steht direkt unterhalb von

    # Start the Management Utility
    /usr/local/sbin/emhttp &

    Quote

    modprobe amd_pstate

     

    Immerhin funktionier "powertop --auto-tune &>/dev/null" so, dass auch die HDD, die am verbauten ASM SATA-Chip hängt, wieder problemlos aus dem Ruhezustand aufwacht.

     

    Powertop zeigt mir leider nur bis C3 an.

     

    Ich komme so im idle aller Platten mit zwei verbauten 980 Pro 1 TB SSDs und vier 14 cm Noctua Lüftern auf ± 30W.

     

    Hat jemand eine Idee, woran es scheitert?

    Erlaubt der neue Linux Kernel stromsparende AMD Server?

    in Deutsch

    Posted

    @mgutt Ich habe mich jetzt auch endlich mal an das Thema Stromsparen gesetzt. Ich habe in die Syslinux Config "amd_pstate=passive" eingefügt und neu gestartet. cpufreq-info zeigt mir

     

    Quote

    cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
    Report errors and bugs to [email protected], please.
    analyzing CPU 0:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 0
      CPUs which need to have their frequency coordinated by software: 0
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:1.36%, 1.70 GHz:1.05%, 1.40 GHz:97.59%  (2368)
    analyzing CPU 1:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 1
      CPUs which need to have their frequency coordinated by software: 1
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:1.67%, 1.70 GHz:1.14%, 1.40 GHz:97.18%  (2344)
    analyzing CPU 2:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 2
      CPUs which need to have their frequency coordinated by software: 2
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:1.24%, 1.70 GHz:1.03%, 1.40 GHz:97.73%  (2206)
    analyzing CPU 3:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 3
      CPUs which need to have their frequency coordinated by software: 3
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:1.76%, 1.70 GHz:1.21%, 1.40 GHz:97.03%  (1992)
    analyzing CPU 4:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 4
      CPUs which need to have their frequency coordinated by software: 4
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:1.22%, 1.70 GHz:0.87%, 1.40 GHz:97.91%  (2133)
    analyzing CPU 5:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 5
      CPUs which need to have their frequency coordinated by software: 5
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:1.28%, 1.70 GHz:1.42%, 1.40 GHz:97.31%  (1927)
    analyzing CPU 6:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 6
      CPUs which need to have their frequency coordinated by software: 6
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:1.27%, 1.70 GHz:1.62%, 1.40 GHz:97.11%  (2078)
    analyzing CPU 7:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 7
      CPUs which need to have their frequency coordinated by software: 7
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:1.26%, 1.70 GHz:0.97%, 1.40 GHz:97.77%  (1976)
    analyzing CPU 8:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 8
      CPUs which need to have their frequency coordinated by software: 8
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:0.90%, 1.70 GHz:1.05%, 1.40 GHz:98.05%  (1602)
    analyzing CPU 9:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 9
      CPUs which need to have their frequency coordinated by software: 9
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:0.70%, 1.70 GHz:1.12%, 1.40 GHz:98.18%  (1306)
    analyzing CPU 10:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 10
      CPUs which need to have their frequency coordinated by software: 10
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:0.81%, 1.70 GHz:0.65%, 1.40 GHz:98.55%  (1221)
    analyzing CPU 11:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 11
      CPUs which need to have their frequency coordinated by software: 11
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:0.90%, 1.70 GHz:0.73%, 1.40 GHz:98.37%  (1161)
    analyzing CPU 12:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 12
      CPUs which need to have their frequency coordinated by software: 12
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:0.82%, 1.70 GHz:0.75%, 1.40 GHz:98.42%  (1566)
    analyzing CPU 13:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 13
      CPUs which need to have their frequency coordinated by software: 13
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:0.93%, 1.70 GHz:0.95%, 1.40 GHz:98.12%  (1697)
    analyzing CPU 14:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 14
      CPUs which need to have their frequency coordinated by software: 14
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:0.81%, 1.70 GHz:0.92%, 1.40 GHz:98.27%  (1527)
    analyzing CPU 15:
      driver: acpi-cpufreq
      CPUs which run at the same hardware frequency: 15
      CPUs which need to have their frequency coordinated by software: 15
      maximum transition latency: 4294.55 ms.
      hardware limits: 1.40 GHz - 4.45 GHz
      available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz
      available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
      current policy: frequency should be within 1.40 GHz and 3.60 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 1.40 GHz (asserted by call to hardware).
      cpufreq stats: 3.60 GHz:1.03%, 1.70 GHz:0.62%, 1.40 GHz:98.35%  (1542)

     

    Ich gehe nicht davon aus, dass ich das Ganze richtig konfiguriert habe, wundere mich vor allem über die 1,40 GHz. Die CPU ist eine 4750G auf nem ASRock B550 Taichi.

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    2 minutes ago, Rysz said:

     

    Are you sure the text in "Network UPS Tools Backend" didn't change? Because this is the (older) stable backend which you've selected - so the correct backend is installed (according to your selection). Maybe you were on the (older) stable backend already - which is why your load value wasn't shown and the backend hasn't changed? The new backend is "nut-2.8.0-x86_64-11master.ssl11" or "nut-2.8.0-x86_64-12master.ssl11".

     

    In any case the backend definitely switches when reinstalling, so worth trying changing again to:

    • default (recent master) => reinstall plugin => test if it works
    • legacy (2.7.4. stable) => reinstall plugin => test if it works

     

    You are right. I just didn't read it right. However, load isn't shown with 2.8.0 or 2.7.4. I will try again with a different USB-Cable. Do I still have to set anything in Unraid's own UPS Settings?

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted

    1 minute ago, Rysz said:

     

    Can you try with the "legacy (2.7.4)" backend - some UPS don't play well with the newer backends. Please note that if you switch backends you need to either restart your system or re-install the plugin. Otherwise the backend change will not be in effect, so worth attempting to change to 2.8.0 or 2.7.4 with this in mind.

     

    Ah, so when I tried switching back to 2.8.0, it couldn't work. I wouldn't like to reboot the system right now. So, in options I choose 2.8.0, then uninstall the plugin and install it again?

    [Plugin] NUT v2 - Network UPS Tools

    in Plugin Support

    Posted · Edited by Hiko0

    I have encountered an issue. I don't know whether it's been a recent reboot or the update from 10-22-2023/10-24-2023, but there's no load shown anymore. Everything was working out of the box with NUT a few days ago. My UPS is an Eaton Ellipse ECO 800 USB DIN.

     

    Any idea, what the problem might be, @Rysz?

     

    EDIT: Reverting back to 2.8.0 didn't help.

    SCR-20231024-nlz.png

    Direktzugriff auf Unterverzeichnis einer SMB Freigabe

    in Deutsch

    Posted

    @frah

    Ich stehe gerade vor dem gleichen Problem. Könntest Du von deiner funktionierenden Lösung noch einmal sagen, wie genau Du das gemacht hast? Ich habe einen share ("paperless") erstellt und einen Ordner "consume" dort reingepackt. Ich habe dann dem Benutzer "brother" die Rechte Read/Write auf dem Share gegeben und die Benutzerdaten auch beim Brother eingegeben. 

     

    Hast Du bei den Berechtigungen bzw. bei den Besitzrechten auf Terminal-Ebene noch etwas verändert? Wie lautet Dein Adresspfad im Brother?

     

    Danke für die Hilfe!

    Cloudflare, Cloudflare-DDNS & NGINX: Error 521

    in Deutsch

    Posted

    @mgutt
    Ich glaube, in deinem Container zum NGINX-Proxy-Server gibt es einen Fehler. Trotz Eingabe des Portes 1443 für 443 und 180 für 80 wird der Wert bei mir nicht übernommen. Im Docker-Tab von Unraid steht unabhängig von der Eingabe bei mir 80 -> 80 und 443 -> 443. Ich habe daher die Ports für die Unraid-Weboberfläche geändert und 80 sowie 443 für NGINX gelassen sowie Deinen Container im bridge-Modus gestartet. Hiermit funktioniert die Portfreigabe der Fritzbox, das Abrufen der SSL-Zertifikate und ich kann die Seite endlich öffnen. Danke für die Anregungen, @alturismo – an der doppelten IP lag es nicht.

    • Like 1

    Cloudflare, Cloudflare-DDNS & NGINX: Error 521

    in Deutsch

    Posted

    Ich wechsle gerade frisch von der Synology rüber, bin also nicht ganz unbedarft, was die Konfiguration von reverse proxys angeht. Was habe ich bisher gemacht?

     

    1. Domain registriert.
    2. Cloudflare-Account eingerichtet und Nameserver beim Domainverwalter entsprechend angepasst.
    3. In Cloudflare-DDNS die API und Domain configuriert, Cloudflare erhält hier auch die passende IP.
    4. A-Record erstellt (DOMAIN.de -> verweist auf IP)
    5. CNAME für Nextcloud-Docker erstellt (CLOUD.DOMAIN.de)
    6. NGINX-Docker erstellt, IPs 180 -> 80 und 1443 -> 443 konfiguriert
    7. In der Fritzbox für den Unraid-Server eine Portfreigabe erstellt (180 -> 80 und 1443 -> 443)

     

    Wenn ich nun via NGINX versuche, einen neuen Host einzutragen (CLOUD.DOMAIN.de) und ein Let's Encrypt Zertifikat zu bekommen, gibt es eine Fehlermeldung. Ich hatte ganz zu Beginn die Ports noch nicht richtig konfiguriert. Da kam ich über DOMAIN.de auf die Unraid-Oberfläche, bekam aber kein Zertifkat. Dann habe ich die Ports (s.o.) angepasst und so auf NGINX verwiesen. Dann ging auch das Zertifikat. 

    Mittlerweile bekomme ich so keine Zertifikate (für andere Test-Subdomains) mehr und bekomme, egal worauf ich zugreifen will, den Cloudflare Error 521 -> Host Error. Browser und Cloudflare funktionieren hier.

     

    Ich weiß aktuell keinen Rat mehr. Es geht nicht. Vielleicht ist es wichtig zu erwähnen, dass ich Pihole mit eigener IP laufen habe (192.168.178.3, Unraid hat die .2). Meine Fritzbox kommt hiermit scheinbar durcheinander und weist immer die .3 aus. Ich kann jedoch manuell auf die .2 zugreifen und auch Plex ist extern mit Portfreigabe 32400 verfügbar.


    Könnte es an dem IP-Mixup von Unraid und Pihole liegen? Ich sehe den Server in der Fritzbox immer nur ein Mal, meist mit der IP von Pihole und nicht der eigentlichen Unraid-IP.

    [Support] ich777 - Application Dockers

    in Docker Containers

    Posted

    I can only offer a mobile screenshot. 

     

    I configured it as a sync and without any additional manual options. It does transfer the files, the mentioned files are on the Synology NAS and on my Unraid server. It‘s a first-time sync, so there are no changes or deletions that would be processed. I guess, it‘s just weird behavior. 

    IMG_1114.jpeg

    [Support] ich777 - Application Dockers

    in Docker Containers

    Posted · Edited by Hiko0

    7 minutes ago, ich777 said:

    Where did you read that?

    The colour red is somethimes wrong but not what it states.

    Thanks for the quick reply. 

     

    That‘s what it‘s been saying for five hours in the information window. However, files are transferred and I don‘t know what files and where are deleted. 

     

    IMG_1113.jpeg

    [Support] ich777 - Application Dockers

    in Docker Containers

    Posted · Edited by Hiko0

    I am just using LuckyBackup to mirror my files from my Synology to my new Unraid-Build. Backing up one share worked like a charm, synchronizing another share that I might fill with new files on the Synology before the migration is complete however, scared me a bit. LuckyBackup via VNC shows "deleting files" in the Information Window for all the files mentioned in the commands output. However, this is the first sync and nothing has been deleted on the source nor the destination. Also, the files mentioned there are both still available on source and destination. 

     

    Is this just a mistakenly shown text caused by VNC? I read about red text in the commands output being a VNC error, too. For my understanding this should read "transferring files:".

×
×
  • Create New...