DoeBoye

Members
  • Posts

    1175
  • Joined

  • Last visited

Everything posted by DoeBoye

  1. Ah! Got it! Thank you! Hypothetically speaking, due to limited space and trying to be efficient, if I were to recreate all my existing plots and set them k29, k30 or k31, would I see any negative effects on the other coins being farmed?
  2. After following the guide I have successfully updated to the newest version. I have all the new coins working except Chives. It shows fully synced, but cannot seem to connect to my plots. This is the log error that repeats over and over: "Failed to send events over script" Any ideas?
  3. No problem! Good luck and welcome to Unraid!
  4. I know that NOW! . I always thought it was just a short cut to save time when you wanted to upgrade parity and put it in the array at the same time. TIL
  5. Exactly! Cache drive can host your dockers as well as serve as the cache drive for your array. In theory you could even put VMs on there if you wanted (though I wouldn't recommend it. VMs perform best with their own dedicated drive). The docker image and the associated docker files live on the cache drive, while the media lives on the array drives. You could backup the docker files to the array if you like (I believe there is a plugin that does that... though it may have been deprecated... poke around Community Apps - install the plugin if you haven't yet. Makes finding/installing dockers/plugins much easier). Certainly wouldn't hurt and would save them if the cache drive ever failed. No worries. We all start somewhere!
  6. Correct. Cache drive can be anything. NVME, SSD, SATA, IDE (🤣). Doesn't matter. Any data copied to a share will first be copied to the cache drive (though the process is 'invisible' to the user. The data will appear to be directly on the share). That data is then transferred to the actual share drive(s) late at night during 'down time' (you can choose when that happens). The point is the cache drive is much faster than the array, and will make transfers etc 'feel' much faster as transfer speeds will be at the full speed of the cache drive (limited by your network of course if transferring over the network). A fast cache drive like an NVME (or to a lesser extent SSD) will also make your docker apps perform quicker, especially if they do a lot of IO intensive work.
  7. Fantastic! I never tried a parity swap before and always assumed it was only for an array without a failed drive. Thanks!!
  8. If cost is not an issue, NVME NVME NVME for cache drive! . Speeds up the whole system, including transfers as well as all the dockers running on it. 500GB is a bit small if you're going to start using it for dockers as well. I would look at 1 to 2TB if possible.
  9. Here's the situation: I have a failed data drive, but my replacement drive is larger than my existing parity drive. Is there a way to swap the existing parity drive with the new larger drive and using the old parity drive to replace the failed data drive without losing data? Thanks for any advice!
  10. As a data point, I farm flax and chia and my usage seems to hover around 7.4GB.
  11. Ahhh! Ok. That explains the Chia difference. Thanks! Now what about the Flax? It's not pooling, right? So shouldn't it match what's in the wallet?
  12. I did. I started plotting in other Chia Docker and imported the seed phrase. Doesn't look like an issue to be concerned about, so I will ignore :). A new issue. When I switched to pooling (or just coincidence?), my summary page is no longer updating wallets. Chia wallet or Flax wallet (though I can see the correct coin amount in the wallet page). Any ideas?
  13. Apologies if this has been answered, but I can't seem to find an explanation. Why did 2 Pooling wallets get created when I joined pooling? The wallet page now shows three Chia wallets: Wallet ID 1 type STANDARD_WALLET (I get it. This is the old one) Wallet ID 2 type POOLING_WALLET Wallet ID 3 type POOLING_WALLET (Why a second Pooling wallet?)
  14. I'm still not clear on Solo plotting vs self pool. Please correct me if I am wrong: solo plotting is the old way. No portable plot. farmer_pk and pool_pk are uncommented. pool_contract_address is commented. 2. Self pooling plots are portable. Not a part of any pool, but can join one with these plots. farmer_pk and pool_contract_address uncommented. Pool_pk commented.... Is this accurate?
  15. Ugh. That's embarrassing! . Thanks! It didn't even occur to me that it was the view!
  16. Apologies if I missed it, but how do I go about deleting these extra environment variables? There is no Edit/Remove buttons beside the extra variables...
  17. My Unraid Machinaris has been humming along quite nicely until this morning. All of a sudden, my plotting page no longer loads. Other pages are fine (Index, wallet etc), but /plotting throws a 500 error. Hmmm... Looking further, one of my plotting drives has dropped offline... Not sure why... Could that be causing this error?
  18. Just a word of warning. If you're using the auto update docker plugin, make sure to disable it for Machinaris, otherwise it will auto-update and wipe out any plots that are being plotted.
  19. Ahhh. OK. I will adjust accordingly . That said, I thought that tmpdir_stagger_phase_limit is more about number of CPU threads being consumed (more in 1st phase), so wouldn't make more sense to limit this on a global level, rather than per drive? Or if it is an issue for both threads used and disk IO, maybe make it configurable per drive then? Then the user can control how many total threads as well as how many per drive...
  20. Regarding "tmpdir_stagger_phase_limit", I have it set to '3', but I currently have 5 phase 1 plots running. I thought this was working before, could something have changed in .3? I *do* have 2 temp plotting directories, so is it possible that it is now applying the limit per temp directory rather than globally (which I assume should be the expected behaviour since the CPU is shared between all plotting jobs).
  21. This worked almost perfectly! The only thing is it is still showing my public keys on the wallet Settings page (and it still seems to think the mnemonic.txt file is in my root folder), even though the mnemonic.txt file was removed. Should there even still be a keys setting option? I'll submit it to github if it's an issue, but wanted to check here first. Perhaps it's working as designed...
  22. To run this in Plotter mode only, are these the correct changes (variables added) that need to be made to the docker (See attached image). Is there any other changes required? Also, do we need to remove the mnemonic.txt file from the chia root folder? Thanks!
  23. I thought I came across how to set Machinaris to only plot, or only farm but I can't seem to find it. Would you mind providing a lilnk to the right place?