KaBo

Since the last update of my paperless-ngx the docker container crashes after starting. Redis conatiner is running, thia is the log: text error warn system array login File "/usr/local/bin/wait-for-redis.py", line 12, in <module> import click ModuleNotFoundError: No module named 'click' s6-rc: warning: unable to start service init-wait-for-redis: command exited 1 Traceback (most recent call last): File "/usr/src/paperless/src/manage.py", line 8, in <module> from django.core.management import execute_from_command_line ModuleNotFoundError: No module named 'django' s6-rc: warning: unable to start service init-migrations: command exited 1 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. Traceback (most recent call last): File "/usr/local/bin/wait-for-redis.py", line 12, in <module> import click ModuleNotFoundError: No module named 'click' s6-rc: warning: unable to start service init-wait-for-redis: command exited 1 Traceback (most recent call last): File "/usr/src/paperless/src/manage.py", line 8, in <module> from django.core.management import execute_from_command_line ModuleNotFoundError: No module named 'django' s6-rc: warning: unable to start service init-migrations: command exited 1 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. Traceback (most recent call last): File "/usr/local/bin/wait-for-redis.py", line 12, in <module> import click ModuleNotFoundError: No module named 'click' Traceback (most recent call last): File "/usr/src/paperless/src/manage.py", line 8, in <module> from django.core.management import execute_from_command_line ModuleNotFoundError: No module named 'django' s6-rc: warning: unable to start service init-wait-for-redis: command exited 1 s6-rc: warning: unable to start service init-migrations: command exited 1 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. Traceback (most recent call last): File "/usr/src/paperless/src/manage.py", line 8, in <module> from django.core.management import execute_from_command_line ModuleNotFoundError: No module named 'django' s6-rc: warning: unable to start service init-migrations: command exited 1 Traceback (most recent call last): File "/usr/local/bin/wait-for-redis.py", line 12, in <module> import click ModuleNotFoundError: No module named 'click' s6-rc: warning: unable to start service init-wait-for-redis: command exited 1 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. [init-migrations] Apply database migrations... [init-start] paperless-ngx docker container starting... [init-start] paperless-ngx docker container starting init as root [env-init] Checking for environment from files [env-init] No *_FILE environment found [init-tesseract-langs] Checking if additional teseract languages needed Installing languages... [init-redis-wait] Waiting for Redis to report ready [init-db-wait] Database is ready [init-user] No UID changes for paperless [init-user] No GID changes for paperless [init-folders] Running with root privileges, adjusting directories and permissions [init-tesseract-langs] Package tesseract-ocr-deu already installed! [init-tesseract-langs] Additional packages installed [init-migrations] Apply database migrations... [init-start] paperless-ngx docker container starting... [init-start] paperless-ngx docker container starting init as root [env-init] Checking for environment from files [env-init] No *_FILE environment found [init-redis-wait] Waiting for Redis to report ready [init-db-wait] Database is ready [init-tesseract-langs] Checking if additional teseract languages needed Installing languages... [init-user] No UID changes for paperless [init-user] No GID changes for paperless [init-folders] Running with root privileges, adjusting directories and permissions [init-migrations] Apply database migrations... [init-tesseract-langs] Package tesseract-ocr-deu already installed! [init-tesseract-langs] Additional packages installed [init-start] paperless-ngx docker container starting... [init-start] paperless-ngx docker container starting init as root [env-init] Checking for environment from files [env-init] No *_FILE environment found [init-tesseract-langs] Checking if additional teseract languages needed [init-db-wait] Database is ready Installing languages... [init-redis-wait] Waiting for Redis to report ready [init-user] No UID changes for paperless [init-user] No GID changes for paperless [init-folders] Running with root privileges, adjusting directories and permissions [init-migrations] Apply database migrations... [init-tesseract-langs] Package tesseract-ocr-deu already installed! [init-tesseract-langs] Additional packages installed ** Press ANY KEY to close this window ** Any idea what goes wrong here?

I also recognized that 3 VMs are broken now: Linux and Windows 11 won't boot anymore 😕 Diagnostics: kunraid-diagnostics-20220708-1736.zip

