Struck
-
Posts
88 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Struck
-
-
On 2/29/2024 at 9:50 PM, guy.davis said:
Machinaris v2.2.0 is now available:
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.
I am having trouble updating to 2.2.0
I am still on 2.1.4 and the docker page shows that there is no update, and the docker being not available.
-
I finally got a breakthrough.
I tried many different settings.
But when I switched the USB Controller from 2.0 EHCI to 3.0 (qemu XHCI) It suddently appeared as a bootable device
I didn't try this earlier, since i expected 2.0 to work better for boot than 3.0.
Thanks for all your guys help so far
-
3 minutes ago, SimonF said:
What about the vnc console? does it just show the uefi boot?
-
5 minutes ago, SimonF said:
What does the console show?
Cant really find anything about the USB in the Logs for the VM:
Unraid Host logs tells me this:
-
I tried creating the USB with the manual way, of, but I still have the same error.
-
16 minutes ago, SimonF said:
Are you using ovmf for the bios and have renamed the efi- directory on flash to efi?
I actually used the USB media creation tool to create the media, but altered the drive label and edited the files afterwards,
Maybe this is not the way to do it.
EFI folder is named as is default, when using the media creation tool.
-
Just now, itimpi said:
Is the USB drive the same model as that used by the host? It is much more convenient if it is not.
Host is using a HP w165 usb,
VM is using a Sandisk extreme USB.
So different vendor and model. -
2 minutes ago, SimonF said:
How are you mapping the USB device to the VM?
Using the USB Manager shown in the video.
I have also tried to assign it using the normal method in the VM settings.
-
1 hour ago, SimonF said:
You need to change the 2nd USB to be a different volume name and change the syslinux config with the label name.
append unraidlabel=UNRAID-VM initrd=/bzroot
Thanks for the informatiopn.
This solved my initial problem.
I followed the video, but the USB does not appear as a boot device in the VM.
I edited the files on thje USB drive, and ran the make_bootable file without any problems.
-
Hello everyone.
I am trying to combine two unraid machienes I have been running.
But since Unraid still does not support multiple arrays in a single install, I am trying to run the second unraid in a VM.
But when i plug a new unraid USB into the already running system, the USB is not available to be assigned to a VM.
As unassigned disks plugin, says the USB is "array"
The Log tells me what happens:
It seems like the existing unraid picks up the USB unraid, and locks the device, as it now is the active license.
The USB i am using is using a new blank unraid 6.10.3 install, until i know if this would work or not.
I already own the two unraid pro licenses.
The host unraid system is currently running Unraid 6.9.2
I can post diagnostics, but i don't know if that would help anyway.
-
I realize i never replied to this topic.
I tried reformattig the disk, and it seems to be working.
But i later changed the filesystem to xfs, and ever since i haven't had a problem with corrupt data or full disk.
-
Just to confirm.
I don't HAVE to use a cold wallet address, for chia and alt-coins to work properly, right?
My Flax farm, haven't caught any blocks for 5-6 weeks at this point. My estimated time to win is 8-10 days.
But i know that is only an estimate, and should count on that.
My current setup, does not use a cold address for rewards, and i have about 40 XFX already, but hasn't gained any for the last month and a half.
Machinaris does not report any problems, Only have a few (0-3( skipped SP's a day. and a search time average, under 0.5s.
-
Hi
I have the past two days got an error that indicated my cache drive is out of space. This apparently causes the system to stop functioning correctly. The docker service turns offline, and some of the cpu cores are pinned at 100%.
The sys logs says this:
Nov 4 07:59:24 ChiaTower kernel: BTRFS info (device sdo1): leaf 139039850496 gen 76585 total ptrs 0 free space 16283 owner 18446744073709551610 Nov 4 07:59:24 ChiaTower kernel: BTRFS critical (device sdo1): not enough freespace need 48992 have 16283 Nov 4 07:59:24 ChiaTower kernel: ------------[ cut here ]------------ Nov 4 07:59:24 ChiaTower kernel: kernel BUG at fs/btrfs/ctree.c:4814! Nov 4 07:59:24 ChiaTower kernel: invalid opcode: 0000 [#1] SMP PTI Nov 4 07:59:24 ChiaTower kernel: CPU: 11 PID: 28875 Comm: shfs Not tainted 5.10.28-Unraid #1 Nov 4 07:59:24 ChiaTower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X99M Extreme4, BIOS P3.10 06/13/2016 Nov 4 07:59:24 ChiaTower kernel: RIP: 0010:setup_items_for_insert+0xe1/0x294 Nov 4 07:59:24 ChiaTower kernel: Code: 39 f0 73 28 48 89 ef e8 f9 8c 00 00 48 89 ef e8 83 d9 ff ff 48 8b 7c 24 08 44 89 f2 48 c7 c6 de f3 d8 81 89 c1 e8 e3 82 49 00 <0f> 0b 48 8d 7c 24 40 48 89 ee e8 6b 97 ff ff 44 3b 64 24 20 0f 84 Nov 4 07:59:24 ChiaTower kernel: RSP: 0018:ffffc90002b03b10 EFLAGS: 00010296 Nov 4 07:59:24 ChiaTower kernel: RAX: 0000000000000000 RBX: 0000000000003f9b RCX: 0000000000000027 Nov 4 07:59:24 ChiaTower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88848fcd8920 Nov 4 07:59:24 ChiaTower kernel: RBP: ffff88810cd498c0 R08: 0000000000000000 R09: 00000000ffffefff Nov 4 07:59:24 ChiaTower kernel: R10: ffffc90002b038c0 R11: ffffc90002b038b8 R12: 0000000000000000 Nov 4 07:59:24 ChiaTower kernel: R13: 000000000000ab10 R14: 000000000000bf60 R15: ffff8881037e0000 Nov 4 07:59:24 ChiaTower kernel: FS: 000014ece30f0700(0000) GS:ffff88848fcc0000(0000) knlGS:0000000000000000 Nov 4 07:59:24 ChiaTower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 4 07:59:24 ChiaTower kernel: CR2: 00001527d203ca24 CR3: 000000014a2e4005 CR4: 00000000001706e0 Nov 4 07:59:24 ChiaTower kernel: Call Trace: Nov 4 07:59:24 ChiaTower kernel: btrfs_insert_empty_items+0x65/0x77 Nov 4 07:59:24 ChiaTower kernel: copy_items.isra.0+0xe2/0x358 Nov 4 07:59:24 ChiaTower kernel: ? read_extent_buffer+0x1d/0x91 Nov 4 07:59:24 ChiaTower kernel: ? btrfs_set_path_blocking+0x1f/0x3e Nov 4 07:59:24 ChiaTower kernel: ? btrfs_search_forward+0x23d/0x274 Nov 4 07:59:24 ChiaTower kernel: btrfs_log_inode+0x597/0xab6 Nov 4 07:59:24 ChiaTower kernel: btrfs_log_inode_parent+0x25b/0x901 Nov 4 07:59:24 ChiaTower kernel: ? slab_post_alloc_hook+0x1e/0x14a Nov 4 07:59:24 ChiaTower kernel: ? _cond_resched+0x1b/0x1e Nov 4 07:59:24 ChiaTower kernel: ? wait_current_trans+0xbc/0xda Nov 4 07:59:24 ChiaTower kernel: ? kmem_cache_alloc+0x108/0x130 Nov 4 07:59:24 ChiaTower kernel: ? join_transaction+0x9d/0x3a3 Nov 4 07:59:24 ChiaTower kernel: btrfs_log_dentry_safe+0x36/0x4a Nov 4 07:59:24 ChiaTower kernel: btrfs_sync_file+0x250/0x340 Nov 4 07:59:24 ChiaTower kernel: do_fsync+0x2a/0x44 Nov 4 07:59:24 ChiaTower kernel: __x64_sys_fsync+0xb/0xe Nov 4 07:59:24 ChiaTower kernel: do_syscall_64+0x5d/0x6a Nov 4 07:59:24 ChiaTower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Nov 4 07:59:24 ChiaTower kernel: RIP: 0033:0x14ecf13f5a8b Nov 4 07:59:24 ChiaTower kernel: Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 43 f7 ff ff 8b 7c 24 0c 41 89 c0 b8 4a 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 81 f7 ff ff 8b 44 Nov 4 07:59:24 ChiaTower kernel: RSP: 002b:000014ece30efc70 EFLAGS: 00000297 ORIG_RAX: 000000000000004a Nov 4 07:59:24 ChiaTower kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000014ecf13f5a8b Nov 4 07:59:24 ChiaTower kernel: RDX: 000014ece30efd60 RSI: 0000000000000001 RDI: 000000000000001e Nov 4 07:59:24 ChiaTower kernel: RBP: 000014ece30efcc0 R08: 0000000000000001 R09: 000014ecc001c724 Nov 4 07:59:24 ChiaTower kernel: R10: 000000000046ab58 R11: 0000000000000297 R12: 000014ecc0010600 Nov 4 07:59:24 ChiaTower kernel: R13: 0000000000000001 R14: 00000000000000ac R15: 000014ece30efd60 Nov 4 07:59:24 ChiaTower kernel: Modules linked in: veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod nct6775 hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables e1000e alx mdio intel_wmi_thunderbolt mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper rapl intel_cstate intel_uncore i2c_i801 input_leds i2c_smbus i2c_core ahci led_class aacraid libahci wmi button [last unloaded: e1000e] Nov 4 07:59:24 ChiaTower kernel: ---[ end trace d8547447692a8044 ]--- Nov 4 07:59:24 ChiaTower kernel: RIP: 0010:setup_items_for_insert+0xe1/0x294 Nov 4 07:59:24 ChiaTower kernel: Code: 39 f0 73 28 48 89 ef e8 f9 8c 00 00 48 89 ef e8 83 d9 ff ff 48 8b 7c 24 08 44 89 f2 48 c7 c6 de f3 d8 81 89 c1 e8 e3 82 49 00 <0f> 0b 48 8d 7c 24 40 48 89 ee e8 6b 97 ff ff 44 3b 64 24 20 0f 84 Nov 4 07:59:24 ChiaTower kernel: RSP: 0018:ffffc90002b03b10 EFLAGS: 00010296 Nov 4 07:59:24 ChiaTower kernel: RAX: 0000000000000000 RBX: 0000000000003f9b RCX: 0000000000000027 Nov 4 07:59:24 ChiaTower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88848fcd8920 Nov 4 07:59:24 ChiaTower kernel: RBP: ffff88810cd498c0 R08: 0000000000000000 R09: 00000000ffffefff Nov 4 07:59:24 ChiaTower kernel: R10: ffffc90002b038c0 R11: ffffc90002b038b8 R12: 0000000000000000 Nov 4 07:59:24 ChiaTower kernel: R13: 000000000000ab10 R14: 000000000000bf60 R15: ffff8881037e0000 Nov 4 07:59:24 ChiaTower kernel: FS: 000014ece30f0700(0000) GS:ffff88848fcc0000(0000) knlGS:0000000000000000 Nov 4 07:59:24 ChiaTower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 4 07:59:24 ChiaTower kernel: CR2: 00001527d203ca24 CR3: 000000014a2e4005 CR4: 00000000001706e0 Nov 4 08:59:23 ChiaTower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog
Where we in the first lines see this:
Nov 4 07:59:24 ChiaTower kernel: BTRFS critical (device sdo1): not enough freespace need 48992 have 16283Which means my drive sdo does not have enough space. That drive is mapped to my cache drive.
An Intel 480GB SSD, which ONLY holds my docker and app data for 3 dockers.
Two of these dockers have a high disk usage, but nowhere near 480GB, they will also write to the disk all the time, but not at full speed. The dockers are: krusader, Machinaris, and Machinaris-flax. Which are used as chia farming and flax farming
Unraid says i have used 102GiB of space on the disk.
Is the disk bad or am i experiencing another problem?
I have lots of spare disks of the same type and size, so i can swap it, if needed.Currently i have 2 ssds as UD, one of which i have used previously as my cache disk, but it appeared to have some problems, where btrfs whould be corrupted a couple of times. That issue can be found here:
But i have not experienced that issue with the replaced cache disk.
-
1 hour ago, TheNotoriousFlow said:
hi @guy.davis,
since the update today i have 2 issues so far.
I got two chia tabs in the connections tab and an error message appears on clicking to connections:
also 2 tabs of chia appear when i click on blockchain.
When i click on wallet, i see all of a sudden two wallets which seem to be the same. One is outdated (not synced) with the sync date when i updated the container. the other one seems to be synched with current date.
any advise? i did follow the upgrade advisory.
regards
Florian
14 minutes ago, DaPedda said:Great,.... after Update my Farming is offline 😞
Please read the notes on updating from 0.5.x to 0.6.0 for unraid docker.
-
1
-
-
1 hour ago, guy.davis said:
Good day. Machinaris v0.6.0 is now available with support for many more blockchain forks:
- 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.Core enhancements to underlying components include:
- Plotman - enhancement to support plotting for Chives via Madmax.
- Chiadog - enhancement to support monitoring of other blockchain forks.
Really big thanks to all those that helped review and provide feedback on this big step forward for Machinaris!Unraid users of Machinaris, please follow the upgrade guide:
Thanks for the new version.
With a little finegeling i managed to get it to work with flax.
-
1
-
-
2 hours ago, guy.davis said:
Probably not critical as this is about to change in v0.6.0. By the way, which version of Machinaris are you running? See version at bottom of each page in Machinaris WebUI. Thanks.
Yeah, i see i gained a block reward, so it must still be farming. but flexdog is likely not running, and also not providing allerts and daily updates. (This has never worked for flax, for me)
I am on Machinaris 0.5. which seems to be the newest in this present time. -
I get the following error from flexdog.
Is that something i should be conserned about?
On the summary page, flax and chia is still listed as Farming: active[2021-10-11 08:53:36] [ INFO] --- Starting Flaxdog (v0.6.0-3-g8867a71) (main.py:54) Traceback (most recent call last): File "/flaxdog/main.py", line 111, in <module> init(conf) File "/flaxdog/main.py", line 57, in init flax_logs_config = config.get_flax_logs_config() File "/flaxdog/src/config.py", line 35, in get_flax_logs_config return self._get_child_config("flax_logs") File "/flaxdog/src/config.py", line 22, in _get_child_config raise ValueError(f"Invalid config - cannot find {key} key") ValueError: Invalid config - cannot find flax_logs key -
6 hours ago, trurl said:
How long did you let it run?
Not long enough.
2 passes, like 4 hours.
-
On 8/7/2021 at 2:54 PM, Robc390 said:
can the card run in IT mode?
I am looking to use this card as well, and I've read a lot of problems using a card in raid mode.All drives are passed to the OS by individual drives, and SMART data is available.
Have not tried running a raid mode on the card.
-
Memtest didn't find anything.
Extended SMART test did not find any issues either.
I have not tried replacing the drive yet. I will do that after the weekend i guess
-
4 minutes ago, JorgeB said:
Array is XFS, btrfs is much more sensitive to bad RAM, though if that is the problem you'll also get data corruption on the array, just undetected.
Okay,. Thanks i will try it after the extended smart test is done.
As a side note, the cache disk mounted as normally after a reboot.
-
18 minutes ago, trurl said:
You could run an extended SMART test on that SSD. My guess is some other problem is causing corruption. Have you done memtest?
I will run an extended SMART test after reboot.
I have now inserted a new SSD, that is supposed to replace the one i currently use.
I will try memtest later, but i haven't had any problems before i installed the SSD. The array is unaffected of this problem it seems
-
I used the instructions to retore the data,
formatted the drive and copied the data back afterwards.
It worked for less than three days.
Now the issue is the same.
The log is filled with stuff like this:
Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 Aug 31 04:29:37 ChiaTower kernel: BTRFS warning (device sdm1): csum failed root 5 ino 12305 off 15759626240 csum 0x21417709 expected csum 0x00000000 mirror 1 Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 5, gen 0 Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): parent transid verify failed on 8343076864 wanted 3304 found 3233 Aug 31 04:29:37 ChiaTower kernel: BTRFS info (device sdm1): no csum found for inode 12305 start 15759699968 Aug 31 04:29:37 ChiaTower kernel: BTRFS warning (device sdm1): csum failed root 5 ino 12305 off 15759699968 csum 0x108cc45f expected csum 0x00000000 mirror 1 Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 6, gen 0 Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): parent transid verify failed on 8343076864 wanted 3304 found 3233 Aug 31 04:29:37 ChiaTower kernel: BTRFS info (device sdm1): no csum found for inode 12305 start 15759708160 Aug 31 04:29:37 ChiaTower kernel: BTRFS warning (device sdm1): csum failed root 5 ino 12305 off 15759708160 csum 0x7d0b155f expected csum 0x00000000 mirror 1 Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): parent transid verify failed on 8343076864 wanted 3304 found 3233 Aug 31 04:29:37 ChiaTower kernel: BTRFS info (device sdm1): no csum found for inode 12305 start 15759736832 Aug 31 04:29:37 ChiaTower kernel: BTRFS warning (device sdm1): csum failed root 5 ino 12305 off 15759736832 csum 0xabb5631a expected csum 0x00000000 mirror 1 Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): parent transid verify failed on 8343076864 wanted 3304 found 3233 Aug 31 04:29:37 ChiaTower kernel: BTRFS info (device sdm1): no csum found for inode 12305 start 15760031744 Aug 31 04:29:37 ChiaTower kernel: BTRFS warning (device sdm1): csum failed root 5 ino 12305 off 15760031744 csum 0xb842b40e expected csum 0x00000000 mirror 1 Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 9, gen 0 Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): parent transid verify failed on 8343076864 wanted 3304 found 3233 Aug 31 04:29:37 ChiaTower kernel: BTRFS info (device sdm1): no csum found for inode 12305 start 15759298560 Aug 31 04:29:37 ChiaTower kernel: BTRFS warning (device sdm1): csum failed root 5 ino 12305 off 15759298560 csum 0xff2de314 expected csum 0x00000000 mirror 1 Aug 31 04:29:37 ChiaTower kernel: BTRFS error (device sdm1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0 Aug 31 04:30:13 ChiaTower kernel: verify_parent_transid: 10 callbacks suppressed Aug 31 04:30:13 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:30:13 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:30:44 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:30:44 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:31:15 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:31:15 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:31:46 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:31:46 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:32:18 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:32:18 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:32:49 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:32:49 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:33:20 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:33:20 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764 Aug 31 04:33:51 ChiaTower kernel: BTRFS error (device loop2): parent transid verify failed on 4708515840 wanted 203356 found 202764
And my guess is that if i try to reboot the machine the cache drive parition cannot be mounted.
Even though I can access the cache drive fine before the reboot.
Is the drive bad?
I have multiple of these drives, so i can try and replace it.Would i be having less issues if i run multiple of them in the cache pool?
-
Diagnostics attached
the restart also triggered a parity sync. I don’t know why this is, since the array seems to be unaffected of this problem.
[Support] Machinaris - Chia cryptocurrency farming + Plotman plotting + Unraid WebUI
in Docker Containers
Posted · Edited by Struck
Okay. Thank you for the answer.
I see forward to a new release, whenever it is ready.