I don’t think the drive actually failed. The article said that the files disappeared from the drive one-by-one, which sounds like a firmware bug to me.
You could theoretically have the same problem due to a buggy RAID controller or driver.
I don’t think the drive actually failed. The article said that the files disappeared from the drive one-by-one
It didn’t fail in the sense of reporting an I/O error, but it did fail in the sense that the bytes previously written to it can’t be read any more.
which sounds like a firmware bug to me.
Could be. SSD firmware is pretty notorious for data loss.
You could theoretically have the same problem due to a buggy RAID controller or driver.
Which is why I don’t trust hardware RAID controllers, only software RAID, preferably with per-block checksums so that the software RAID controller knows which copy is the good copy.
The author is using macOS, whose APFS file system has those features. Linux’s btrfs does too.
I don’t think the drive actually failed. The article said that the files disappeared from the drive one-by-one, which sounds like a firmware bug to me.
You could theoretically have the same problem due to a buggy RAID controller or driver.
It didn’t fail in the sense of reporting an I/O error, but it did fail in the sense that the bytes previously written to it can’t be read any more.
Could be. SSD firmware is pretty notorious for data loss.
Which is why I don’t trust hardware RAID controllers, only software RAID, preferably with per-block checksums so that the software RAID controller knows which copy is the good copy.
The author is using macOS, whose APFS file system has those features. Linux’s btrfs does too.