Earlier quoted context omitted.
Most database designers assume that a power failure will only affect writes that are pending. Alas, for SSDs and NVMEs that's not always true. A power failure can cause all kinds of corruption. Long story short: even append-only strategies will not save you. https://www.usenix.org/system/files/conference/fast13/fast13...
That paper sounds like problems that can not be worked around in software and need hardware fixes?
So the only thing you can do is add checksumming schemes that allow you to detect you have been affected.
The paper is from 2013, so the situation might have improved meanwhile (I wouldn't put any money on it)