TexasUnraid

Had a strange thought after reading a youtube comment about people selling their old plots when moving to the new pool plots. I would consider selling my drives + plots + seed if there was a market for it. I mean if someone wanted ~20TB worth of drives + plots for ~$250, I think I would let it go and hope hard drive prices get back to normal in the coming months then re-purchase a new 14tb drive with the money. Loose a bit of space but save ~100w worth of power and 16 bays in my server. Someone would be silly to buy it though so doubt it would happen.

Looking forward to the pooling version of Machinaris with madmax plotter. Figure I will hold off on replotting until it is ready since the forks are not ready for the pooling plots yet anyways.

If you are not having speed issues then just roll with it. My file situation for backups is a lot differnt then most, I have around 10 million small files that has to be sorted through and it takes FOREVER over SMB. Doing it directly takes a fraction of the time.

lol, yeah pretty close to mine. 8x 12tb drives for my main server and planning to use these 14tb drives as backups. Although I will be using the dirsyncpro docker to handle the sync. It is MUCH faster then using a windows VM in my testing (I also tried that first and it was stupid slow with a bunch of small files). Might look into the dirsyncpro docker, it has a GUI and works great. The drives also work natively with unassigned devices with unraid which I find a lot easier to deal with. Plus I like having all my drives encrypted, just provides that piece of mind that my data won't fall into someone else's hands. I also use BTRFS for all the drives, the check summing is really nice so you don't have to worry about silent data corruption.

lol, ditto. It costs nothing to farm them now, so keep doing it and see if I get lucky down the road. Chia itself it almost not worth the hassle at the market value right now unless like us you already had the hardware and you don't care about it. Most of these drives I simply do not care if they live or die. I have moved to 12TB+ for my real data. Speaking of which, I ordered some 14TB drives back in april for $200 each and they are STILL on backorder. Got an email today that they don't expect them before October! I actually need those drives to get a proper backup of my unraid server.

Interesting, thanks for the heads up, will try that out as well. I am waiting for things to settle out a bit to start plotting. Going to move over to the new plots just not in a major rush to do it. Want to give the forks time to implement the changes so I can keep farming them all lol. I did figure out what seems to be causing a slowdown when starting blockchains, seems my antique 250gb drive that is lucky to get ~30mb/s is slowing everything down a lot. Gonna remove that one from the raid at some point and see if things speed up. That drive stays pegged at 100% during startup of a blockchain.

Cool, so official pools are now live? Guess I need to spin up my systems for some plotting.

I am not sure, I had to take my farming rig offline this morning to move some hardware around so won't know for awhile yet.

Looks like I have: 20 spare 4500 cgn 10 xfx 2 xgj 8 xse And I think around 0.15 xch Numbers look about right considering you have more plots then me.

Ok, long story short, after a long road of testing and trial and error I finally figured out how to deal with the excessive writes to the SSD caused by dockers. More then a few users have noticed that their SSD's have used up all or most of their life recently and some have died as well. The commands and setup is pretty simple. The hardest part is having to do each container individually as it takes a lot of time that way. I think It should be possible to turn these commands into a plugin that could make it MUCH simpler without a lot of hassle. You can see the full guide on the commands and process to stop the excessive docker writes here: A plugin would just need to: setup the inotifywait logging and let the user figure out the problem containers. Have check boxes to add each of the above docker fixes to the docker templates Setup the ramdisk for appdata handle the rsync'ing of the appdata to and from the ramdisk at a user selected interval unmount the ramdisk at shutdown I have no clue how the plugin system works or even where to start but someone that knows what they are doing should be able to figure it out without a lot of hassle I would think. Just an idea for a useful plugin IMHO.

So it has been a few more days and writes are holding steady at ~11-12gb/day. I am calling this a success!

I collect old SSD's for times like this lol. got several 128gb drives I use in place of USB drives and for random boot drives etc.

Something is up with the setup, if you HDD usage is pegged I think a lot of your issues lie there. I have none of these issues. Start them up by clicking the icons and it does take a bit for them to scan the plots / sync up and start farming but after that it has run for a week+ without a single hiccup. All settings are stock as well, have not had to do anything but enter my minomic and the paths to the plots.

