Leaderboard

I had updated the Auto Update Docker Plugin to exclude Machinaris and thought that covered it. My daily docker updates excluded it just fine. Then I realized after an appdata folder backup that the docker updated itself again and I lost 8 Parellel plots In the Backup/Restore Appdata Plugin I realized there's an "Update Applications on Restart" selection which I had as "Yes". I'm thinking this then over rides the Auto Update Docker Plugin that I set to exclude Machinaris. I've set this to "No" now so I'll see if it fixes it on my next weekly Appdata backup. Just in case anybody else runs into this.

This thread is meant to replace the now outdated old one about recommended controllers, these are some controllers known to be generally reliable with Unraid: Note: RAID controllers are not recommended for Unraid, this includes all LSI MegaRAID models, doesn't mean they cannot be used but there could be various issues because of that, like no SMART info and/or temps being displayed, disks not being recognized by Unraid if the controller is replaced with a different model, and in some cases the partitions can become invalid, requiring rebuilding all the disks. 2 ports: Asmedia ASM1061/62 (PCIe 2.0 x1) or JMicron JMB582 (PCIe 3.0 x1) 4 ports: Asmedia ASM1064 (PCIe 3.0 x1) or ASM1164 (PCIe 3.0 x4 physical, x2 electrical, though I've also seen some models using just x1) 5 ports: JMicron JMB585 (PCIe 3.0 x4 - x2 electrically) These JMB controllers are available in various different SATA/M.2 configurations, just some examples: 6 ports: Asmedia ASM1166 (PCIe 3.0 x4 physical, x2 electrical) * * There have been some reports that some of these need a firmware update for stability and/or PCIe ASPM support, see here for instructions. These exist with both x4 (x2 electrical) and x1 PCIe interface, for some use cases the PCIe x1 may be a good option, i.e., if you don't have larger slots available, though bandwidth will be limited: 8 ports: any LSI with a SAS2008/2308/3008/3408/3808 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, 9400-8i, 9500-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed (most of these require a x8 or x16 slot, older models like the 9201-8i and 9211-8i are PCIe 2.0, newer models like the 9207-8i, 9300-8i and newer are PCIe 3.0) For these and when not using a backplane you need SAS to SATA breakout cables, SFF-8087 to SATA for SAS2 models: SFF-8643 to SATA for SAS3 models: Keep in mind that they need to be forward breakout cables (reverse breakout look the same but won't work, as the name implies they work for the reverse, SATA goes on the board/HBA and the miniSAS on a backplane), sometimes they are also called Mini SAS (SFF-8xxx Host) to 4X SATA (Target), this is the same as forward breakout. If more ports are needed you can use multiple controllers, controllers with more ports (there are 16 and 24 port LSI HBAs, like the 9201-16i, 9305-16i, 9305-24i, etc) or use one LSI HBA connected to a SAS expander, like the Intel RES2SV240 or HP SAS expander. P.S. Avoid SATA port multipliers with Unraid, also avoid any Marvell controller. For some performance numbers on most of these see below:

