Yes, absolutely. Right now, SSDs are probably superior in comparison to HDDs in every category except for price (and long-term data integrity when switched off). But when you consider large parity raids and take into account the cost of electricity, even the price difference might only be small, making SSDs even more attractive.
Hmm. Let’s say I add 6 SSDs, 2TB each, for a total of 600€. In a RAID6 configuration, that gives me 8TB of storage. Compare that to a classical NAS with 2×8 TB HDDs for a total of 350€.
The HDDs will draw around 4W idle each, 8W in total. Assuming 0.3€/kWh, over a span of 5 years, that is approximately 100€. The power consumption of the SSDs will be negligible.
So, just in terms of storage, the SSD solution is around 33% more expensive over 5 years. If you include the cost of the NAS itself, the price increment is even less noticeable.
Very helpful. I was just looking at this the other day.
I just checked, and I have connectivity while on cellular. Maybe (just wild speculation) your mobile network is IPv6-only? Android (not Linux) should list 192.0.0.4 as an IP address in that case.
Yes, Linux is running in a VM, and the network interface is a virtualized veth interface connected to a host bridge. The host android system has IP address 192.168.0.1, and this network interface is called avf_tap_fixed (as seen from termux).
While this is very exciting, I just tried it, and the network connectivity seems to be broken. No IPv6.
I met someone that was throwing out old memory modules. Literally boxes full of DDR, DDR2 modules. I got quite excited, hoping to upgrade my server’s memory. Yeah, DDR2 only goes up to 2GiB. So I am stuck with 2×2GiB. But I am only using 85% of that anyways, so it’s fine.
I did the same last week (and am still in the process of setting up more services for my new server). I have a few VMs (running Fedora CoreOS, with podman preinstalled), and I use ansible to push my quadlets, podman secrets, and static configuration files. Persistent data volumes get mounted using virtiofs from the host system, and the VMs are not supposed to contain any state themselves. The VMs are also provisioned using using ansible.
Do you use ansible to automatically restart changed containers after pushing your changes? So far, I just trigger a
systemctl daemon-reload, but trigger restarts manually (which I guess is fine for development).