DenisDenise

I think I've found a new, cheaper and better solution. It allows you to pop the keyfile into a B2 backblaze bucket. Practically free judging on file size and egress. This is what I use in my "go" file. #!/usr/bin/env bash set -euo pipefail B2_KEY_ID="xxxxxxxx" B2_APP_KEY="xxxxxxx" BUCKET="xxxxxxxx" OBJECT="keyfile.txt" DEST="/root/keyfile" # Authorize json=$(curl -sSf -u "${B2_KEY_ID}:${B2_APP_KEY}" \ https://api.backblazeb2.com/b2api/v2/b2_authorize_account) AUTH_TOKEN=$(jq -r '.authorizationToken' <<<"$json") DL_HOST=$(jq -r '.downloadUrl' <<<"$json") # Sanity-check if [[ -z $AUTH_TOKEN || -z $DL_HOST || $AUTH_TOKEN == "null" ]]; then echo "Authorization failed — response was:" >&2 echo "$json" >&2 exit 1 fi # Download the private object wget --header="Authorization: ${AUTH_TOKEN}" \ "${DL_HOST}/file/${BUCKET}/${OBJECT}" \ -O "${DEST}" chmod 600 "${DEST}" echo "Keyfile saved to ${DEST}"

Haven't got around installing it yet but a big ty @ich777 for your reactivity ! Satisfactory dedicated servers barely announced & you already on it TY !

Can confirm, it disabled one of my disks today. Reverted back to 6.8.3 and rebuilding parity now. Hopefully this will be fixed pretty soon, I really needed those multiple pools

Thanks. Quick question, is this more of a "technical" error or is there an actual chance of data loss?

Ty for the answer, is this to do with the 6.9 update? If so I'll probably just roll back, my unraid server is a good 10h drive away and to switch the ports would be a pain.

Hello all, Today I saw on my server in the /Main tab 896 errors on one of my hard drives. I narrowed down these errors to 01h30 on the 03/03/2021. 1h30 of the first Wednesday of the month is when I run my monthly parity check, so it was during the start of the parity check that the errors popped up. The errors concern disk 1. In the logs this repeats multiple times : The device is relatively new, less than a year old. It's a 8TB Seagate Ironwolf drive. I set an extended SMART test to run, seems to be stuck at 10% for the last 2h or so. I attached the logs to this post. Any help is appreciated, Regards, George. tower-diagnostics-20210304-1325.zip

Just to rebound off this @SpaceInvaderOne, I did this multiple times and with 0 doubt renamed the disk (as you do in your video tutorial) but it still shows up in the way the previous person showed. It somehow returns to this screen even though I name the disk "Big Sur". Using method 2 btw for install (not sure what difference it makes). At the end of the installation process, it retakes the correct name though

I'm having issues setting the "openldap" container up. Firstly the certificate issues (shared with letsencrypt), but that's sorted. Main issue now is slapd not starting 5fd381ba daemon: listen(ldap://XXXXX:389, 5) failed errno=98 (Address already in use) Seems to be related to this issue : https://github.com/osixia/docker-openldap/issues/252 This is driving me crazy EDIT : Resolved by removing HOSTNAME variable from template Also, for others wanting to set this up, you can run into certificate issues where the container says to share volumes between LETSENCRYPT and OPENLDAP. It's a pain, easy fix is : set the LDAP SSL Certificate Variable to : /mnt/user/appdata/swag/etc/letsencrypt/ Then the 3 above variables need setting to : live/DOMAIN.com/cert.pem live/DOMAIN.com/privkey.pem live/DOMAIN.com/fullchain.pem

I'm running 6.6.7 and it seems the syslog feature is not available with your plugin, but also not available in the Settings tab (available as of 6.7). Could do with an easy way of tailing syslog but can't seem to be able to until I either upgrade to 6.7 or find some other solution