tjb_altf4

I've managed to solve my wallet not syncing issue by using the windows client in a VM and throwing a VPN client (PIA) to bypass all my current double NAT'd badness. Chia docker is still doing the hard work of harvesting, but now everything is synced up and working as normal in the windows client (pointing to chia smb share) I'm sure this can be done with docker networking, but I wanted a quick solution to tide me over.

For anyone that has moved logs to stdout and is having issues using grep on logs, this is the command you need: docker logs chia 2>&1 | grep YOURKEYWORD

Make sure you have port 8444 forwarded, if you know your ISP has CGNAT you might need a VPN as the double NAT my be causing the sync issues. I'm double NAT'd at the moment and have syncing issues with my wallet (only).

There is also an offical faucet now too, although the official is a once off use as far as I can tell. https://faucet.chia.net/

Should be on par, Linux versions in general are far better than windows by at least 10%, not sure if would be much between Linux distros. Unraid's strength for Chia farming is that it is already setup to manage the apps, the drives, and the tiered storage solution. If I happen to win a bingo coin (XCH), I'll probably build a dedicated farming rig with parts I have already. User scripts plugin (GUI for cron essentially) and at minimum this code running on a schedule is all you need to get going #!/bin/bash dirNew=$(date +"%H%M%m-%d%y") docker exec chia venv/bin/chia plots create -b 3840 -r 4 -n 1 -t /plotting/$dirNew -d /plots note "-it" has been removed (we don't want interactive mode), otherwise its the same as the normal docker command

You need to restart the container before the changes will kick in. I don't think those warnings are anything to be worried about, but read through this if you're worried about the health of you farm https://github.com/Chia-Network/chia-blockchain/wiki/Is-my-farm-healthy---I-am-not-finding-proofs

Are there any issues with overlapping jobs when scheduling? i.e. ~4hr jobs run every hour

@Partition Pixel it should be: ghcr.io/chia-network/chia:latest I updated yesterday, and I'm currently on 1.1.6.dev0 according chia version You should only need to press the check for updates button on docker page, if you want to force a check

Out of the box this docker isn't configured optimally for logging, after some research these are two changes I've made to get better logging. Both changes are made to the config.yaml file that will be in chia's appdata folder: change log_level to INFO (from WARNING) change log_stdout to true (from false) Change one adds more useful info to the logs, change two pushes the logs to the standard docker logging mechanism, which means it is visible from the GUI's log button. Happy hunting!

Looks like new image has been build, it should appear shortly. It is recommended to update as soon as you can.

Put a fan on them so there is air moving through the enclosure (or across the bare drive), this will bring the temp down significantly.

No resume at the moment, so make sure your jobs have finished before you restart/update the container. note: this is a problem on all platforms, not docker specific

Make sure you either disable your old NIC, or ensure the 2 NICs are on different subnets. If the 10GbE is now your primary, or you have swapped around IP/subnets etc, make sure you also power cycle your network equipment.

This document linked from their FAQ should give you a good idea https://www.chia.net/faq/#faq-8

My server is busy 24/7, so I don't use S3, so I cannot confirm either way.

Did CA settings get reset to default on a recent update ?

Sorry if this has been covered, but does the plugin work with multiple pools? Any gotchas? Thanks.

Do you still see the 100% usage when the array is stopped?

From 6.9 onwards the global setting was deprecated due to multi-pool functionality, and is now set via each shares settings. For each share, you can now choose the type of pool use (including none), and the pool you want to use.

That will work, all that card does is pass the lanes to the nvme, so as far as your system is concerned it is directly connected. I've run a single nvme adaptor like this one in the past and it worked well.

Documentation is a little out of date for newer versions of Unraid, which has simplified the process to a drop down

Assuming you're on version 6.8.3 or higher... Create the pool (if it doesn't already exist), then go into settings and convert it from the default raid1 to raid0 using the dropdown in the pool settings (under balance heading), select raid0 and press balance.

169 address means unraid can't reach a DHCP service, i.e. the one on your router. Try power cycling your network equipment to start with. On the off chance you LAN is 2.5GbE, make sure your installing the latest unraid release (6.9+)

I would keep latest backup locally (from CA backup), you could then do incremental backups to a remote location based off the local backup. If you really don't want to keep the local backup, you could remove after the remote backup is complete.