[[Support] Partition Pixel - Chia]

Looking for some advice. My current Unraid array already has 36 drives so its at the Unraid capacity for drives. I have an additional 12 drives that I'm looking to use only for Chia plots that are sitting in my unassigned drives. I either was thinking of passing them all through as individual plot locations to the container (creating a separate parameter for each, etc.) or passing them all through to a VM. I am just looking to run the full node and harvester on my unraid server and have my other servers be plotting and moving to the plot locations.

My two concerns I have is how the plotters on my other servers will know which drive has free space out of the 12 and managing those sound like a pain. I was considering using Stablebit DrivePool in a windows VM to have all the drives balanced and accessible from a single share and have the full node and harvester running on the same windows VM. That way my plotters will only need to write to a single share.

 

What would you guys do with this setup?

[[Plugin] CA Fix Common Problems]

On 4/10/2021 at 1:14 PM, Squid said:

Fixed

 

 

Also on today's update, a new warning will be issued under 2 circumstances:

 

The string xmrig is found in your go file, or a process named xmrig is running.

 

If it's found in your go file, then most likely your entire system has been compromised and a hacker has edited your go file to automatically install xmrig on every boot

 

If it's a process, two scenarios exist

1. You're purposely running it.  In which case this warning is safe to ignore
2. You've possibly installed a compromised container via a random dockerHub search that is masking the fact that it's installing xmrig as it's primary purpose.

 

For reference, xmrig is mining software, and since malware, viruses, ransomware etc are now passe, Compromising a system to instead mine for bitcoin is the hack of choice.

 

Had the xmrig warning appear. I do not do any mining on my unraid system at all. After running FCP manually it did not return that warning again. Is there anything I can do to check my container images to see if any might be triggering xmrig to be running? What would your recommendations be?

EDIT: here are the only lines I can seem to find in the diagnostics that reference it -

### [PREVIOUS LINE REPEATED 1 TIMES] ###
May  3 15:59:00 UnraidCore root: FCP Debug Log: root     32685  0.0  0.0   3848  2884 ?        S    15:58   0:00 sh -c ps -aux | grep -i xmrig
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May  3 15:59:00 UnraidCore root: FCP Debug Log: root     32686  0.0  0.0   3848  2952 ?        S    15:58   0:00 sh -c ps -aux | grep -i xmrig
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May  3 15:59:00 UnraidCore root: FCP Debug Log: root     32688  0.0  0.0   3260   768 ?        S    15:58   0:00 grep -i xmrig
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May  3 15:59:00 UnraidCore root: FCP Debug Log: root     32690  0.0  0.0   3260   832 ?        S    15:58   0:00 grep -i xmrig
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May  3 15:59:00 UnraidCore root: Fix Common Problems: Warning: Possible mining software running
### [PREVIOUS LINE REPEATED 1 TIMES] ###

unraidcore-diagnostics-20210503-1718.zip

[VGA Controller listed as: Intel corporation device 9bc8 (rev 03)]

I am having this issue as well except I am missing it for UHD P630 since I have a Intel E-2288G. Assuming this is happening for all of Coffee Lake CPUs. I'm also on the most recent beta25.