Goal: Easy remote WOL of my UNRAID server There are a thousand ways to this, however this worked for me and was pretty easy to do: (some steps might not even be necessary - but doing them anyway does not matter while leaving them out might...) HowTo Setup WOL for UNRAID: (assuming onboard NIC and WOL activated in motherboard's BIOS) *Put to sleep* 1. Webterminal or SSH into server 2. Type "ifconfig" and note IP-address and MAC-Address (ether) of used NIC 2. Type "ethtool -s eth0 wol g" 3. Type "echo -n mem > /sys/power/state" *Wake up* using 1. MacOS / Linux / Windows a) Download "MiniWOL2" from https://www.tweaking4all.com/home-theatre/miniwol2/ and install b) Click miniicon, push "Add" button and name the device to wake (Alias in Menu) c) set "IPv4 Address" (manually or select from ARP List) and "MAC-Address" (manually or click on 'detect') in appropriate fields d) Set "Broadcast" 255.255.255.255 e) Push "Test" to wake-up device (needs to be in sleep mode: see above) 2. Windows: (ALTERNATIVE) a) Download "wolcmd.exe" from https://www.depicus.com/wake-on-lan/wake-on-lan-cmd und unpack b) Open command line prompt and move to do dowload directory c) type "wolcmd.exe <ether> <ip-dest> 255.255.255.255 3. Linux: (ALTERNATIVE) a) Type "wakeonlan <MAC-Address>" OR b) Type "wol <MAC-Address>" I did not include any explanations on purpose, so if you need any - feel free to google :-) The only intent of posting this guide was hopefully sparing you guys some time if you just want to have it up and running. Feel free to question and comment.

Simple install with any recently updated version of opencore. I hear bluetooth breaks boot on bare metal so i would avoid that. Im using virtio for the network and the disk type and it boots just fine. Now to see what does not work.

Back to normal display after few minutes.

its only an Chia update. so no worries. the chia update adresses sync problems. do the update at good not plotting time

most of what people are running into are Docker related hardships that I have seen so far. Docker is a different mindset for how to run, map, and share resources but it is among the best once you get it up and some familiarity with it. I think you should rename the shares to not have spaces, periods, other non-alphanumeric characters and give it another try. The docker container will handle the map so you only need the friendly name "in container" mapped specified in your plotman.yaml Does that help? If you look about 10 questions back, Guy went over another person's mapping issues as well. Let me know if you have other pain points and I will try to make a video covering that setup.

Disk was already unmountable when you booted: Jun 7 11:24:04 ZEUS emhttpd: shcmd (201): mkdir -p /mnt/disk4 Jun 7 11:24:04 ZEUS emhttpd: shcmd (202): mount -t xfs -o noatime /dev/mapper/md4 /mnt/disk4 Jun 7 11:24:04 ZEUS kernel: XFS (dm-3): Mounting V5 Filesystem Jun 7 11:24:04 ZEUS kernel: XFS (dm-3): Corruption warning: Metadata has LSN (4:46847) ahead of current LSN (4:44318). Please unmount and run xfs_repair (>= v4.3) to resolve. Jun 7 11:24:04 ZEUS kernel: XFS (dm-3): log mount/recovery failed: error -22 Jun 7 11:24:04 ZEUS kernel: XFS (dm-3): log mount failed Jun 7 11:24:04 ZEUS root: mount: /mnt/disk4: wrong fs type, bad option, bad superblock on /dev/mapper/md4, missing codepage or helper program, or other error. Jun 7 11:24:04 ZEUS emhttpd: shcmd (202): exit status: 32 Jun 7 11:24:04 ZEUS emhttpd: /mnt/disk4 mount error: not mounted Jun 7 11:24:04 ZEUS emhttpd: shcmd (203): umount /mnt/disk4 Jun 7 11:24:04 ZEUS root: umount: /mnt/disk4: not mounted. Jun 7 11:24:04 ZEUS emhttpd: shcmd (203): exit status: 32 Jun 7 11:24:04 ZEUS emhttpd: shcmd (204): rmdir /mnt/disk4 syslog doesn't survive reboot unless you have Syslog Server going. Do you have logs from that? https://wiki.unraid.net/Manual/Troubleshooting#Persistent_Logs_.28Syslog_server.29

Did a reinstall and everything worked like a charm with the same setup. Guess the image had taken a hit in the upgrade or something. Thanks for the help

helped me out

Have you done memtest? Bad RAM could certainly cause corruption. How full was that disk?

Thank you for the donation, I'm glad you enjoy my work [emoji16] Sent from my CLT-L09 using Tapatalk

Hello, I get the error below 2021-06-07T17:15:06Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: x509: certificate is not valid for any names, but wanted to match ******.**" cfRay=hfsfhkfhkfh-FRA originService=https://192.168.178.42:4443 When I use this config and disable TSLVerify it works. tunnel: <my_UUID> credentials-file: /home/nonroot/.cloudflared/<my_UUID>.json ingress: - service: https://192.168.1.100:1443 originRequest: noTLSVerify: true On the GitHub post is mentioned to use: host.my.domain, where host is a subdomain you have valid DNS records for. But what does that mean? Have some one an example for me, because I am not so familiär with DNS records.

You're welcome, you can take a look here for some recommended models:

Problem with the onboard SATA controller: Jun 1 14:00:59 SRVUNR1 kernel: ahci 0000:03:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xe7d60000 flags=0x0000] Unfortunately quite common with some Ryzen boards, BIOS update might help, or using a newer Unraid release when available due to the newer kernel, failing that best bet is to use an add-on controller (or a different model board).

Hast du beim Container /mnt zugeweisen oder einen Unterordner?

Hi! Interesting suggestion. Could be a good enhancement. Please add an Issue request with all the details to Github. What did the Wallet page show after you made this transaction? These pages are cached for ~60 seconds to limit performance impact, so perhaps take a look after a minute. Interesting one. You may wish to open an Issue on the Chiadog Gitub.

Quick googling suggests to enable TPM in the BIOS

Das geht nur manuell: - Krusader installieren - manuell so viele Dateien wie du meinst von /mnt/disk1 zu /mnt/disk5 verschieben (Achtung: Niemals von /mnt/user zu /mnt/diskX. Das kann zu Datenverlust führen!) oder mit einem Trick: - die neue Disk5 (sage ich jetzt mal das wäre die 5.) dem Share zu ordnen - Verteilungsregel "most-free" - Share auf "Prefer" stellen - Mover anwerfen - die Dateien werden auf den Cache verschoben bis dieser voll ist - Share auf "Yes" stellen - Mover anwerfen - Unraid berücksichtigt die Verteilungsregel und schiebt die Dateien nun auf die Disk5 Da der Cache allerdings selten groß genug ist, müsste man im Wiederholungsfall noch weiter tricksen: - Disk1 und neue Disk aus dem Share weglassen - Prefer - Mover - Disk5 wieder zuordnen - Yes - Mover Nun sollte er die Dateien von Disk2 auf den Cache verschoben haben und dann die wieder auf die neue Disk. Beim 3ten mal müsste man dann noch mehr Disks rauslassen: - Disk1, Disk2 und Disk5 aus dem Share weglassen - Prefer - Mover - Disk5 wieder zuordnen - Yes - Mover Das wiederholt man nun so lange bis man mit Disk4 durch ist. Danach kann man wieder alle Disks dem Share zurodnen. Bitte mach das aber nicht mit Shares, die durch Docker/VMs in Verwendung sind. Diese Dienste sonst vollständig deaktivieren bis alle Dateien da sind, wo sie hin sollen. Für die Zukunft: Vielleicht die Shares/Unterordner so erstellen, dass sie sich besser verteilen lassen. Ich habe deswegen zB Filme in den Ordner A bis Z.

Thank you for the feedback and the creation of the issue itself, much appreciated. Please report back what the outcome of this issue is.

The devs, due to the errors, think it might be a metadata string issue: -Looks like the photo location can't be created properly due to a broken metadata string. Need to know what it is specifically to provide a fix if needed. -Might be related to the location details, which our backend returns... so it would be good to test as guessing takes a lot of time I'll send you a PM with a RAW file, but any idea what metadata strings might be broken?

Das könnte schon sein, weil ich dieses Problem beim Umstieg von Win 7 auf Win 10 (1909) auch hatte. Ich mußte in den SMB-Settings den Eintrag umstellen auf "min protocol = SMB2" Die Frage is nur, welches Win 10 er zur Zeit benutzt. Ein aktuelles Win 10 benutzt v3.1.1

