remotelove

Also, it depends on the problem you are trying to solve and if the good deal lets you buy plenty of spare drives.

I have a 3 server cluster running 9 k8s nodes with persistent storage in Longhorn. While it thrashes the drives a bit more and I lose performance, I opted to use hardware RAID so a drive rebuild would be much easier. (I think with Ceph, it’s a step or two more to kick a drive out of the storage pool before you can swap the drive safely. The fact that I can’t remember much about Ceph already and it’s only been a month or two since I setup a Ceph testing cluster should alone explain my decision.)

Basically, I get volume replication backed by easy to manage and affordable drive replacements. I even get mirrored boot drives too. The setup is fault tolerant to a degree and it gives me enough time to shuffle things around if a server starts to die completely.

All the drives are used and have already had a full life, but yey, the risk is ok because the parts are cheap. I’ll probably buy another refurbished server of the same type just for the spare parts, drives and memory. I could even just use the extra server as a cold standby. Whatevers.

The cluster isn’t critical, to be perfectly honest. It really just holds a massive tool suite of containers that I need at random times and now I at least have solid templates and ansible confogs for all of those containers anyway. Even the data isn’t super critical.

Parts are cheap and my setup allows for disposable drives in a setup where risk tolerance is sky-high.

My NAS is RAID 10 with brand-new drives and read/write cycles are conserved. I care about that data and will probably mirror that storage that to an additional pair of mirrored m.2’s to absorb most of the read a cycles while adding an additional redundancy layer. (The hdds would primarily only see write cycles and probably just function as an incremental backup location for specific folders off of the m.2’s.)

Those are the cliff notes, and only I attempted to explain how I thought about risk in my setup. Volume over quality for my cluster: I think about fast recovery and how I can parch around a problem during a catastrophic failure. Long term: Multiple layers of redundancy for important data with less concern about price but I have less capacity and speed.

Having spent years around lots of equipment, I view a flashy red light on an HDD as a suggestion to do something about it in a couple of days if the server is just a worker node. (I have been desensitized to most hardware faults, TBH.)

Same for me, with the exception of an Atari 2600 because she liked pacman. By the time I was old enough to remember playing it, it was already extremely outdated.

I am not sure where our C64 was on the scale of computing, TBH. The only thing it was exceptional at was gaming, but it is where I got exposed to BASIC and how filesystems worked.

Our TRS-80 was a really fancy paperweight and still not sure what it was actually used for, to this very day.

Our 286 is where the magic really started and that is when I truly began to disregard consoles. (Consoles were still cool and I still wanted one, but Space Quest or LSL were still just fine.)

Lulz. We converged in our search and found the same link you did… (I completely skipped over the link you provided somehow before I started my own looking.)

But yeah, I agree it’s probably an EEPROM and you might be able to copy it? Dunno.

I think you two just said the same thing.