I've had a similar frustration. For what it's worth, sending most logs to RAM drastically reduces the write-thrashing on the SD card, and greatly prolongs the life of a 24/7 Pi: https://github.com/azlux/log2ram

Depending on the use case, RAM disks are also pretty easy to set up for any temporary/volatile storage used by shell scripts and the like.

I've used various RPi's (and clones) for years now, and I've never had a SD card fail.

One RPi has been running my Home Assistant for 3 years 24/7, with a very noisy ZWave network that has debug logging on.

I had one where I _thought_ there was something weird going on with the SD card, but it turned out to be a crappy USB cable that lead to excessive voltage drop under load. Swapped the cable and it's been running my PiHole for over 2 years now on a standard Armbian+Docker install, zero issues.

Maybe I've just been lucky?

I purchased 2 Pi4s to run various small self-host services on. I've lost two SD cards in the course of about 6 months, and I've generally had stability problems with both of them, the hangs seem mostly tied to SD card and USB controller issues from what I can tell. I think my highest uptime is about 4 weeks. I'm not sure if it's heat or power related, or just bad SD cards, or general instability of the 4.

Regardless, I'm done monkeying with Pi 4s, and I'm moving to cost comparable PC Thin Clients for my self-hosting needs.

Never had any issues with several Pi3s over the years. They just don't have the oomph anymore for my needs.

It usually dies during an ungraceful shutdown. Had at least 3 go over the years until I switched to USB to SATA SSD boot. Not a problem since.

Standard Pi perhaps, but the official Pi Compute module supports sata. Geerlinguy did a nice writup about it.

Ebon has said specifically (in answer to my question in a Q&A) that the standard Pi will never have built in SATA. Your best option is one of the other manufacturers Pi type SBC clones.