Öffnest du nextcloud über https://deinesub oder http://deinesub? Wenn es letzteres ist, dann bitte in NPM auf https weiterleiten lassen. Ich habe das gefunden: https://github.com/nextcloud/server/issues/18602#issuecomment-569513414 was auf das verlinkt: https://github.com/nextcloud/docker/pull/819#issuecomment-541434657 Teste bitte mal die folgenden Einstellungen in der config.php anzupassen:

Check mal ob dein BIOS eine entsprechende Option hat. Ansonsten hier lesen:

Lieferung ist da. Hinweis: 4 Stück sind bereits verkauft.

Just to be very clear, the file will be moved, not copied with the regular Unraid behavior.

Sorry i should have tried earlier but your advice to check tvheadend let me see that the device was being detected so i removed the binhex plex and installed the linuxserver container and it is now detected. Sorry for the time waste but thank you for responding so quickly.

Maybe this is what you were proposing but I'm not sure. You have several shares set as cache-only, appdata, system, some others related to VMs. Mover can't move open files, so you will have to disable Docker and VM Manager in Settings before you can move these shares off cache. Set each of these shares to cache-yes and run mover to get them moved to the array. Check to make sure everything got moved from cache before replacing cache. I don't anticipate any problems such as duplicates because all these shares are cache-only and currently have no files on the array. After you replace cache, set any shares you want moved back to cache to cache-prefer, then run mover. After you have things back on cache you can set these to cache-only if you want, then enable dockers and VMs.

Wenn du einen Docker Container manuell installierst, musst du die Pfade, Variablen usw selbst erstelle. Unten über den +-Button.

Thanks I'll give that a try and report back.

Bin mit Vaultwarden (Bitwarden Rust mit Premium Features) auch sehr zufrieden.

Yes that slot is already busy (by the ide controller). First free slot is 0x08. Replace the xml: <domain type='kvm'> <name>Buzz</name> <uuid>54263aab-81a4-ed75-aa59-e7701d3f14fd</uuid> <description>3 Cores</description> <metadata> <vmtemplate xmlns="http://unraid.net/xmlns" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='10'/> <vcpupin vcpu='1' cpuset='26'/> <vcpupin vcpu='2' cpuset='11'/> <vcpupin vcpu='3' cpuset='27'/> <vcpupin vcpu='4' cpuset='12'/> <vcpupin vcpu='5' cpuset='28'/> <emulatorpin cpuset='18-19'/> </cputune> <numatune> <memory mode='strict' nodeset='1'/> </numatune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/54263aab-81a4-ed75-aa59-e7701d3f14fd_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='6' threads='1'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback' discard='unmap'/> <source file='/mnt/user/domains/Buzz/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='scsi'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback' discard='unmap'/> <source file='/mnt/user/domains/Buzz/vdisk2.img'/> <backingStore/> <target dev='hdd' bus='scsi'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/iso/Windows.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/iso/virtio-win-0.1.190-1.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='scsi' index='0' model='virtio-scsi'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='e8:2e:d9:1e:b4:9d'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x44' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/gpu/gtx1660.dump'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x44' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x44' slot='0x00' function='0x2'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x2'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x44' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x3'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x45' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain> The i440fx machine type has hardcoded addresses in qemu: 0000:00:00.0 Host Bridge 0000:00:01.0 ISA bridge 0000:00:01.1 primary IDE controller 0000:00:01.2 PIIX3 USB controller 0000:00:01.3 ACPI (power management) and SMBus controller So these addresses cannot be used for other hardware

Or if you added a pre-cleared 12TB to the array. If the system didn't check the remainder of the parity, then the parity may or may not be in sync with the precleared new large data drive.

Thanks, I did end up having to flash to a new usb drive and it's working now.

Yeah, I'm sure it's your antivirus software on your computer doing it. Just posting an example of what to look for.

Post Diagnostics

I felt compelled to post here and give you a HUGE thank you for putting this utility together. It is exactly what I didn't know I needed! I have a lot of 2TB drives of various ages, some over 7 years, and while they pass their monthly parity check and show no issues in SMART, your utility will help me monitor the actual performance of the drives and help catch any issues. I imagine it's only a matter of time before I'll need to replace a couple of the drives. Thank you!

UPDATE: ControlR iOS is now available on the App Store (give it some time for the rollout to reach your region) ControlR Android is in review, but should become available shortly now available on the Play Store (give it some time for the rollout to reach your region) 🙌

OK, granted, but also keep in mind that, and again assuming the OP is using SATA devices, he will suffer from some performance loss due to the mentioned SAS wide link not being really 12G, and that is probably what's limiting his current bandwidth, and not the PCIe x8 slot. x4 SAS link has max bandwidth of 1200MB/s, 1100MB/s usable, x4 SAS2 link max is 2400MB/s, 2200MB/s usable, both of these I confirmed myself in the tests linked above and results are very consistent with a number of different devices, x4 SAS3 link max is 4800MB/s, I'm going to assume 4400MB/s usable, unfortunately I have no way of testing this since I'd need some SAS3 SSDs, but LSI points to the same values: Now if we accept those I can show the performance degradation of not using a real SAS3 link: Left side 8 SATA3 SSDs directly connected to an LSI 9300-8i, right side same but now with an expander in the middle, so while Databolt does a very good job, or max combined speed would only be 2.2GB/s, still about 10% degradation from what it should be with real SAS3 devices (4.4GB/s), and IMHO that's likely the limit the OP is hitting, and in that case getting a PCIe x16 HBA won't really help. I would say not possible with SATA devices because of the above, and very much doubt it's possible even with SAS devices, I believe that in optimal conditions around 6500MB/s would be possible, don't think 7000MB/s+ can be done, but happy to be proved wrong , just point to someone achieving those speeds in the real world with a HBA/expander, I would like to get my hands on some SAS3 SSDs to test myself, maybe some day if I can find some cheap ones.

