Then why do you think manufacturers still list these failure rates (to be sure, it is marked as a limit, not an actual rate)? I’m not being sarcastic or facetious, but genuinely curious. Do you know for certain that it doesn’t happen regularly? During a scrub, these are the kinds of errors that are quietly corrected (althouhg the scrub log would list them), as they are during normal operation (also logged).

My theory is that they are being cautious and/or perhaps don’t have any high-confidence data that is more recent.

Bit error rates have barely improved since then. So the probability of an error whenr reading a substantial fraction of a disk is now higher than it was in 2013.

But as others have pointed out. RAID is not, and never was, a substitute for a backup. Its purpose is to increase availability. And if that is critical to your enterprise, these things need to be taken into account, and it may turn out that raidz1 with 8 TB disks is fine for your application, or it may not. For private use, I wouldn’t fret. but make frequent backups.

This article was not about total disk failure, but about the much more insidious undetected bit error.

Let’s do the math:

The error-reate of modern hard disks is usually on the order of one undetectable error per 1E15 bits read, see for example the data sheet for the Seagate Exos 7E10. An 8 TB disk contains 6.4E13 (usable) bits, so when reading the whole disk you have roughly a 1 in 16 chance of an unrecoverable read error. Which is ok with zfs if all disks are working. The error-correction will detect and correct it. But during a resilver it can be a big problem.

I also use this, and it works great. Another downside is that when using the free service, others can just use subdomains of your registered domains. You can always deny it, but you have to do it manually. With the premium subscriptions you can prevent that automatically for a number of domains, depending on how much you pay.

If you want a proper server, it seems that Asrock Rack is the only manufacturer of AM4-socket-based server mainboards. Unlike desktop/gamer boards, these are designed for parallel airflow, typically from front to back in a 19" rack. These also come with IPMI remote maintenance, so can be operated headless in a remote location.

I have considered one of these for a while, such as the X570D4U, which also supports up to 128 GB of ECC RAM. Depending on what you want, this may be overkill, though.

(This was my favourite, because it has two M.2 slots, but there are others with only a single slot, since you said you only need one.)

Unlike gamer or other boards, these have no fancy black vanity covers and often won’t allow overclocking, but are typically very well designed and rock solid for unattended 24/7 operation.

That’s a very narrow-minded view. I thought the same thing when the iPad was new. But I changed my mind.

Sitting on the sofa and watching movies or reading news is a good application, a laptop is too clunky for that, and a phone screen is too small.

Also use as an air-navigation device (not only) light aircraft, and replacement for paper charts in airline operations. There are many legitimate uses where tablets are exactly what you want. If it’s not for you, fine.

Not so much server-based, but the experimental part of "lab" is well covered: I replaced my late-2013 27" iMac's internal HDD with an SSD. It's a really delicate procedure, as the display is glued to the chassis; it needs to be cut loose and very carefully removed (it's tempered glass), and then re-glued with special adhesive strips. But the performance gain is worth it. In addition, it also now runs Ventura, even with the nVIDIA card, thanks to OpenCore Legacy Patcher. Feels like a new machine now, and is perfectly adequate even for small video editing tasks with its 32 GB RAM.

One urgent thingis that the EU follow the UK in abandoning the ill-conceived “client-side scanning”, aka Chat-Control.

--info=progress2 for long transfers involving a large number of files. Gives continuously updated statistics on the whole transfer.

As to filling up the drives so fast, have you considered transcoding it to a smaller format (such as HEVC/H.265) in real time? I know that would require quite some CPU power. Even H.264 is likely to improve on camera native formats, as those often need to encode the videos with embedded/low-power CPUs. Do you need to retain the footage beyond 3 months?