Possible I suppose, I am running off an old 128gb ssd.

I have used sandboxie for years, works great although changing ports is not something I remember seeing an option for.

Never heard of Influxdb, it looks like just a database, how does it collect writes? Sounds interesting. Got a link to what you are using? Me I am just monitoring the raw LBA writes from the SSD smart data, this is the only way to see the actual writes to the SSD, every other method will not correctly account for things like write amplification. The exact command varies depending on how the drive calculates the LBA's but here is the script I use or just enter the data into this site and play with the numbers until the writes look right lol. https://www.virten.net/2016/12/ssd-total-bytes-written-calculator/ As you can see the samsung, liteon and sandisk all use different calculations for the LBA's to MB #!/bin/bash #description=Basic script to display the amount of data written to SSD on drives that support this. Set "argumentDefault" to the drive you want if you will schedule this. #argumentDescription= Set drive you want to see here #argumentDefault=sdm #path to save logs DIR=/mnt/user/Backup/Smart\ reports/SSD\ TBW\ Logs ### Argument selected drive, replace argument above with label of drive you want TBW calculated for ### DRIVE1="$1" DRIVE1NAME=Argument_SSD #hard coded Samsung compatible LBA reporting drives DRIVE2=disk/by-id/ata-Samsung_SSD_860_EVO_1TB_ DRIVE2NAME=Samsung-_1TB-860_EVO_1 DRIVE3=disk/by-id/ata-Samsung_SSD_860_EVO_1TB_ DRIVE3NAME=Samsung-_1TB_860_EVO_2 #Sandisk compatible LBA reporting drives DRIVE10=disk/by-id/ata-SanDisk_ DRIVE10NAME=Sandisk_256GB_ssd #liteon compatible LBA reporting drives DRIVE11=disk/by-id/ata-LITEONIT_LCT- DRIVE11NAME=Liteon_128GB_SSD echo ---------------- First drive you want to log from argument "$1" ---------------- sudo smartctl -A /dev/"$1" |awk ' $0 ~ /Power_On_Hours/ { poh=$10; printf "%s / %d hours / %d days / %.2f years\n", $2, $10, $10 / 24, $10 / 24 / 365.25 } $0 ~ /Total_LBAs_Written/ { lbas=$10; bytes=$10 * 512; mb= bytes / 1024^2; gb= bytes / 1024^3; tb= bytes / 1024^4; #printf "%s / %s / %d mb / %.1f gb / %.3f tb\n", $2, $10, mb, gb, tb printf "%s / %.2f gb / %.2f tb\n", $2, gb, tb printf "mean writes per hour: / %.3f gb / %.3f tb", gb/poh, tb/poh } $0 ~ /Wear_Leveling_Count/ { printf "%s / %d (%% health)\n", $2, int($4) } ' | sed -e 's:/:@:' | sed -e "s\$^\$/dev/"$1" @ \$" | column -ts@ # Get the TBW of /dev/s!db TBWSDB_TB=$(/usr/sbin/smartctl -A /dev/"$1" | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 * 512 / 1024^4 }') TBWSDB_GB=$(/usr/sbin/smartctl -A /dev/"$1" | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 * 512 / 1024^3 }') TBWSDB_MB=$(/usr/sbin/smartctl -A /dev/"$1" | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 * 512 / 1024^2 }') echo "TBW on $DRIVE1 $(date +"%d-%m-%Y %H:%M:%S") -->> $TBWSDB_TB TB, which is $TBWSDB_GB GB, which is $TBWSDB_MB MB." >> "$DIR/TBW_$DRIVE1NAME.log" echo echo ---------------- Samsung Compatible LBA $DRIVE2 ---------------- sudo smartctl -A /dev/$DRIVE2 |awk ' $0 ~ /Power_On_Hours/ { poh=$10; printf "%s / %d hours / %d days / %.2f years\n", $2, $10, $10 / 24, $10 / 24 / 365.25 } $0 ~ /Total_LBAs_Written/ { lbas=$10; bytes=$10 * 512; mb= bytes / 1024^2; gb= bytes / 1024^3; tb= bytes / 1024^4; #printf "%s / %s / %d mb / %.1f gb / %.3f tb\n", $2, $10, mb, gb, tb printf "%s / %.2f gb / %.2f tb\n", $2, gb, tb printf "mean writes per hour: / %.3f gb / %.3f tb", gb/poh, tb/poh } $0 ~ /Wear_Leveling_Count/ { printf "%s / %d (%% health)\n", $2, int($4) } ' | sed -e 's:/:@:' | sed -e "s\$^\$/dev/$DRIVE2 @ \$" | column -ts@ # Get the TBW of /dev/s!db TBWSDB_TB=$(/usr/sbin/smartctl -A /dev/$DRIVE2 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 * 512 / 1024^4 }') TBWSDB_GB=$(/usr/sbin/smartctl -A /dev/$DRIVE2 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 * 512 / 1024^3 }') TBWSDB_MB=$(/usr/sbin/smartctl -A /dev/$DRIVE2 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 * 512 / 1024^2 }') echo "TBW on $DRIVE2 $(date +"%d-%m-%Y %H:%M:%S") -->> $TBWSDB_TB TB, which is $TBWSDB_GB GB, which is $TBWSDB_MB MB." >> "$DIR/TBW_$DRIVE2NAME.log" echo echo ---------------- Samsung Compatible LBA $DRIVE3 ---------------- sudo smartctl -A /dev/$DRIVE3 |awk ' $0 ~ /Power_On_Hours/ { poh=$10; printf "%s / %d hours / %d days / %.2f years\n", $2, $10, $10 / 24, $10 / 24 / 365.25 } $0 ~ /Total_LBAs_Written/ { lbas=$10; bytes=$10 * 512; mb= bytes / 1024^2; gb= bytes / 1024^3; tb= bytes / 1024^4; #printf "%s / %s / %d mb / %.1f gb / %.3f tb\n", $2, $10, mb, gb, tb printf "%s / %.2f gb / %.2f tb\n", $2, gb, tb printf "mean writes per hour: / %.3f gb / %.3f tb", gb/poh, tb/poh } $0 ~ /Wear_Leveling_Count/ { printf "%s / %d (%% health)\n", $2, int($4) } ' | sed -e 's:/:@:' | sed -e "s\$^\$/dev/$DRIVE3 @ \$" | column -ts@ # Get the TBW of /dev/s!db TBWSDB_TB=$(/usr/sbin/smartctl -A /dev/$DRIVE3 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 * 512 / 1024^4 }') TBWSDB_GB=$(/usr/sbin/smartctl -A /dev/$DRIVE3 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 * 512 / 1024^3 }') TBWSDB_MB=$(/usr/sbin/smartctl -A /dev/$DRIVE3 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 * 512 / 1024^2 }') echo "TBW on $DRIVE3 $(date +"%d-%m-%Y %H:%M:%S") -->> $TBWSDB_TB TB, which is $TBWSDB_GB GB, which is $TBWSDB_MB MB." >> "$DIR/TBW_$DRIVE3NAME.log" echo echo ---------------- Sandisk LBA drive you want to log $DRIVE10 ---------------- #this uses a different LBA to byte calculation for sandisk SSD drives sudo smartctl -A /dev/$DRIVE10 |awk ' $0 ~ /Power_On_Hours/ { poh=$10; printf "%s / %d hours / %d days / %.2f years\n", $2, $10, $10 / 24, $10 / 24 / 365.25 } $0 ~ /Total_LBAs_Written/ { lbas=$10; bytes=$10; mb= bytes / 64 * 1000; gb= bytes / 64 ; tb= bytes / 64 / 1000; #printf "%s / %s / %d mb / %.1f gb / %.3f tb\n", $2, $10, mb, gb, tb printf "%s / %.2f gb / %.2f tb\n", $2, gb, tb printf "mean writes per hour: / %.3f gb / %.3f tb", gb/poh, tb/poh } $0 ~ /Wear_Leveling_Count/ { printf "%s / %d (%% health)\n", $2, int($4) } ' | sed -e 's:/:@:' | sed -e "s\$^\$/dev/$DRIVE10 @ \$" | column -ts@ # Get the TBW of /dev/s!db TBWSDB_TB=$(/usr/sbin/smartctl -A /dev/$DRIVE10 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 / 64 / 1000}') TBWSDB_GB=$(/usr/sbin/smartctl -A /dev/$DRIVE10 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 / 64 }') TBWSDB_MB=$(/usr/sbin/smartctl -A /dev/$DRIVE10 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 / 64 * 1000 }') echo "TBW on $DRIVE10 $(date +"%d-%m-%Y %H:%M:%S") -->> $TBWSDB_TB TB, which is $TBWSDB_GB GB, which is $TBWSDB_MB MB." >> "$DIR/TBW_$DRIVE10NAME.log" echo echo ---------------- Liteon LBA drive you want to log $DRIVE11 ---------------- #this uses a different LBA to byte calculation for liteon drives sudo smartctl -A /dev/$DRIVE11 |awk ' $0 ~ /Power_On_Hours/ { poh=$10; printf "%s / %d hours / %d days / %.2f years\n", $2, $10, $10 / 24, $10 / 24 / 365.25 } $0 ~ /Total_LBAs_Written/ { lbas=$10; bytes=$10; mb= bytes / 32 * 1000; gb= bytes / 32 ; tb= bytes / 32 / 1000; #printf "%s / %s / %d mb / %.1f gb / %.3f tb\n", $2, $10, mb, gb, tb printf "%s / %.2f gb / %.2f tb\n", $2, gb, tb printf "mean writes per hour: / %.3f gb / %.3f tb", gb/poh, tb/poh } $0 ~ /Wear_Leveling_Count/ { printf "%s / %d (%% health)\n", $2, int($4) } ' | sed -e 's:/:@:' | sed -e "s\$^\$/dev/$DRIVE11 @ \$" | column -ts@ # Get the TBW of /dev/s!db TBWSDB_TB=$(/usr/sbin/smartctl -A /dev/$DRIVE11 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 / 32 / 1000}') TBWSDB_GB=$(/usr/sbin/smartctl -A /dev/$DRIVE11 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 / 32 }') TBWSDB_MB=$(/usr/sbin/smartctl -A /dev/$DRIVE11 | awk '$0~/LBAs_Written/{ printf "%.1f\n", $10 / 32 * 1000 }') echo "TBW on $DRIVE11 $(date +"%d-%m-%Y %H:%M:%S") -->> $TBWSDB_TB TB, which is $TBWSDB_GB GB, which is $TBWSDB_MB MB." >> "$DIR/TBW_$DRIVE11NAME.log"

