Selfhosted

No screenshots, but I had an old server with a pair of mirrored 8GB Seagates hosting a particularly specialized service on a very beefy and regularly maintained UPS and it had a server uptime of 21 years (had not been rebooted since somewhere around 1999) when I finally decommissioned it about 5 years ago, both disks would've been the same. It was on the public internet the whole time too, running Debian Slink with kernel 2.0.36, which had been awkwardly patched and rebuilt somehow to make the service (itself already obsolete at that time) actually work. I don't know why I remember all this, but I do.

I do remember monitoring the SMART status at various points and the drive bearings must've been pretty cooked because those two drives were always running at 50-60C and I had a big old box fan pointed at the thing with the side panel off.

This example is also why I don't always buy into the cult of "you must always regularly update all software immediately all the time". Old software is not always bad software, same with old hardware. Sometimes it's genuinely possible to have a bulletproof system. The problem is you never really know you do, until it either enters survivorship bias or becomes catastrophically proven otherwise. But you can make educated guesses, and if you're going to naively assume that your old software must have exploitable security holes it seems equally naive to me to assume that updates must never have exploitable security holes. I think the risk calculus has to be done on a case-by-case basis.