Tibbe

The plugin has stopped showing any information recently. The CLI shows that I do have datasets: $ zfs list NAME USED AVAIL REFER MOUNTPOINT cache 20.0G 879G 120K /mnt/cache cache/appdata 10.5G 879G 10.5G /mnt/cache/appdata cache/domains 96K 879G 96K /mnt/cache/domains cache/system 9.39G 879G 9.39G /mnt/cache/system cache/www 11.9M 879G 11.9M /mnt/cache/www disk1 1.39T 9.39T 104K /mnt/disk1 disk1/data 1.39T 9.39T 1.39T /mnt/disk1/data disk1/isos 96K 9.39T 96K /mnt/disk1/isos vault 1.81T 8.63T 813G /mnt/vault vault/backups 451G 8.63T 451G /mnt/vault/backups vault/gdrive 1.13G 8.63T 413M /mnt/vault/gdrive vault/gphotos 17.1G 8.63T 17.0G /mnt/vault/gphotos vault/lesley 140K 8.63T 140K /mnt/vault/lesley vault/tibbe 284G 8.63T 284G /mnt/vault/tibbe vault/time-machine 290G 8.63T 290G /mnt/vault/time-machine However the plugin shows nothing: I have default settings:

Is there an approach that copies the old parity drive for more safety and to avoid reading all data disks to rebuild parity?

I feel like this should be a very common use case but the documentation around this is very unclear. I currently have 4x 4TB drives, one being used as parity. They are all healthy. I've recently bought 2x 12TB drives that I want to add to the system, replacing the current parity with one of the new drives. I have enough bays in my server so I will eventually end up with 6x drives. How do I add the two new drives to the system?

$upstream_CONTAINERNAME is just an arbitrary name here: you could call it $upstream_whatever. It's just set to the IP and port from the NPM config you filled in for this proxy host.

I managed to get it working using a custom Docker network (called "proxy"). My machine is at 192.168.5.100:

I also get "Unauthorized" but refreshing doesn't help. Accessing qbittorrent through the Unraid webui (i.e. through 192.168.x.x) works.

Have anyone gotten qbittorrent working with Authelia? My other endpoints work fine but qbittorrent seems sad. I found https://github.com/qbittorrent/qBittorrent/issues/6962 but haven't managed to make it work.

I just did a fresh reinstall and it seems like pihole has an issue reaching the upstream DNS servers when updating the blocklist: # cat /etc/resolv.conf nameserver 127.0.0.11 options ndots:0 # pihole -g [✗] DNS resolution is currently unavailable [i] Time until retry: 120^C [i] User-abort detected PIHOLE_DNS_ is correctly set to 8.8.8.8;8.8.4.4 but that doesn't seem to be used here.

I don't know what the problem in the end but switching to a new USB drive and transferring my key there worked.

I had a typo in my above post (but not in my actual command). /config doesn't seem to exist: # ls /config /bin/ls: cannot access '/config': No such file or directory

I will try safemode. There seems to be no /config/disk.cfg? Is it in some other subdirectory? Update: fixed typo. There's no /config/disk.cfg

Unfortunately "Starting diagnostics collection..." never finishes (that's why I uploaded some files manually above). I suspect that perhaps it's trying to make HTTP requests to the server and therefore hangs, just like my web UI connection.

My Unraid server's web UI has become unresponsive. I can still SSH to the machine and a restart has no effect. /var/log/syslog has lots of these: Jan 24 17:42:09 Tower nginx: 2022/01/24 17:42:09 [error] 10604#10604: *6414381 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.5.64, server: , request: "GET /login HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.5.100:9080", referrer: "http://192.168.5.100:9080/login" Trying manually with curl has the same effect (i.e. curl just hangs waiting for the HTTP server response that never comes.) syslog.txt dmesg.txt

I'm trying to copy over an old Dedicated.db and Dedicated.fwl from another server but on server/Docker start those two files get overwritten for some reason.

470.74 because, as you say, the 490 series doesn't support my card.