lol, yeah not rushing into it at this point. Stupid like scam or stupid like lazy?

I use hpool so guess that is why I have not had issues with spare.

wow, I see that. Explains why I could not get it to sync up. Hopefully they will fix that, not worth restarting the server right now so I guess I will give them a few days to sort that out before resorting to manually editing it.

lol, yeah chiagreen you get 500 for each block. Think I am up to 3000 or 4000 now. LTSC is what windows should be, no cortona, no edge, no bloat. I found the link to the ISO on reddit.

Yeah, it is still in alpha/beta right now and on the testnet. I am having issues getting it going right now so not surprised it is sharing ports. Might have to wait for them to sort that out to get it working.

Yeah, just normal gui launch. No particular order other then starting hpool/chia last and after the rest have fully started farming. I use LTSC for everything, so much more stable and so much less bloat then normal windows. I refuse to use any of the "normal versions" of windows 10.

Adding yet another blockchain to my system lol. Kinda a game at this point, how many blockchains can I get running on a single system. https://github.com/silicoin-network/silicoin-blockchain also decided to wait to do anymore plotting until the new plotting protocol is out, seems they are in the testnet stage, so 3 days without errors and it should move to mainnet. If I get all my servers plotting I should technically be able to plot ~10tb/day. Although I will also be burning ~1500w of power lol.

I am on the :test version of krusader and noticed it got an update. After updating my taskbar disappeared so that if a copy window pops up and I click away from it, I can't figure out how to pull it up again? I will just move back to the latest branch but figured I would let you know.

What is the windows setup on the systems? I am running windows 10 LTSC on the farming system and don't seem to be having any of these issues running full nodes on all 6 of them.