UPDATE: We found the root cause of the issue !!! 🙌 Can't thank enough @Dantheman and Peter (don't have his handle), for the patience and willingness to help me test and troubleshoot. Thank you !!!! The root cause is what I had originally thought: Unassigned Devices changed its api in a recent release and that broke the app 😮 😀 I'll be publishing a new release to both stores in the coming hours, although Apple Store generally takes longer to review than Google Store. I'll post back when they're available.

UPDATE: We found the root cause of the issue !!! 🙌 Can't thank enough @Dantheman and Peter (don't have his handle), for the patience and willingness to help me test and troubleshoot. Thank you !!!! The root cause is what I had originally thought: Unassigned Devices changed its api in a recent release and that broke the app 😮 😀 I'll be publishing a new release to both stores in the coming hours, although Apple Store generally takes longer to review than Google Store. I'll post back when they're available.

Disks used in the UnRaid array have to be partitioned and formatted by Unraid.

This: may be useful to understand how the q35 emulated machine topology works, so that we can attach hardware in the correct bus, for example HDEF audio and built-in ethernet.

2.2.1 - 2024-03-06 Updated - Chia to v2.2.1 - possible fixes for serious problems in v2.2.0? Notes - Updated potentially buggy Chia software DOES NOT imply my endorsement. *Only upgrade when you are comfortable.* 2.2.0 - 2024-02-29 Added - Support for Achi blockchain. Requires its own plots (like Chives), you'll have to plot separately if interested. Thanks @priyankub - Optionally launch Chia Data Layer services if env var `chia_data=true` is set. Changed - Harvester mode will now optionally also run chia-exporter for Prometheus results. Updated - Chia to v2.2.0 - misc improvements, see their release notes. - Cactus to v2.1.4. - Gigahorse to v2.1.4.giga26. - Wheat to v2.1.6 Notes - Support for new blockchains and tools DOES NOT imply my endorsement for them. Only run those you are comfortable with. 2.1.4 - 2024-01-11 Added - Optionally launch `chia-exporter` [metrics endpoint](https://github.com/Chia-Network/chia-exporter) for Prometheus reporting if env var `chia_exporter=true` is set. - Support for running Gigahorse containers on arm64 architectures such as Raspberry Pi. - Main dashboard page can now be pinned (Pin Icon) to display only a blockchain of interest, rather than rotating through each in turn. Changed - Optionally launch of Gigahorse recompute server when in harvester mode if env var `gigahorse_recompute_server=true` is set. - Fix for Bladebit GPU plotting jobs taking a minute to display on Plotting page on job start. Should now be seconds only. Updated - Chia to v2.1.4 - misc improvements, see their release notes. - Gigahorse to v2.1.3.giga26. 2.1.3 - 2023-12-19: addresses the unfortunate bug CNI released in v2.1.2. 2.1.2 - 2023-12-13 ### Added - Settings | Plotting | Bladebit now supports "no_direct_io: true" option - Settings | Plotting | Bladebit now supports "check_plots: 100" option to check at end of plot creation - Settings | Plotting | Bladebit now supports "check_threshold: 0.6" option to delete invalid plots at end of plot creation ### Changed - Support for Gigahorse Recompute Server (single GPU on fullnode/farmer), shared by multiple Gigahorse harvesters. ### Updated - Chia to v2.1.2 - misc improvements, see their release notes. - Gigahorse to v2.1.1.giga25 with C20 compression support. - Flask to v3.0.0 - serves up the Machinaris WebUI. ### Notes - Regression in Chia binaries (since v2.0.0) ignoring the "-y" parameter on plotnft changes, has broken pool join/leave thru WebUI. 2.0.0 - 2023-08-24 Added - Request a new plot check, via 'Recheck' button added to Check results dialog on Farming page. - Optionally exclude certain plot directories from replotting check to free disk space. Useful for drives only partially dedicated to holding plots. Changed - Deprecated stale blockchains, by hiding them from Worker wizards: BPX, N-Chain, Silicoin, Stor Updated - Bladebit to 3.0.0. - Cactus to v2.0.0 - Chia to v2.0.0. - Gigahorse to 1.8.1.giga14. - HDDCoin to 3.0.0 based on Chia 1.8.2. - MMX to v0.10.6. - Wheat to v1.8.2. 1.8.2 - 2023-06-30 Updated - Chia to v1.8.2 1.8.1 - 2023-05-17 Changed - By default, exclude Gigahorse plots from automated plot check due to poor performance of the 'ProofOfSpace' binary. - Fix for plotting manager issues when plotting with multiple tmp drives. Updated - Bladebit to 3.0.0-alpha4. See known issues. - BPX to v2.1.0 - Cactus to v1.8.0 - Chia to v1.8.1 - Flora to v1.8.0, updated by ageorge95. - Gigahorse to v1.8.0.giga11. Notes - Bladebit still broken on ability to ramplot and diskplot as they try to match Gigahorse's GPU plotting. Still awaiting a fix... - Support for new blockchains and tools DOES NOT imply my endorsement for them. Only run those you are comfortable with. 1.8.0 - 2023-05-04 Added - Concurrent plot transfers to both remote and local archive paths. Previously was one plot transferred at a time. - Checking for adequate free space on both tmp and dst paths before starting another plotting job. - Replotting selection (Farming page settings) can now target uncompressed plots for deletion. Changed - Fix for Download button on Settings pages that were providing the wrong config file. Thanks @TuftyBruno. - Updated German and Portugese translations. Thanks to @slowfinger and @antcasq. All contributions are appreciated. - Follow Chia version numbers (like 1.8.0) from now on, as Machinaris is on their release cadence. Updated - Cactus to v1.7.1 - Chia to v1.8.0 - Gigahorse to v1.8.0.giga10. - HDDCoin to 3.0.0-beta1 based on Chia 1.7.0. - MMX to v0.10.2 on `testnet10`. 0.8.8 - 2023-03-23 Added: Support for running a blockchain timelord with environment variable `mode` set to `fullnode,timelord`. Optional config setting to restart fork fullnodes if they consume too much memory. Looking at you Flora, HDDCoin, N-Chain, etc... Changed: On fresh install, optionally download (via libtorrent) a recent Chia database checkpoint. https://www.chia.net/downloads Fixes for Gigahorse GPU plotting including 64 GB RAM mode using the `tmp3` SSD plotting path. Fix for Gigahorse Alerts, please reset earlier broken settings file to https://github.com/guydavis/machinaris/blob/develop/config/chiadog/gigahorse.sample.yaml. Fix for container stop signal to cleanly shutdown forks too, as was already happening for Chia. Updated: Bladebit to 3.0.0-alpha3, so still unstable. https://downloads.chia.net/bladebit/ Chia to v1.7.1 https://github.com/Chia-Network/chia-blockchain/releases/tag/1.7.1 Gigahorse to v1.6.2.giga7 with OpenCL support for AMD GPUs. https://github.com/madMAx43v3r/chia-gigahorse/releases/tag/v1.6.2.giga7 MMX to v0.9.14 on `testnet9`. Supporting the latest AMD GPU driver. https://github.com/madMAx43v3r/mmx-node/releases/tag/v0.9.14 One to v1.7.0 https://github.com/xone-network/one-blockchain/releases/tag/1.7.0 Notes: Bladebit has regressed on the ability to `ramplot` as they try to match Gigahorse's GPU plotting. Still awaiting a fix... Support for new blockchains and tools DOES NOT imply my endorsement for them. Only run those you are comfortable with. 0.8.7 - 2023-02-16 Added Schedule plotting on the "Settings | Plotting" page to take advantage of off-peak electricity, lower your fan noise, avoid backups, etc... Bladebit - alpha GPU plotting support in main Machinaris image. Set `mode: gpuplot` under `bladebit` on Settings | Plotting page. Gigahorse - beta GPU plotting and farming support in new Machinaris-Gigahorse image. Set `mode: gpuplot` under `madmax` on Settings | Plotting page. Ballcoin - blockchain at version 1.6.0, another slow Silicoin fork. Pipscoin blockchain at version 1.7.0. Changed Fix missing Connections listing for Flax and MMX blockchains. Thanks @ekersey! Fix for Bladebit ramplot relaunching. Thanks @JoeZotacExperience! Multiple functionality & performance cleanups from excellent code review by @qoole. Display compression level for active plotting jobs on Gigahorse and MMX. Updated BTCGreen to v1.7.0b Cactus to v1.6.2 Chia to v1.7.0 Chives to v1.5.4, including staking. SHIBGreen to v1.7.0.1 Staicoin to v1.3.0. Note, they require a fresh `config.yaml`. Notes Support for new blockchains and tools DOES NOT imply my endorsement for them. Only run those you are comfortable with. [0.8.6] - 2023-01-03 Re-plotting: **Optional** background deletion of a few old plots to free space for new plotting. See Farming page, Settings icon, top-right. Table of recent plot archiving (local and remote) on new "Plotting | Transfers" page, including status and transfer speed. "Settings | Alerts" page: new 'Send Test Alert' button to validate Chiadog configs and receive sample alert to mail/discord/etc. [Coffee](https://github.com/Coffee-Network/coffee-blockchain) blockchain at version 1.0.1, a slow Silicoin fork. [GreenBTC](https://github.com/greenbtc/greenbtc-blockchain) blockchain at version 1.6.3, another slow Silicoin fork. [Moon](https://github.com/MOONCOINTEAM/moon-blockchain) blockchain at version 1.6.0, a recent Chia fork. [One](https://github.com/xone-network/one-blockchain) blockchain at version 1.6.2, a recent Chia fork. Fixed broken 'Generate/Import Key' actions for Chia 1.6.1 on Setup page. Thanks @SilverFolfy Missing plots on Farming page when a status.json file was corrupted. Thanks @Yurly Fix for duplicated Chiadog alerts of wallet additions. Thanks @GravitasProblem and @doma2345 Improved "Settings | Pools" page with fee amount and `delete_unconfirmed_transactions` action. [Bladebit](https://github.com/Chia-Network/bladebit/releases/tag/v2.0.1) to v2.0.1 [Cactus](https://github.com/Cactus-Network/cactus-blockchain/releases/tag/1.7.0) to v1.7.0 [Chia](https://github.com/Chia-Network/chia-blockchain/releases/tag/1.6.2) to v1.6.2 [Chinilla](https://github.com/Chinilla/chinilla-blockchain/releases/tag/1.4.0) to v1.4.0 [Chiadog](https://github.com/guydavis/chiadog/releases/tag/v0.7.5) to v0.7.5 [Flax](https://github.com/Flax-Network/flax-blockchain/releases/tag/0.1.11) to v0.1.11 [MMX](https://github.com/madMAx43v3r/mmx-node/releases/tag/v0.9.3) to (v0.9.3) on `testnet9`. Supporting the latest AMD GPU driver. [Tad](https://github.com/BTCgreen-Network/tad-blockchain/releases/tag/1.7.0b2) to v1.7.0 NOTE: Support for new Chia forks DOES NOT imply my endorsement for them. Only run those you are comfortable with. [0.8.5] - 2022-11-03 Wallets page - Claim Rewards button offers portable plot reward recovery after one week has elapsed. (EARLY BETA!) Chart memory usage per container (GiB) as well as total host memory usage (%) for OS and all apps. Enhanced Forktools to optionally decrease a blockchain's full_node process count, which greatly limits memory usage. Improve Plotting page to display configured tmp, dst, and archiving directories before starting to plot. Support `site_path_filter` for archive folders under `site_root`. Bladebit support for new `ramplot` mode (needs 416 GB RAM) Enhance 'NFT Reward Recovery' tool to support v2 databases. Fixes for invalid Chiadog harvester alerts. Fixes for bladebit `diskplot` mode (less than 416 GB RAM, needs 400+GB of tmp disk) [Bladebit](https://github.com/Chia-Network/bladebit/releases/tag/v2.0.0) to v2.0.0 [Chia](https://github.com/Chia-Network/chia-blockchain/releases/tag/1.6.1) to v1.6.1 [Chinilla](https://github.com/Chinilla/chinilla-blockchain/releases/tag/1.3.0) to v1.3.0 [Littlelambocoin](https://github.com/BTCgreen-Network/littlelambocoin-blockchain/releases/tag/1.6.1) to v1.6.1 [Maize](https://github.com/Maize-Network/maize-blockchain/releases/tag/1.6.0) to v1.6.0 [MMX](https://github.com/madMAx43v3r/mmx-node) to `testnet8`. [0.8.4] - 2022-09-21 Scaling-Down: Optional mode where wallets are synced daily, not run 24/7. Saves ~35% memory so smaller farmers can farm more blockchains concurrently on the same machine. See Wallets page, top-right Settings. Scaling-Up: Improved plot tracking efficiency for multi-PB sized farms. Thanks @grobalt! Warnings for duplicated, invalid, or key-less plots. See Farming page. Update: Flax to v0.1.10, Cactus to v1.5.2, Chia to v1.6.0 Security: Disable Setup page's mnemonic import field autocomplete from caching value in your local browser. Thanks @Baatezu! Fixes: Better handling of farmed block logging for certain blockchains like Apple & BPX, Alerts from Chia 1.5.1 for added coins missing due to blockchain logging changes. Improved Smartctl response processing. Thanks @gnomuz! [0.8.3] - 2022-08-23 Additional blockchain pricing from Vayamos and Posat exchanges on the Blockchains, Wallets, and Summary pages. New blockchains: Apple, Chinilla, Gold, LittleLamboCoin, Mint, Tad, Wheat Update: BPX to v2.0.0, BTCGreen to v1.5.0, Maize to v1.5.0, Petroleum to v1.0.16, Shibgreen to v1.5.0 Update: Chia to v1.5.1, Bladebit to v2.0.0 (beta-1) with diskplot mode (beta only in `:develop` and `:test` images) Fixes: Avoid timeout/slowness encountered by those with many drives, also many cold wallet transactions [0.8.2] - 2022-07-24 MMX - Record created blocks from blockchain logs, for display in Machinaris, off index page. Ubuntu - latest blockchains run on Jammy Jellyfish (Python 3.10), outdated blockchains run on Focal Fossa (Python 3.9). Fixes missing chia_plot error in v0.8.1 which started yesterday. Updated: Cactus 1.4.1 to fix SSL certificate expiry, may require entire deletion of mainnet directory and full re-sync. Check their Discord for latest support of this blockchain. Updated: Chia 1.5.0 [0.8.1] - 2022-07-17 Connections - add node peers directly from list offered by AllTheBlocks per blockchain. MMX - Compute "Estimated Time to Win" from plots size, netspace size, and blocks per day. New blockchains: BPX, Ecostake, Petroleum, and Profit Updated: Cactus, Chiadog [0.8.0] - 2022-06-30 Charting of each blockchain's netspace, farmed coins, and wallet balances over the past month. Tracking farmed blocks sent directly to cold wallet. Set your cold wallet addresses on the Wallets page. Added a read-only transactions viewer for each blockchain's wallet, available from Wallets page. Alerts: per-notifier allow setting to allow only selected alerts, based on criteria. Chia - v1.4.0, after a month of pre-release testing with Machinaris. Cactus - v1.3.4, matches Chia 1.3.4, please run: cactus db upgrade Chives - v1.3.1, please run: chives db upgrade Cryptodoge - v1.3.4, matches Chia 1.3.4, please run: cryptodoge db upgrade Flax - v0.1.9, matches Chia 1.4.0, please run: flax db upgrade if you haven't yet MMX - updated version for their testnet6 network. [0.7.2] - 2022-05-17 Drives monitoring page - allow overrides of smartctl commands for special hardware. Drive failure alerts thru our enhanced Chiadog. Alerts: per-notifier ignore setting to prevent unwanted alerts, based on criteria. German translations of the Machinaris WebUI by @ApfelBirneKreis. Big thanks! Chia - v1.3.3 release, various minor bug fixes Chia - v1.3.4 release, upgrade fullnode before harvesters Chia - v1.3.5 release, fixes their `chia version` number offset Staicoin - v1.2 release - careful, bugs reported on their Discord, but seems to be working... [0.7.1] - 2022-04-02 Drive monitoring using Smartctl (WebUI status currently, alerting to come soon) Dutch translations (nl_NL) provided by @bdeprez. Thanks! Updates to various fork blockchains and tools including BTCGreen, Flax, HDDCoin, Madmax, MMX and Shibgreen Chia- v1.3.1 and v1.3.2 patch releases [0.7.0] - 2022-03-11 Chia v1.3: please note reports of issues in this new Chia release... double-check your Wallet, Payout, and Pools settings after upgrading! Internationalization for locale-specific text, numbers, and currencies. Huge thanks to @antcasq (pt_PT) and @fabriziocacicia (it_IT) for providing translations! Geolocation of peer connections for each blockchain by their IP address. Optionally enabled using a free Maxmind account. Silicoin - supported again as per Discord votes. [0.6.9] - 2022-02-04 MMX - support for this new blockchain, which requires its own plot files. HDDCoin - update to version 2.0.0 Improved summary display for status. Estimated price in USD provided by alltheblocks.net Various fixes for issues reported in the Discord. Thanks to all who reported! [0.6.8] - 2022-01-04 SHIBGreen - cross-farming support for this blockchain fork. Support for pooling configuration of forks like Chives. Updated blockchains: Chives, Stor, Stai(coin) Various fixes for issues reported in the Discord. Thanks all! [0.6.7] - 2021-12-03 BTCGreen - cross-farming support for this blockchain fork. Plotting page - Charts to show plotting speed for recent jobs across all workers on your farm. Option to disable background job to Chia `plots check` and Plotman `analyze`. Set `plots_check_analyze_skip` env var. Fix for Madmax building on certain user's hardware. Thanks @karaliux for the patch! Fix to ensure Forktool's configs (~/.machinaris*/forktools/ftconfigs/) are persistent across container restarts. Fix to quiet logrotate output from container stdout. Too verbose. Fix to incorrect commenting out of `pool_contract_address` on plotter systems. Please double-check your Settings | Plotting page! Check Farming | Plots page for recent 'solo' plots. Fix to Plotting | Workers page for graph showing tmp disk usage during plotting on mode=plotter systems. Fix Farming | Workers page to show Daily Summaries for TrueNAS users with FQDN hostnames in their containers. Fix - Blockchain download for fresh installs, use the new download paths provided by Maize team. [0.6.6] - 2021-11-28 Maize - cross-farming support for this blockchain fork. Forktools - utilities including a multiproc patch to limit memory usage. Farming - right-side of Plots table offers Chia "plots check", slowly generated on background thread. Bug Fix - hourly log rotation for `farmr`, auto-deletion log if above 20 MB in size. Sorry all! [0.6.5] - 2021-11-19 Cryptodoge - cross-farming support for this blockchain fork. Docker images now roughly 1/3 the size of previous releases. Shared base image further decreases download size for forks. API endpoint /metrics/prometheus exposes plotting statistics. Thanks to @Nold360 for the contribution! Windows deployments now support automatically mounting remote plot shares (such as on a NAS) using CIFS in-container. On Wallets page, display total wallet balance including cold wallet address amounts. [0.6.4] - 2021-11-12 Farmr - include `farmr` client for optional monitoring at farmr.net Stor - cross-farming support for this blockchain fork. Cactus - cross-farming support for this blockchain fork. [0.6.3] - 2021-11-05 Staicoin - cross-farming support for this blockchain fork. Chia - Update to version 1.2.11. See their changelog for details. [0.6.2] - 2021-10-29 Silicoin - cross-farming support for this blockchain fork. fd-cli - Daily scheduled 7/8 coin win recovery for those farming NFT plots on other blockchains. Madmax - support for plotting k33 and k34 plot sizes. Machinaris - correctly show daily difference tooltips on Summary page statistics for all blockchains [0.6.1] - 2021-10-23 Flora - cross-farming support for this blockchain fork. ChiaDog - improved support for forks, fix coin symbol in certain alerts, Chives decimal placement, etc. Machinaris - correctly report Chives plots from harvesters in the WebUI. Plots were farmed, but hidden from WebUI before. Machinaris - fix error in Setup - Mnemonic Import wizard. Machinaris - re-enable the Plotman Archving start/stop buttons. [0.6.0] - 2021-10-18 NChain- cross-farming support for this blockchain fork. HDDCoin - cross-farming support for this blockchain fork. Chives - support for this blockchain fork. Flax - now farmed in a separtate Docker container. Plotman - enhancement to support plotting for Chives via Madmax. Chiadog - enhancement to support monitoring of other blockchain forks. [0.5.7] - 2021-10-02 Chia - Update to version 1.2.8. See their changelog for details. Bladebit - Update to version 1.2.0. See their changelog for details Chia - Update to version 1.2.9. See their changelog for details. [0.5.6] - 2021-09-17 Machinaris - On RaspPi, allow configurable status update frequency when running a Machinaris fullnode/controller. Machinaris - Fix for launching harvesters on RaspPi devices, avoids missing bladebit error. Machinaris - "Disconnect Selected" feature now available on Network | Connections page. Machinaris - Improve Summary page to better separate Chia and Flax blockchains. Chia - Update to version 1.2.7. Flax - Update to version 0.1.2. Bladebit - Update to version 1.1.1. [0.5.5] - 2021-09-13 Chia - Update to version 1.2.6. See their changelog for details. Plotman - Update to version 0.5.2 with support for the Bladebit in-memory plotter. Plotman - Avoid use of tty for container platforms such as TrueNAS to allow plotting without `-t` docker flag. Machinaris - Improved status reporting efficiency and better logging. [0.5.4] - 2021-08-31 Chia - Update to version 1.2.5. See their changelog for details. Machinaris - Fix for Chia 1.2.4 SSL issue seen on plotter-only systems. Machinaris - Displayname for Workers tabs of Plotting and Farming pages. Machinaris - Fix for partials chart on Summary page. Machinaris - Fix for plotting log view. [0.5.3] - 2021-08-27 Worker page for each worker shows Warnings for certain configuration issues. Farming page now shows current disk usage for each drive (free and used) Plotting page now shows recent disk usage for each drive (free and used) Summary page now charts recent blockchain challenges and partial proofs Fixes from feedback received by users on the Machinaris Discord. Thanks all! Chia - Update to version 1.2.4. See their changelog for details. [0.5.2] - 2021-08-13 - Machinaris - Docker images now available for [Apple M1](https://github.com/guydavis/machinaris/issues/43) and [Raspberry Pi OS](https://github.com/guydavis/machinaris/issues/155) architectures. - Chiadog - Update to new v0.7.0 to [support for parsing partials and solo blocks](https://github.com/martomi/chiadog/pull/268). - Chia - Update to patch release of 1.2.3. See their [changelog for details](https://github.com/Chia-Network/chia-blockchain/releases/tag/1.2.3). - Flax - Update to version 0.1.1. See their [changelog for details](https://github.com/Flax-Network/flax-blockchain/releases/tag/0.1.1). - TrueNAS - Support for Machinaris deployment via helm chart. [Issue #78](https://github.com/guydavis/machinaris/issues/78) - Big thanks to @kmoore134 for this! - Machinaris - Daily Farming Summary now available on Farming page for both Chia and Flax. Add new plot type column. - Machinaris - Pools - Show each Pool's status including link to your pool provider. List pool point events on Summary page. - Machinaris - Workers - Use hostname for Worker display name, even when using IP addresses behind the scenes. Also show versions. Automated harvester setup. - Machinaris - Connections page has link to test your router port forward for farming. - Machinaris - New [public website](http://www.machinaris.app) with launch Wizard for generating first Docker run/compose of Machinaris. [0.5.1] - 2021-07-22 - Wizard on Workers page to create a Docker run/compose based on your settings. [Issue #97](https://github.com/guydavis/machinaris/issues/97) - Latest Madmax plotter with support for n_buckets3 and n_rmulti2 settings in Plotman. - Update to patch release of Chia 1.2.2, including a fix for harvester cache updates. See their [changelog for details](https://github.com/Chia-Network/chia-blockchain/releases/tag/1.2.2). [0.5.0] - 2021-07-09 - Support for [official Chia pools](https://github.com/guydavis/machinaris/issues/131). Chia and Madmax plotters can create portable plots. - Plotting and farming on the [Flax Network](https://github.com/guydavis/machinaris/issues/105). Enabled by default, but can be [disabled](https://github.com/guydavis/machinaris/wiki/Flax#optional-to-disable). [0.4.0] - 2021-06-25 - Support for [Madmax plotter](https://github.com/madMAx43v3r/chia-plotter), in addition to official [Chia plotter](https://github.com/Chia-Network/chia-blockchain). - Manage multiple plotters, harvesters, and farmers across your LAN, all from a [single WebUI on one controller system](https://github.com/guydavis/machinaris/wiki/Workers). [0.3.2] - 2021-06-06 Include the just released Chia 1.1.7. For details, see their [changelog](https://github.com/Chia-Network/chia-blockchain/blob/1.1.7/CHANGELOG.md#117-chia-blockchain-2021-06-05). [0.3.1] - 2021-06-04 After testing showed between 15% to 30% speedup on plotting, adopting Chiapos multithreaded library. Thanks to `hereisderek` for a great PR containing better rsync support, SSH key import, and optional auto-plot on container restart. Include `paho-mqtt` library to support Chiadog alerts via MQTT by default. [0.3.0] - 2021-05-28 Integrate the excellent Chiadog project for log monitoring and alerting Plotman Analyze output to show time spent in each plotting phase Log Viewer for Farming, Alerts, and Plotting including logs for running plot jobs Rebase off ubuntu:focal, include nice Dockerfile cleanup by sparklyballs When mode=plotter, autoconfigure Plotman with provided farmer_pk and pool_pk When mode=harvester, auto import of your farmer's CA certificates [0.2.0] - 2021-05-20 Improved key handling including generation (if needed) and supporting multiple keys. Now supports mounting multiple final plots folders for plotting and/or farming. Plotting page now has Plotman Stop action, along with Suspend/Resume/Kill actions for plots. When you can take a pause in plotting jobs, click Unraid's Docker 'Check for Updates' button. Machinaris should be showing an available update. Please let me know any feedback you have.

