banterer

So, odd stuff has just happened. I noticed that my deluge docker ui was reporting a lack of disk space. Looked at the main unraid UI, and it said all my devices were missing. No parity disk, nothing. Interface is otherwise responding fine, and my dockers are still working (albeit with disk space issues). Tried rebooting and shutting down from within unraid. Nothing happened. In the end, forced a shutdown, everything came back up except my cache drive (WD m.2 nvme 1TB). It's xfs. Docker is still working despite appdata being set to 'prefer cache', so that seems odd. Unless there's an old copy of it from previous issues (actually, that does make sense, I think). What should I do now?

It lets me set it up fine, but when I connect to the external hostname I get the 400 error. It's definitely hitting Nginx (and that configured external address) as if I change it to homeassistant.local instead of the internal IP of home assistant, I get a different error (unraid isn't resolving .local addresses it seems).

Ok so this worked! It let me create an insecure one, and it's now letting me create https ok and SSL is working too! But... when I set it up for home assistant, I get '400: Bad Request'. This is my setup: I want SSL to Nginx and http to home assistant on port 8123, so this is correct surely? I know it's getting through to Nginx ok, and the url http://10.10.10.10:8123 works fine locally.

Hi all, this looks amazing - exactly what I need. But, new install on unraid 6.11.5 All works fine until I try creating the certificate. All port forwards are set up and firewall rules etc. But I get: `communication with api failed, is npm running` Do I need to install this manually or something? If I look in the logs, I have: [12/18/2022] [3:04:34 PM] [SSL ] › ℹ info Renew Complete `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0 `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0 QueryBuilder#omit is deprecated. This method will be removed in version 3.0 Model#$omit is deprected and will be removed in 3.0. [12/18/2022] [3:10:04 PM] [SSL ] › ℹ info Testing http challenge for sub.mydomain.com Uncaught SyntaxError: Unexpected end of JSON input FROM [services.d] stopping services [services.d] stopping app... [services.d] stopping cert_cleanup... [services.d] stopping nginx... [services.d] stopping statusmonitor... [services.d] stopping logmonitor... [services.d] stopping s6-fdholderd... [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

I seem to have everything back now! The only difference is I have spare SSD as I now have a single XFS SSD as my cache instead of a Btrfs pool of two. Thanks for your help.

BTW, I have now changed my backup settings to give me more time to sort things out. Also from what I've read I will change to XFS.

Also more info, the docker image path is listed as: /mnt/user/system/docker/docker.img 'system' is a 'prefer cache' share, which is completely empty. If I try to create the docker subdirectory I get: root@Tower:/mnt/user/system# mkdir docker mkdir: cannot create directory ‘docker’: Input/output error So I'm thinking recreate the share, add the docker directory, start docker, cross fingers?

Ok so looking at it, I have the CA backups running to backup my appdata (of course I would have set this up!) But, the only 'backup set' available, is today at 3am. So does that mean I would have overwritten the good backup with the bad data?

(I can't even view the docker configs to check where all my data is!)

Why would the scrub be aborting, and how do I restore everything once I've recreated the pool? I can't lose all my docker containers!

tower-diagnostics-20221113-1229.zip

Really need some help here!

Doesn't seem to do anything, it just comes up with this immediately: ```UUID: d3a1b53b-b4c0-40e3-9467-1f7226b8100d Scrub started: Sat Nov 12 18:14:07 2022 Status: aborted Duration: 0:00:00 Total to scrub: 648.26GiB Rate: 0.00B/s Error summary: no errors found```

All dockers (well, Docker won't start). I have a parity but the dockers mainly use the pool devices. What's the 'CA' backup? Might need to cgheck that!

I'm finding contradicting ways to do this, what's the 'correct' way?

Ummm, help?

I've attached my diagnostics. Pre-empting (given some googling) that it might be my disk image is corrupt (seems to be the case commonly, is it for me? I can't make any sense of it), I'm a little panicked at the idea of having to reinstall everything! Really? Isn't it backed up or something? And will I lose anything? Sorry if this sounds curt, just in a panic right now! tower-diagnostics-20221110-2340.zip

Ah ok. I was a new user 6 months ago and it didn't have it then I guess. Haven't upgraded as I heard some had things stop working (not complaining, very common!). Going away next week so don't want to break stuff now I've installed the Dynamix one and it's working. I guess the thing to do when I get back is remove it and upgrade unraid...

I don't have that?...

I want to install Wireguard VPN (server), so have looked at the apps section of unraid to pick a docker install. Choices are: Dynamix WireGuard - says it contains GUI support, but unclear if it's the whole thing? wiregard - deprecated WireGuard-Easy - sounds good but has a worrying warning about running as privileged Any advice as to which one I should pick? Or should I find a different docker image somewhere?!

Ah yes I guess that makes sense. Now I just need to find out why Mover is taking 12 hours (so far) to move <1TB

I have split any directory enabled - settings below. I will set the min space to 100G or something like that, when move has finished and I can stop the array. I still don't understand why a disk full error is being generated though, because surely the min space setting shouldn't matter - if it's X% full, or 100% full, further writes should go to the array according to the help / docs?

The command is: rsync -a /mnt/disks/main/backups/* /mnt/user/backups/ I can't find the minimum free space setting, where is it exactly? Re your point on not adding more data than the cache pool can hold - absolutely. This is just the initial copy, future syncs will be incremental. I'm caught in a situation where none of the cache options 'fit'. If I set it to 'no', it will leave data it's already copied on the cache... so I have to set it to yes! Could do with another option which will move from the cache, but not put any further data onto it....

I have an array with plenty of space on it, and a share called `media` set to `cache: yes`. However, when the cache fills up, my script (using rsync to copy to `/mnt/user/media`) generates a disk full error: No space left on device (28) Yet cache: yes says If there is insufficient space on the Cache disk/pool, then new files and directories are created on the array Why is this?? Do cache rules not work for rsync / bash scripts?

It would be cool if it stored an incremental list of changes made to the emulated disk, so it could just apply those changes (probably none in this case), rather than the however many hours rebuild I'm looking at. But then I guess that might have issues of its own I haven't really thought about hard enough. And maybe being dumb and pulling out the wrong disk is a bit of an, ummm "edge case" anyway