jeradc
Members
-
Joined
-
Last visited
Solutions
-
jeradc's post in Corrupted Config folder on USB drive..... 2 issues remain after my recovery was marked as the answerI typed a reply in my notes, but never copy/pasted here. I just found them, so for future reference:
Why:
Useful for docker containers like DuckDNS that have fields not list in the Unraid GUI like "Subdomain" and "Token", Plex for the "Plex Claim Token", and NordLynx "Private Key".
How:
Use this docker inspect library to get more details on what's running on the system: https://gist.github.com/efrecon/8ce9c75d518b6eb863f667442d7bc679
Run the following command to get a list of all docker guid's on your system (this is also available in the UI, by toggling "Basic View" on the Docker Tab) docker ps -a
Then, for each container you need the details from, update the GUID appropriately and run the following full command shown below.
Example:
DuckDNS:
docker inspect \ --format "$(curl -s https://gist.githubusercontent.com/efrecon/8ce9c75d518b6eb863f667442d7bc679/raw/run.tpl)" \ 884a92747365
Note: You will need to expose the QbitTorrent Web UI port by adding a port to the container. (reference the "--expose "xxxx/tcp" line from our docker inspect command)
-
jeradc's post in 6.12.6 - ZFS cache pool error "status: One or more devices has experienced an error resulting in data corruption was marked as the answerStopped array, removed drives from cache pool, set pool drive size to (0). rebooted. started array Ran this command "wipefs -af /dev/sdx"
stopped array, created pool, added both devices, started array.
cache came up, but drives were unformatted. Selected the box to format, and unraid then set it up as a BTRFS cache pool by default. I enabled a daily balance and a weekly scrub on this pool. Not sure what best practice is.
Started docker. moved back my AppData directory. Recreated my "Scratch Space" share, and enabled visibility on it. Reinstalled all my docker containers from "Apps -> Previous Apps"
..... and so far, I think I'm back and functional.
This is my 2nd failure on this cache pool in (6) months. First failure this past summer was on a btrfs pool, so when I rebuilt it, I chose ZFS. I guess they both suck. I had no errors for years, before setting it up as a pool for redundancy last year. Wish there was more stability to this system.