I've had hundreds of enterprise SSDs fail on my servers, but only a couple had any pre-failure indicators in SMART, including write volume which was pretty low. The post-failure indicator was almost consistently no longer visible through the disk controller.

Failure rate was much less than enterprise spinning disks, but at least with the spinners failed, you could still see them and get most of the data off, if you needed to. And they had reliable pre-failure indications.

TLDR: take regular backups and plan for storage to fail (which for soldered storage means plan to get a new device, I guess)

If your running that big of a shop, I would call your channel partner/support group and bitch until they figure out whats failing. The usual expected failure modes for SSD's should be that they go into read only mode. If that isn't happening its either a firmware bug (probably) or a controller/vr failure which could be a process/heat/etc type of failure.

Particularly for "enterprise" equipment the expectations isn't that it fails, but that the failures are more graceful and understood.

So complain... that is why your paying the "enterprise" tax.

This was in managed hosting, we'd open a ticket and get teh SSDs replaced quickly, which was good enough for us. For the most part, the failure rate was about 10% of the rate of the hard drives, and concentrated in the systems with many disks, which were setup to handle disk failures, so it wasn't a big big deal.

Although we did get a couple of bad batches on our single disk systems, almost all of those failed within 2 weeks of install and we had the rest replaced.

I also suspect firmware bugs, but it wasn't convenient to upgrade them, so who knows. I did have to upgrade some of the same disks on single disk systems with low usage; the disks would sometimes timeout for no reason and confuse some of our OSes. The upgrade procedure was more or less PXE boot the manufacturer upgrade utility and hope it worked with whatever disk controller was there (eta: 5 minutes) or let the hoster firmware upgrade script run and hope it upgraded the ssd firmware and didn't mess anything else up (eta: 40 minutes per run, probably run it twice).

Apple SSD module failures on portable Macs are quite common. A buddy has a computer repair shop and they do brisk business replacing them. Mine failed about 5 years in.

SSDs are wear items. Especially when they're quite full, it is very easy to blow through spare writes and brick the drive.

There was a problem with some of the SSDs where they corrupt themselves on powerloss.

That’s a totally different reason, and afaik, they should be using proper caps to let the controller write/flush their buffers.

My last MacBook Pro was 7 years old, almost always full, and still works fine. Granted I’m not a video editor, but I had quite some write cycles.

Did those modules fail readonly, and the SMART data showed that their write limit had been reached?

Or did the entire module electronically fail, as distinct from the SSD "no more writes" case?

One, small capacity X limited cycles = short life span.