sota

didn't work. disk makes some evil click noises at startup, then dies (spins down.) tried a new disk in the MD1000... doesn't recognize. there's plots being loaded onto one of the other drives right now, so I can't do a restart on the system yet. wondering now if either the slot has died, or the little adapter board (I forget what they're called) has toasted itself.

freezer trick sometimes gets drives to behave. other times, not.

yea i picked them up to be primarily used as cold storage for my security cameras, but figured since I have time before I'd use them all i'd toss a couple into chia use.

tossed it in the freezer, see if that gets it to come alive, at least long enough to maybe copy the plots off it. $1260 for 40 4TB drives, bought as-is. if this one is toast that makes #2 of the lot that have died.

... and I just had a 4TB drive *** itself apparently.

looks like i'm the ./btrfs bloated club now too. for a less than filthy casual such as myself, what's the best way to cure this, hopefully without having to stop the docker service, or deleting the docker.img file? i've reasons for not having certain containers to not be down for long, if at all.

mad max took 15,557 seconds to complete a plot on one of the servers, using 2 HDDs as temp1 and temp2. that's not a stellar metric. I could try and make a couple RAID0 arrays (thinking a 2/6 or 3/5, with the latter as temp2).

I downloaded that compiled windows version.

and regarding pricing, i'm of the opinion that this is THE time to get as many plots up and running. lower coin price will naturally mean more people will bail out. that can only improve the odds for those that remain. I doubt we'll see any major farms go belly up, but who knows? if their money backers get nervous, they could start pulling plugs. I'm going to stay the course, get the 15-block of 4TB drives I've slated for plots done, then re-evaluate the way they're powered up/connected (this MD1000 is a goddamn power HOG) and plan on just letting the plots run for a decent period of time.

well this has been a not fun time. went to check stuff this morning, and found the farm "rack" off. tripped the GFCI on the circuit everthing was plugged into. swell. also, i'm having problems running madmax; testing on one of the servers, it randomly dies in the middle of a plot. no errors shown on the screen to tell me why.

well the trick of it is, I found a ramdisk windows tool I can use, but the only way it's viable is to stuff the 144GB of ram back into the single machine. I can reconfigure the disks into arrays easily enough.

playing with 'max now. to give it everything I'd need to shut down all 3 plotters and put everything back into the one machine, so i'm holding off on that for the moment.

guess I need to look at using madmax.

be interesting to see what the fallout from this is.

Caught plotting error: bad allocation seems to be the bane of my existence now. getting that error at random times on 2 of the 3 plotter machines. bad part is it leaves lint that can clog up the disk, preventing a plot from completing. just added code to the script to flush the disk after every plot run, successful or not.

so what's the update that mine wants me to install?

you see how far chia has slid? actually think if it went down by half from now, it would be good. would cause a bunch of people to bail I bet. $250 chia might cause a nice sized contraction of netspace. also, at 194 plots now.

right now, i'm going to just plot this 15x4TB group solo, and let it run for a while most likely.

in unraid, it should show up. in windows, I have no clue.

ok. added *another* script to my collection (monitor). folders: temp\# ... individual drives where a single plot is processed. harvest... where each plot dumps its final file locally, before it's moved to the farm computer scripts: wrapper... starts all the other scripts (monitor, mover, initchia). one and done. monitor... checks the harvest folder (every 60 seconds) and suspends (.\pssuspend.exe robocopy.exe) the mover if a TMP file appears (keeps from thrashing the disk, which MASSIVELY impacts both final file creation and network transfers), and resumes the mover if not. mover... checks the harvest folder (every 300 seconds) for the presence of TMP or PLOT files, and starts moving them (robocopy) when only PLOT files exist. initchia... kicks off (every 1000 seconds) the individual plotter scripts (plotschia) for each of the temp\# drives. one and done. plotschia... keeps a plot going on each temp\# drive, and processes the log file generated.

don't forget though, if you're in the back half of the disk, its data transfer rates slow down.

ah, I see. I think now that I have my scripts in a pretty stable state, i'm just going to run with them and see how things go. IF, I don't manage to mess anything else up any time soon, it looks like i'm doing about 20 plots per day, with the 3 plotter machines.

how does it handle the fact that not every plot is taking the same amount of time, and they seem to be random as to which process/processor it touches.

Other than the "virgin" kick off, I'm not bothering with trying to control staggering. I'm going to run 8/8/4 for now, let them auto cycle. Then there's the "incident" from last night where the storage drive on the farm filled up, and I hadn't re-pointed the 'latest' share, so that the all 3 machines were "backed up" a little. I'm going for Chaos Theory now.

CHIA1.11.20210603.2224.log 6/3/2021 22:24:34 CHIA1.12.20210603.2241.log 6/3/2021 22:41:12 CHIA10.11.20210603.2253.log 6/3/2021 22:53:54 CHIA1.13.20210603.2257.log 6/3/2021 22:57:54 CHIA10.12.20210603.2310.log 6/3/2021 23:10:30 CHIA1.14.20210603.2314.log 6/3/2021 23:14:33 CHIA10.13.20210603.2327.log 6/3/2021 23:27:12 CHIA1.15.20210603.2331.log 6/3/2021 23:31:13 CHIA10.14.20210603.2343.log 6/3/2021 23:43:51 CHIA1.16.20210603.2347.log 6/3/2021 23:47:53 CHIA10.15.20210604.1200.log 6/4/2021 00:00:31 CHIA11.11.20210604.1202.log 6/4/2021 00:02:50 CHIA1.17.20210604.1204.log 6/4/2021 00:04:34 CHIA10.16.20210604.1217.log 6/4/2021 00:17:11 CHIA11.12.20210604.1219.log 6/4/2021 00:19:28 CHIA1.18.20210604.1221.log 6/4/2021 00:21:14 CHIA10.17.20210604.1233.log 6/4/2021 00:33:51 CHIA11.13.20210604.1236.log 6/4/2021 00:36:08 CHIA10.18.20210604.1250.log 6/4/2021 00:50:32 CHIA11.14.20210604.1252.log 6/4/2021 00:52:48 CHIA10.11.20210604.1703.log 6/4/2021 17:03:34 CHIA1.11.20210604.1731.log 6/4/2021 17:32:00 CHIA11.11.20210604.1811.log 6/4/2021 18:11:16 CHIA1.17.20210604.1926.log 6/4/2021 19:26:30 CHIA11.12.20210604.1949.log 6/4/2021 19:49:40 CHIA11.13.20210604.1210.log 6/4/2021 20:10:23 CHIA10.12.20210604.1216.log 6/4/2021 20:16:39 CHIA11.14.20210604.1224.log 6/4/2021 20:24:50 CHIA10.13.20210604.1250.log 6/4/2021 20:50:22 CHIA1.12.20210604.1251.log 6/4/2021 20:51:24 CHIA10.14.20210604.2323.log 6/4/2021 23:24:47 the drift between threads are hilarious.