DrMor

YES! That solved it. So simple. Thank you so much!

I'm using v6.12.15 and I held off on updating to v7 for now. Before taking the plunge, I want to verify something -- https://docs.unraid.net/unraid-os/release-notes/7.0.0/#add-support-for-overlay2-storage-driver What exactly does it mean when it says "Docker data-root", is it the location of the vdisk? Currently, my vdisk location is "/mnt/user/system/docker/docker.img" and my default appdata storage location is "/mnt/user/appdata/". where both "system" and "appdata" are in a pool of 4x1TB (2x SATA SSD and 2x NVME) running a ZFS pool with a 1 drive redundancy (so 3TB available space). If I update to v7 will I need to go through the upgrade to overlay2? Because as I understand it, I'll then need to reinstall all my dockers, and I have about 50, I'm not thrilled about that idea, if that's really what's needed. If it is needed, is there some plan to make this transition more painless with a future version? If so, I'll wait more, I have absolutely no problems with v6.12.15 other than FOMO for the latest and greatest... 🙂

Yeah, I don't really understand why. It's a no-no because it breaks the VM, but why exactly I have no idea. If anyone can explain that'll be great.

I didn't realize it was a big no-no, and from my Windows 10 Pro VM I went into "Add/Remove Windows Features" and ticked ON the Hyper-V feature. Now the Windows VM does not boot. I tried changing the order of the boot and booting from the ISO and I don't see any way to get into Safe Mode. None of the recovery options are working. Going into the recovery console DOS mode doesn't help me as the DSIM commands won't let me remove the Hyper-V component now. I really don't want to re-install the Windows VM unless I absolutely must... I also tried just disabling the Hyper-V from the VM settings, thinking maybe without it it will work, didn't help as well... Is there a simple solution for my problem?

I'm trying to change the port, currently my port 8080 is taken up by something I can't change. In "webhookd.env" I wrote: WHD_LISTEN_ADDR=:8077 I even manually changed rc.webhookd script in /etc/rc.d folder, changed the port there to 8077 and yet still when I do rc.webhookd start it still tries to access the 8080 port. Any solution for that? root@Tower:/etc/rc.d# ./rc.webhookd start Starting webhookd ... Loaded environment variables from /mnt/user/appdata/webhookd/webhookd.env: time=2025-01-23T15:30:31.280+02:00 level=INFO msg="server started" addr=:8080 time=2025-01-23T15:30:31.280+02:00 level=ERROR msg="unable to start the server" addr=:8080 err="listen tcp :8080: bind: address already in use" Error! and: root@Tower:/mnt/cache/appdata/webhookd# cat webhookd.env WHD_LISTEN_ADDR=:8077

For anyone looking to do the same, I solved it. startup.sh needs to be: #!/bin/sh # Install necessary Python packages pip install PyPDF2 openai # Default command if none is provided if [ -z "$1" ]; then set -- "/usr/local/bin/paperless_cmd.sh" fi # Execute the original entry point script with provided arguments exec /sbin/docker-entrypoint.sh "$@" and "Extra Parameters" is: --entrypoint /usr/src/paperless/scripts/startup.sh Important to not forget "chmod +x startup.sh" and the proper path allocation in unraid, in my case from "/mnt/cache/appdata/paperless-ngx/scripts/" to "/usr/src/paperless/scripts"

Replying to myself here for a minute, I made some progress but still no success - I wrote - --entrypoint /usr/src/paperless/scripts/startup.sh in the "Extra Parameters" And startup.sh is #!/bin/sh pip install PyPDF2 openai /usr/sbin/docker-entrypoint.sh But /usr/sbin/docker-entrypoint.sh is probably not the right entrypoint, or I'm missing something obvious here, because the docker doesn't load. Any assistance will be highly appreciated. I get the error: /usr/sbin/docker-entrypoint.sh: line 162: $1: unbound variable I then modified startup.sh to be: #!/bin/sh pip install PyPDF2 openai /usr/sbin/docker-entrypoint.sh "$@" And now I don't see any issues in the log, it just stops and doesn't continue. The log now ends with: Installing collected packages: PyPDF2, pydantic-core, distro, annotated-types, pydantic, openai Successfully installed PyPDF2-3.0.1 annotated-types-0.7.0 distro-1.9.0 openai-1.35.10 pydantic-2.8.2 pydantic-core-2.20.1 Paperless-ngx docker container starting... Mapping UID and GID for paperless:paperless to 99:100 Creating directory scratch directory /tmp/paperless Adjusting permissions of paperless files. This may take a while. Waiting for Redis... Connected to Redis broker. Apply database migrations... Operations to perform: Apply all migrations: account, admin, auditlog, auth, authtoken, contenttypes, django_celery_results, documents, guardian, paperless, paperless_mail, sessions, socialaccount Running migrations: No migrations to apply. Running Django checks System check identified no issues (0 silenced).

I'm using paperless-ngx docker, I need to install a few more pip packages for a post processing script I'm creating (Using ChatGPT to get me the costs in bills and receipts and add it as a field to each document). I tried to write - -it paperless-ngx sh -c 'pip install PyPDF2 openai' In the Extra Parameters field, and it failed so badly, it messed up the installation, I had to reinstall the docker... (and re-set all the parameters and variables, a big headache). What should be the trick to do that? What am I missing?

That was silly, sorry to trouble you. I was super skeptical but did it anyway, swapped between the cables and now both drives are recognized. So maybe one of them just wasn't plugged properly or something. Everything is working now, thanks!

Attached, thanks! And now that I'm looking into the logs more carefully, I see in the syslog the line: "ata10.00: disable device" After it's getting some errors in the syslog. I see "failed to enable AA (error_mask=0x4)". tower-diagnostics-20240618-1917.zip

I purchased this one: https://www.aliexpress.com/item/1005005225588036.html?spm=a2g0o.order_list.order_list_main.41.44d01802h5K7Su Since I saw that ADMedia chip is being recommended, and it's not PCIe x1 like some other models. I connected to it 2 identical WD 14TB 3.5" drives. (and the adapter itself is sitting in a x16 slot in the motherboard). When I boot the PC there's a quick popup before the BIOS logo that shows that both drives were detected. However, in Unraid I only get one of them detected. I'm turning one of them into parity, that will take like 24 hours to complete and I started running it, I'll start playing around with the system when it'll finish. Anything I need to do in Unraid to enable this adapter? It should be an ok adapter, right?