Airmaster

Question...if I just reboot the machine, and the disk I was zeroing was empty, could I just rebuild the parity from the other disks? If so, how?

Its writing to two parity drives plus an array drive at the same time. I cannot kill the processes, they won't die.

I may do that if I have no other choices. The thing is it is writing to the two parity drives and the one I am clearing right now.

They won't seem to die. I have identified two dd processes and I tried: kill -9 2818167 kill -9 3051232 They are still running

I cannot stop the array. It just says "Sync filesystems" and it is still zeroing out the disk.

I am trying to shrink the array, and I was using the user scripts plugin to do that (https://forums.unraid.net/topic/48707-additional-scripts-for-userscripts-plugin/?tab=comments#comment-490808). Zero out the array so that the parity is maintained. Spaceinvader has a video about it.

I am running the user script from RobJ to zero out the array. This particular drive is taking too long to clear, about 6 days so far, transferring at 10 mb/s. I have to leave town, so I needed to stop in and complete the last later, maybe after checking out cables. The problem is, I cannot shut down. The array activity still says it is zeroing out the array and updating the other drives and parity. I don't know what to do. I am concerned if I force shutdown (reset or power button), it will destroy all of my data. Any thoughts?

nextcloud.log

Nextcloud was stuck in maintenance mode, so I changed the value to false. I am now getting the message : Nextcloud will be updated to version 28.0.1 I thought that the version would be updated as part of the docker. There is an update button, but it doesn't do much. What should I do to get Nextcloud working again? I did remove and re-add the docker, but same message.

I used the docker instead and it worked great. My conclusion is that this plug-in is buggy.

I am trying to pre-clear on unraid 6.11.5 using the plugin (Unassigned Device Preclear 2022.09.02). I keep getting the a post-read verification fail with "Low memory detected". All of them VMs are stopped and I have 128 GB of RAM with 6% utilization. This has happened twice. Any thoughts on what is wrong? server-diagnostics-20221201-2033.zip

I would like some help with understanding my problem. First, I have things "working" but it bothers me that following the video from Spaceinvader didn't quite work. As I mentioned, I followed the instructions. When I point myself to the subdomain, I get the nginx default page. Somehow it isn't seeing the subdomain redirection. I followed some other instructions, and they mentioned that I can create a file in appdate/letsencrypt/nginx/site-confs directory, and I did so with the name nextcloud. I can't seem to get it to properly work using the same method with sonarr, as I get a bad gateway message. So, the questions I have are: 1. Why does it not work with proxy-confs (note that I tried to use port 444, and also the IP in proxy_pass, no difference). 2. What is the secret sauce to get sonarr working the same way as I got nextcloud working, or to properly get it to work in proxy-confs Hopefully this wasn't answered before, as I did search and read quite a few posts. File: appdata/letsencrypt/nginx/site-confs/nextcloud server { listen 443 ssl; server_name nextcloud.domainname.org; root /config/www; index index.html index.htm index.php; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass https://10.99.2.10:444/; proxy_max_temp_file_size 2048m; include /config/nginx/proxy.conf; } } File: appdate/letsencrypt/nginx/proxy-confs/nextcloud.subdomain.conf server { listen 443 ssl; listen [::]:443 ssl; server_name nextcloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_nextcloud nextcloud; proxy_max_temp_file_size 2048m; proxy_pass https://$upstream_nextcloud:443; } }