Thanks for the reply, I've added a static route now on both configs - Some improvements, but I still having some issues. On the simple server - I can now connect to the Unraid UI and to the pfsense UI. but I still can't access anything else on the network. I've tried the firewall rules because of the firewall log: (first one 192.168.0.31:8123 is the source, the 10.253.0.2 is the destination) it looks like the remote device (the VPN peer) try to talk to the local service, but when the local service try to "take back" there's an issue. on the complex server, it's basically the same + but I can't access the main UI as it forward automatically to the local domain (unraid.privateFQDN.org) and it stops there. dockers on the unraid server (using the IP address) connect perfectly. Edit: Found the fix the the issue, not sure why my config is causing it - but the scenario here is Asymmetric Routing. The solution is to enable "Bypass firewall rules for traffic on the same interface" under System/Advanced/Firewall & NAT: That fix both of the issues described above.

same problem here with 6.9.1, my windows 10 VM is unusable....really slow, really anoying semm to be solved with unraid tips trick => CPU Scaling Governor was on save, put it "on demand"

Thanks for this Rich. I'm running BigSur and noticed I couldn't move to /bin as you mentioned. I ran the mv command with /usr/local/bin and it appeared to work however I didn't yet have a bin folder in that location so it seems it moved the iperf3 tool there and renamed it to bin. Once I figured this out, I deleted it, created the bin directory and then ran the command again and it moved it as expected. Just thought I would mention this in case anyone else had the same experience.

/usr/local/bin seems to be the better location for macOS BigSur, due to System Integrity Protection on /bin.

Option 2 seems easiest, created the following script below and set it to run every 5 min using the "Users Scripts" plugin #!/bin/bash docker exec -u www-data Nextcloud php -f /var/www/html/cron.php exit 0 Thanks!