My assumption was it had something to do with the drivers for the controller, and the update flooding it faster than it could take data and not caching everything it couldn’t cram into controller DRAM, causing parts to just get dropped wholesale.
modern ssds have on board firmware that executes actual nvme (or sata) commands. so it’s possible a bad dma driver can coincide with a firmware bug to result in unexpected behaviour.
My assumption was it had something to do with the drivers for the controller, and the update flooding it faster than it could take data and not caching everything it couldn’t cram into controller DRAM, causing parts to just get dropped wholesale.
modern ssds have on board firmware that executes actual nvme (or sata) commands. so it’s possible a bad dma driver can coincide with a firmware bug to result in unexpected behaviour.