eav86

hmm nothing has been changed since a year. gonna see if it works if i remove one disc since its basicly still unused.

Hello Guys, since 2 days my parity drive has swapped to "disabled" status. so i read the forum and it could be a broken hdd or controller. so i swapped the drive yesterday with a WD Red which is 100% fine. an this morning after the parity rebuild was done for 12 hours. i get a message again. with the new HDD. i changed the sata port. changed nothing. then i set as the drive for parity 2 instead of parity 1 and it stared but failed with disabled again. Worked fine for 1 year. the update from unraid 6.12.6 worked fine for weeks too. So i'm out of ideas. Diagnostics included. happy for help knas-diagnostics-20240101-1155.zip

Sadly i got the same issue as kilobit, however i created the files beforehand and everything thats. but got the same log with "tomcat spawned, exited" etc. i thought the H2 database was automaticly installed and need no further config. or did i miss something there ?

Hello guys, i'm running unraid on my Dell T20 and i had a old i7 4770k after upgrade to a new pc. So i installed it and all fine. However i'm wondering the CPU has 4 Cores and 8 Threads. On the cpu page i the cpu gets deteced and it shows all 4 cores. However where can i see if it uses threads. and can the threads be added to a VM instead of a cpu core ? or does is basicly just accept and work with the cores ?

Still looking for help with the issue have tried basicly everything but changing the port. but the container still instantly switches to "stopped" after it get started.

Hi guys, i got an issue with my paperless-ng container. After update the container semed to be corrupted. so i had to completly clean my docker.img file since it got damaged. Now i reinstalled redis docker and paperless. however when i start the "paperless"-Docker it instantly stops again. in the systemlogs i only find this as an error: "Mar 10 09:57:41 Tower nginx: 2021/03/10 09:57:41 [error] 3603#3603: *4528 connect() to unix:/var/tmp/paperless-ng.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.2.116, server: , request: "GET /dockerterminal/paperless-ng/ws HTTP/1.1", upstream: "http://unix:/var/tmp/paperless-ng.sock:/ws", host: "tower"" 192.168.2.116 is my local pc from where i got the interface open. edit. Also tried with removing the app data from the old one - got it backup through. But didn't change a thing. Did i have to do anything in redis before the container could work ? been i while since i set it up. Any idea what the issue could be ? and if ya need anythign else to help just say so.