Brace yourself, giant wall-of-text!
As I’ve mentioned elsewhere on the forum, I think it’d be theoretically possible to create a sort of m.2 2280 riser card that includes two m.2 2230 slots, both assigned 2 PCIe lanes each.
I have literally never had this happen. Conversely, I’ve had at least three SSDs just suddenly die, one of which I was able to revive by leaving it plugged into power for an hour, unplugging for an hour, and then plugging it back in. Admittedly though, all 3 SSDs were older models with capacities measured in mere double-digit gigabytes.
That being said, even just plain old power failure can brick an SSD - I have a family friend where that happened to a 480GB Crucial M500 SATA SSD after their desktop PC’s PSU failed (though, rather than being a true brick, it was permanently locked to a read-only state).
I similarly had the exact same “permanently locked to read-only” issue occur when trying to clone the data from the aforementioned family friend’s SSD when I was experimenting with powering two SSDs off of a USB power bank due to questionable weather at the time. I was almost certain it’d be fine even with both sharing a single USB port since the power bank can output up to 2 amps at 5 volts, but I made the horrible discovery that only one of the bank’s two USB ports can output at 2 amps and, sure enough, I connected them to the port that could only output 1 amp. Now luckily one of the two connected SSDs worked without issue to the point that I don’t even remember which SSD of mine it was, but the other SSD was ironically yet another 480GB Crucial M500 SATA SSD that, due to insufficient power, permanently locked itself to read-only.
(yet another reason for open firmware - I would love to be able to unlock the two aforementioned M500 SSDs that are locked to read-only and then run a proper test to see if they’re at least partially usable or not, but Crucial seems to have not made such a thing possible and AFAIK nobody has created any 3rd party “homebrew” firmware - even doing a secure erase doesn’t unlock them despite actually completing the actual erase process)
Lastly, I also had a psuedo-brick occur with an older 256GB Crucial M4 SATA SSD when I tried connecting it via a USB 3.0 SATA adapter that doesn’t have supplementary power to the front USB of an older LGA1156 motherboard, forgetting that most pre-USB 3.0 PCs only provide something like 500 milliamps to their front USB ports. Ironically, because it was an older model SSD that didn’t have the “lock to read-only” fail-safe, I was actually able to revive it by simply leaving it connected to power for an hour or so, unplugging it for another hour or so, and then plugging it back in.
One of the benefits of software RAID is that you can mix and match completely different drives in order to avoid this very issue, and is something you can do with mechanical hard drives as well.
And the good news is that, unlike mechanical hard drives, it’s so incredibly rare to have an SSD fail during a process where you’re only reading data (e.g. rebuilding a RAID mirror), so using two different model drives should basically guarantee you always having at least one functioning drive (assuming no catastrophic disaster has occurred such as the aforementioned PSU failure).
And technically, even if they’re the same model drive and you avoid any sort of “instant brick” failure scenario, if they were manufactured at substantially different times (e.g. a year or two apart) then it’s very likely that the NAND chips themselves have different yield characteristics - heck this could be the case even if they were manufactured close together simply due to the way the silicon lottery works (something that doesn’t apply for mechanical hard drives but definitely does for NAND flash memory).