Yeh, the 16/32 in the screenshot and that 2 sticks are dead suggests they have 4x 8gb sticks, and lends credence that one channel is being messed with.
They said they tested the ram on multiple systems, but they might have just thrown both “dead” sticks in there at the same time - leading to a similar failure mode as they are both on the same channel.

I bet 1 stick is dead, and they could probably get away with 24gb of ram in a 3/2 channel distribution

Maybe 1 is causing the other to fail?
Could try the sticks individually.

It is strange that 2 sticks fail at the same time. It smells like a symptom instead of the root issue.

While true, quantity of poop particles also matters.
Your body can fight off loads of bacteria. But once it gets to an infection point, it can’t keep up and you become ill.

So yeh, poop is everywhere. As long as it’s small amounts, it’s fine.

Pretty much any mikrotik is a fantastic piece of kit to have.
It is so unbelievably versatile.
I love the various mikrotik routers, switches and APs I have. I use them all the time for little ad-hoc networks and projects and stuff.
You will learn a lot about networking when using them.

But Unifi is a hell of a lot easier to use, and I have not found anything I can’t do on unifi (but I don’t do bgp, mlag, etc at home).

Oh, and on the “fail often” thing…
Get a basic/old/free pc/laptop and install Proxmox on it.
Loads of tutorials out there, but the basic installer will get you to a “I’m learning” stage.

Create a VM, install Debian, play around.
Then: create a new VM, install Debian, create a snapshot, play around until it does what you want, restore the snapshot, do the steps that got you from vanilla to what you want. Create snapshots along the way as checkpoints. Snapshot, tinker, restore snapshot, advance.

Proxmox is amazing for learning VMs and server things

Raspberry pis are an easy intro to actually using computers (instead of using something like windows).
Raspbian is great (based on Debian) and there is a HUGE community for it.

So yeh, it’s a great started for $25, as long as you have a PSU and SD Card. And an hdmi cable + monitor + keyboard at your disposal (and a mouse if you are installing a desktop environment (IE something like windows, whereas headless is a full screen CLI).
And don’t get your hopes up for a windows replacement.

But… Why not run a Virtual Machine? If you have a windows machine, run VirtualBox, create a VM and install Debian on it?
That’s free. You can tinker and play.
And the only thing you are missing from an actual raspberry pi is that it isn’t a standalone device (IE your desktop has to be on for it to be running), and it doesn’t have GPIO (ie hardware pins. And if this is your goal, there are other ways).

If you really really want a computer that is on all the time running Linux (Debian, a derivative (like raspbian) or some other distro) - aka a server - then there are plenty of other options where the only drawback is lack of GPIO (which, in my experience, is rarely a drawback).
And that is literally any computer you can get your hands on. Because the raspberry pi trades A LOT for its form factor, the ethernet speed is limited, the bus speed is limited (impacting USB and ethernet (and ram?)), the SD card is slower and will fail faster than any HDD/SSD. The benefit is the GPIO, the very low power draw, and the form factor - rarely actually a benefit.

I’d say, play around with some virtual box VMs. See what you want, other than Fear Of Missing Out (things like PiHole? They run on Debian, or even in a docker container). Then see if you actually want a home server, and what you want to run on it.
It’s likely you won’t want a raspberry pi, but a $150 mini pc that can actually do what you want.

The majority of Europe survives.
Although their sockets are recessed.

I doubt it.
Tripping over a cable is as likely to damage the socket as it is to rip the cable out of the plug.
Any appliance that increases risk by being unplugged should probably not be using a consumer connection…

I think the 3 pin layout caused a lot of headaches, and the integrated fuse required a user-servicable plug.
So it would have to be a split-shell design of some type, where the appliance cable would have to be cable-gripped to the same part as the plug/socket pins.
Thus, a bottom-entry (heh) cable grip and a removable back plate that can only be unscrewed when it’s unplugged.
This was all in a time of bakelite. Plastic wasn’t flexible.

But no, I think tripping over an early bakelite g-type (I think it’s officially a g-type) plug cable would likely shatter the plug and pull the pins out of the socket… If it didn’t also damage the socket.

No, the cable comes out perpendicular to the pins (ie parallel to the wall).
Which pretty much guarantees foot-pain orientation

Yeh, bath/shower ones seem affordable.
But for a standalone sink, they seem to be significantly more.

Ah, I missed that part of the conversation

You sure it’s not WhatsApp that’s link-shortening?

I’m amazed at the comments explaining incoming water temperature fluctuations and pressures…

No no, thermostatic tap/faucet mixes waters depending on the output temperature. Ignores all of the variables except the thermal mass (I guess reaction speed) of the thermostatic system.

I think they are normally like 10x the price of a standard mixer tap tho.
So, it’s a budget choice

I hear that the US has oil and WMDs

Id love to believe this is to weed out the bad applicants.
People that answer “lol, I just want a job” actually get the interviews

Ah, fair.

3x minisforums MS-01

A NAS as bare metal makes sense.
It can then correctly interact with the raw disks.

You could pass an entire HBA card through to a VM, but I feel like it should be horses for courses.
Let a storage device be a storage device, and let a hypervisor be a hypervisor.

especially once a service does fail or needs any amount of customization.

A failed service gets killed and restarted. It should then work correctly.
If it fails to recover after being killed, then it’s not a service that’s fully ready for containerisation.
So, either build your recovery process to account for this… or fix it so it can recover.
It’s often why databases are run separately from the service. Databases can recover from this, and the services are stateless - doesn’t matter how many you run or restart.

As for customisation, if it isn’t exposed via env vars then it can’t be altered.
If you need something beyond the env vars, then you use that container as a starting point and make your customisation a part of your container build processes via a dockerfile (or equivalent)

It’s a bit like saying “chisels are great. But as soon as you need to cut a fillet steak, you need to sharpen a side of the chisel instead of the tip of the chisel”.
It’s using a chisel incorrectly.

I would always run proxmox to set up docker VMs.

I found Talos Linux, which is a dedicated distro for kubernetes. Which aligned with my desire to learn k8s.
It was great. I ran it as bare-metal on a 3 node cluster. I learned a lot, I got my project complete, everything went fine.
I will use Talos Linux again.
However next time, I’m running proxmox with 2 VMs per node - 3 talos control VMs and 3 talos worker VMs.
I imagine running 6 servers with Talos is the way to go. Running them hyperconverged was a massive pain. Separating control plane and data/worker plane (or whatever it is) makes sense - it’s the way k8s is designed.
It wasn’t the hardware that had issues, but various workloads. And being able to restart or wipe a control node or a worker node would’ve made things so much easier.

Also, why wouldn’t I run proxmox?
Overhead is minimal, get nice overview, get a nice UI, and I get snapshots and backups