The drive firmware fix is related to power-saving/sleep states of the drive. It appears that the drive will go into power saving mode then not wake up in time for Linux to write to it or read from it - Linux thinks there’s a problem, marks the drive bad or failed and refuses to work with it anymore even after the drive is “up” again. A power cycle should fix this but it’s only a matter of time before it happens again.
There are some drives where this is simply broken and cannot be fixed - there are reports of the Crucial P5 just not working at all. Then there are reports where this is fixed with new firmware, like the WD SN850.
This is supposition on my part but there’s definitely a pattern emerging. The fact that this can be “cured” with a firmware update indicates that the power management/sleep states can be too aggressive at sleeping and the timing and responsiveness after the drive goes to sleep needs to be adjusted. The drive manufacturer has to be willing to release new firmware and if this needs to be done only for the Framework laptop the manufacturer may be unwilling to do so.