Joshwaaa

Thank you! Much appreciated!

I found that link by going here: https://docs.unraid.net/legacy/FAQ/replacing-a-data-drive/ but it seems I can't use that procedure because my drive will be bigger than the parity.

When I first got into unraid a few years back I bought a used HPE gen10 microserver that came with two 4TB drives that were used. I haven't had any problems but I wanted to get new and larger drives as my data is growing. Is there a guide or a step-by-step to do this on version 6.12.4? I tried to find it in the documentation but it's going to a dead link and I'm really not sure I was in the right place. Here's where I looked: https://docs.unraid.net/legacy/FAQ/replacing-a-data-drive/parity-swap-procedure.md/ Can someone direct me to the right procedure or copy and paste it here so I don't screw it up? Thanks in advance!

If you find yourself in this situation mine did work after updating the bios.

@steve1977Yeah I'm on a Lenovo p520 Xeon 3.70GHz W-2145. I threw in a windows nmve today and updated the bios that way to an August release of this year. I am going to uplug my array, use some old hdd, and try out a trial usb with 6.12.5 on it tonight.

@abhi.ko did you ever get this worked out? I luckily had a flash backup of 6.11.5 before I upgraded. I had to wipe my flash and put 6.11.5 back on it and running makebootable. I'm fine but unfortunately stuck for now. Was hoping to upgrade and get zfs going.

What did you rename it? I just upgraded from 6.11.5 to 6.12.4 and it's been rebooting for 1250 seconds.

I've been looking into this server. How is the power usage?

Did you happen to find this when trying to create a new proxy host? I have the same issue.

There's a forum abou this but I think it was in the wrong place. I was searching for it and stumbled on it. https://forums.unraid.net/topic/142123-scrolling-out-of-memory-log-errors/ . Regardless, i'm having similar issues. Any idea of the cause and any solution? Basically this on loop. 2023/07/23 20:28:00 [error] 2916#2916: *1201991 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" 2023/07/23 20:28:00 [error] 2916#2916: MEMSTORE:00: can't create shared message for channel /devices 2023/07/23 20:28:01 [crit] 2916#2916: ngx_slab_alloc() failed: no memory 2023/07/23 20:28:01 [error] 2916#2916: shpool alloc failed 2023/07/23 20:28:01 [error] 2916#2916: nchan: Out of shared memory while allocating message of size 7048. Increase nchan_max_reserved_memory. 2023/07/23 20:28:01 [error] 2916#2916: *1202000 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" 2023/07/23 20:28:01 [error] 2916#2916: MEMSTORE:00: can't create shared message for channel /devices 2023/07/23 20:28:02 [crit] 2916#2916: ngx_slab_alloc() failed: no memory 2023/07/23 20:28:02 [error] 2916#2916: shpool alloc failed 2023/07/23 20:28:02 [error] 2916#2916: nchan: Out of shared memory while allocating message of size 7048. Increase nchan_max_reserved_memory. 2023/07/23 20:28:02 [error] 2916#2916: *1202009 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" 2023/07/23 20:28:02 [error] 2916#2916: MEMSTORE:00: can't create shared message for channel /devices 2023/07/23 20:28:03 [crit] 2916#2916: ngx_slab_alloc() failed: no memory 2023/07/23 20:28:03 [error] 2916#2916: shpool alloc failed 2023/07/23 20:28:03 [error] 2916#2916: nchan: Out of shared memory while allocating message of size 7036. Increase nchan_max_reserved_memory. 2023/07/23 20:28:03 [error] 2916#2916: *1202016 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" 2023/07/23 20:28:03 [error] 2916#2916: MEMSTORE:00: can't create shared message for channel /devices 2023/07/23 20:28:04 [crit] 2916#2916: ngx_slab_alloc() failed: no memory 2023/07/23 20:28:04 [error] 2916#2916: shpool alloc failed 2023/07/23 20:28:04 [error] 2916#2916: nchan: Out of shared memory while allocating message of size 7036. Increase nchan_max_reserved_memory. 2023/07/23 20:28:04 [error] 2916#2916: *1202027 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" 2023/07/23 20:28:04 [error] 2916#2916: MEMSTORE:00: can't create shared message for channel /devices 2023/07/23 20:28:05 [crit] 2916#2916: ngx_slab_alloc() failed: no memory 2023/07/23 20:28:05 [error] 2916#2916: shpool alloc failed 2023/07/23 20:28:05 [error] 2916#2916: nchan: Out of shared memory while allocating message of size 7039. Increase nchan_max_reserved_memory. 2023/07/23 20:28:05 [error] 2916#2916: *1202036 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" 2023/07/23 20:28:05 [error] 2916#2916: MEMSTORE:00: can't create shared message for channel /devices 2023/07/23 20:28:06 [crit] 2916#2916: ngx_slab_alloc() failed: no memory 2023/07/23 20:28:06 [error] 2916#2916: shpool alloc failed 2023/07/23 20:28:06 [error] 2916#2916: nchan: Out of shared memory while allocating message of size 7039. Increase nchan_max_reserved_memory. 2023/07/23 20:28:06 [error] 2916#2916: *1202046 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" 2023/07/23 20:28:06 [error] 2916#2916: MEMSTORE:00: can't create shared message for channel /devices 2023/07/23 20:28:07 [crit] 2916#2916: ngx_slab_alloc() failed: no memory 2023/07/23 20:28:07 [error] 2916#2916: shpool alloc failed 2023/07/23 20:28:07 [error] 2916#2916: nchan: Out of shared memory while allocating message of size 7045. Increase nchan_max_reserved_memory.