Thanks a lot @JorgeB! This exacly was it. But three questions remaining: How did you find out? Is the last number in brackets from syslog lines the generation (the higher, the newer?) - and devid 2 has to be the newest? Do I have to do anything else before the next reboot? sdb1 shows a lot of "bad tree block start" and "read error corrected" after reboot. How did this happen and what can I do to avoid it? Any ideas? Kai

Unraid Version: 6.9.2 Hello folcs, I run Unraid for a couple of months now, the server is often down and powred on via wol when needed. Yesterday I recognized that my VMs couldn't start. The reason: they're on ssdcache only and both SSDs are in state "Unmountable: No file system" 😲 Diagnostics: kunraid-diagnostics-20220706-2215.zip Array and Pool: Shares (part): Any hint where to start to get this fixed?

Alles klar, vielen Dank für Eure Hilfe! Ich bin mit XFS im Array gestartet und bisher läuft unraid stabil wie erwartet 🙂 . IMport der VMs aus dem Proxmox backup hat auch funktioniert: [guide] import vm from proxmox backup to unraid

Moving from Proxmox VE to Unraid I only found partial information about migrating virtual machines from Proxmox backup (.vma - file) to unraid. So this is the guide how I did it: I had backups of my virtual machines in *.vma format (uncompressed). If your backup is compressed, you first need to uncompress it to get the vma-file. vma is a special proxmox backup file which has to be extracted too. The easiest way for me was this python project: vma-extractor on Github. I used my working python install in Linux, you'll fin executables for other systems here: python.org Download the vma.py from Github. usage is very simple: vma.py your-proxmox-backup.vma /new/export/directory "directory" will be created by the script, don't create it yourself! ❗ This will perhaps last several hours without output! In the new "directory" you will find several files, the biggest one is your raw image. Copy it to your unraid server and rename it to something.img Create a new VM in unraid web GUI, try to use the same settings as in Proxmox VE. Change "Primary vDisk Locatiion" from "Auto" to "Manual" and insert the path of you img: Start VM and enjoy! I was really surprised, at least my Win 11 VM worked from the start without any changes.

Vielen Dank für Eure Antworten! Mir war vor allem nicht klar, dass ich den SSD Cache Pool auch für VMs und Container nutzen kann. Die Konfiguration sieht dann so aus, das sollte passen, oder? Dann wäre nur noch die Frage nach dem Dateisystem. In Default wird er wohl XFS für die Array Platte und Btrfs für den Pool nehmen, oder? Ich wäre nicht abgeneigt, Btrfs auch fürs Array zu nehmen, wie seht ihr das?

Guten Tag zusammen, nachdem ich mir Proxmox intensiv angeschaut habe, möchte ich mein System nun gerne mir unraid aufsetzen. Das sind die Eckdaten: HPE MicroServer Gen 10 mit Intel(R) Xeon(R) E-2224 CPU @ 3.40GHz und 16GB ECC-RAM 2 x 1 TB Server SSD 2 x 6 TB NAS HDD Ursprünglich war geplant, die beiden SSDs im RAID 1 für VMs und Docker zu nutzen und die 6 TB Platten im RAID 1 für NAS-Daten. Mir ist nach dem Lesen der Doku klar, dass das mit unraid so nicht funktioniert. Meine aktuelle Idee ist: 6 TB HDD1 als Parity 1 TB SSD1 und 6 TB HDD2 als Array disks 1 TB SSD2 als Cache: Nun meine Fragen: Die VMs und Docker-Container sollen auf die SSD, die NAS-Daten auf die HDD, ist das so realisierbar? Wird die Parity Disk dann für SSD und HDD genutzt? Gleicht die Cache SSD den Geschwindigkeitsverlust der Parity disk dann einigermaßen aus? Oder ist das alles totaler Käse und kann viel besser gemacht werden? 🙂 Weitere Platten bekomme ich in das Gehäuse nicht rein. Ich freue mich auf Eure Anregungen! Viele Grüße Kai