End of February 2024 update

The TR-004 units arrived. The plan is to put four of the 16TB WD drives into each of the TR-004's. I am experimenting with running the TR-004's off a Pi5, but that may turn out to be too slow.

I have a problem in that I have 10 x WD 16TB drives in my primary storage server and I had 4 spares. Two of those spares are now in one of TR-004's. One is off getting replaced under warranty and another spare seems to have died as well. I don't want to pull the drives from the primary storage server until I can generate more plots. Its currently too hot for that at the moment and you need to use an Nvidia GPU if you want compressed plots.

I got 10 x Seagate 20TB drives to put into the primary storage server which will increase its capacity and free up those WD 16TB drives but the weather is holding me back.


Comments

Post a Comment

Popular posts from this blog

That took a while

I had to copy the plots off the 8TB disks so I could swap them out of the storage machine (aka harvester). That took 2 days, even with a 10GbE network connection between the two storage servers. I then removed the 8TB drives, put the 5 x 16TB drives in and copied the plots back. That took another 2 days with it doing 240MB/sec for most of that, which would mean the storage server simply can't write the data any quicker. After that I fired up the full node which told me 121 out of the 252 plots couldn't be opened. I ended up deleting them and I will have to plot fresh ones. Clearly they didn't survive being copied. It probably would have been quicker to upgrade the disks in the storage server and re-plot everything. At the moment I have put 4 of the 8TB drives into the external disk enclosure and I'm copying some of the remaining plots over to it. I ended up setting up a cron task to run every 10 minutes to write a small file to the disk enclosure in order to prevent the
Read more

Storage server upgrade part 1

The first part of the upgrade was to the existing storage server. The existing server is in a Meshify 2 case and has 10 x 16TB HDD drives and a couple of SATA SSD's to use as log devices. The change was to bump the memory up to the maximum it supports (128GB). I tried around a year ago however the memory I got didn't work and the computer wouldn't even POST. This time using different memory modules it worked. While I was at it I disabled the log devices and removed the 2TB SATA SSD's. The log device is only used for writes. Seeing as the disks are full I don't write anything to the drives so there is no point in having a log device. I put a single 1TB SATA SSD in their place to use as a cache drive. I let the system run for a day so I could get some stats on how it was being used. It had a zero hit rate so I decided to disable it. On the subject of stats I seem to be getting around 75% hit rate on the memory cache (or ARC as its called under ZFS). A cache drive (or
Read more

Chia farm specs - April 2023

While waiting for a replacement parts I thought I might cover the specs of the current farm. Full node Intel core i5-11400 with 128GB of DDR4-3200 memory. 10GbE network card. Samsung 970EVO 1TB as boot drive. U2 to PCIe adapter with Intel P4510 U2 SSD (1.8TB). Storage server 1 Ryzen 5600X with 128GB of DDR4-3200 ECC memory Nvidia GT710 graphics card. 8 port SAS controller. 10GbE network card. Samsung 970EVO 1TB as boot drive. 10 x WD Red Pro 16TB SATA HDD in a ZFS raidz2 array (two drive redundancy). Storage server 2 Intel core i3-8100 with 64GB of DDR4-2666 memory. 4 port SATA card. 10GbE network card. Samsung 970EVO 1TB as boot drive. 7 x WD Red Pro 8TB SATA HDD in a ZFS raidz array (one drive redundancy). Raspberry Pi storage server Raspberry Pi4 with 4GB of memory. Micro SD card as boot drive. 2 x Seagate Expansion 16TB HDD via USB3 ports in a btrfs single drive (no redundancy). I have ordered another pair of Seagate Expansion drives in order to create a 2nd Raspberry Pi storage s
Read more