Same. I don't think you'll get much response here. I'm going to post this in the NPM forum but there's not a lot of action there either.

If anyone comes across this and happens to have the same problem it was a permissions issue. Solution is a folder permission issue I had to chmod thanks to a very nice redditor.

Here is logs pulled from Dozzle. Hopefully these last 3 posts will be enough to see the problem! How do I not have root permission running as the admin? 07/15/2023 6:06:18 AM [app ] [7/15/2023] [6:06:18 AM] [Nginx ] › ℹ info Reloading Nginx 07/15/2023 6:06:23 AM [app ] [7/15/2023] [6:06:23 AM] [SSL ] › ℹ info Requesting Let'sEncrypt certificates for Cert #27: nextcloud.xxxx.com 07/15/2023 6:06:23 AM [app ] [7/15/2023] [6:06:23 AM] [SSL ] › ℹ info Command: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-27" --agree-tos --authenticator webroot --email "[email protected]" --preferred-challenges "dns,http" --domains "nextcloud.xxxx.com" 07/15/2023 6:06:24 AM [app ] [7/15/2023] [6:06:24 AM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/temp/letsencrypt_27.conf 07/15/2023 6:06:24 AM [app ] [7/15/2023] [6:06:24 AM] [Nginx ] › ℹ info Reloading Nginx 07/15/2023 6:06:24 AM [app ] [7/15/2023] [6:06:24 AM] [Express ] › ⚠ warning Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-27" --agree-tos --authenticator webroot --email "xxxx" --preferred-challenges "dns,http" --domains "nextcloud.xxxx.com" 07/15/2023 6:06:24 AM [app ] The following error was encountered: 07/15/2023 6:06:24 AM [app ] [Errno 13] Permission denied: '/var/log/letsencrypt/letsencrypt.log' 07/15/2023 6:06:24 AM [app ] Either run as root, or set --config-dir, --work-dir, and --logs-dir to writeable paths. 07/15/2023 6:06:24 AM [app ] Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-fa6dp8rp/log or re-run Certbot with -v for more details. 07/15/2023 6:19:56 AM [app ] [7/15/2023] [6:19:56 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry... 07/15/2023 6:19:57 AM [app ] [7/15/2023] [6:19:57 AM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation 07/15/2023 6:19:57 AM [app ] The following error was encountered: 07/15/2023 6:19:57 AM [app ] [Errno 13] Permission denied: '/var/log/letsencrypt/letsencrypt.log' 07/15/2023 6:19:57 AM [app ] Either run as root, or set --config-dir, --work-dir, and --logs-dir to writeable paths. 07/15/2023 6:19:57 AM [app ] at ChildProcess.exithandler (node:child_process:402:12) 07/15/2023 6:19:57 AM [app ] at ChildProcess.emit (node:events:513:28) 07/15/2023 6:19:57 AM [app ] at maybeClose (node:internal/child_process:1100:16) 07/15/2023 6:19:57 AM [app ] at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

Here, also, is my conf if it helps. I thought it would be a validation limit but I slept all night and tried in the AM and it gave the same "internal error" # ------------------------------------------------------------ # nextcloud.xxxx.com # ------------------------------------------------------------ server { set $forward_scheme http; set $server "192.168.86.23"; set $port 444; listen 8080; listen [::]:8080; server_name nextcloud.xxxx.com; # Asset Caching include conf.d/include/assets.conf; # Block Exploits include conf.d/include/block-exploits.conf; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; access_log /data/logs/proxy-host-1_access.log proxy; error_log /data/logs/proxy-host-1_error.log warn; location / { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; }

I pulled my domain back to Google from Cloudflare but I can't get my nextcloud going again. Mealie has no problem and was running immediately. NC will not get a certificate and will not do https. With http it doesn't go to a webpage at all. What is the internall error?