I'm trying now without the -a because that doubles the memory usage.

I just ran a the mdcct plotter on a 3 TB hard drive but the process says it was killed after a couple of hours of processing? Why did that happen? Did I run out of memory? Can I restart where I left off?

This is what my terminal says:

root@cd4c836402f5:/mnt/disk2-3TB# plot -k 145xxxxxxxxxxx82820 -x 1 -d ./ -a                   
Async mode set.
Using SSE2 core.
Creating plots for nonces 851589091774395047 to 851589091785422627 (2892 GB) using 15982 MB memory and 1 threads
0 Percent done. 610 nonces/minute, 300:25 leftKilled
root@cd4c836402f5:/mnt/disk2-3TB# 

@haitch Why did you decide to strip the data instead of having a plot for each disk? Thank you all the information! I have about 6TB free right now.

@haitch Is only some of the plot read to create a valid block when mining?

What type of ZFS configuration do you have? I assume you are not using any redundancy.

What happens if a part of the disk is unreadable during mining? Does the plot need to be created from scratch? I'm thinking about setting up ZFS filesystem to detect failures. Will detecting failures make a difference for mining?