[lazide]

Yes, and? HDD controllers dying and head crashes are a thing too.

At least in the ‘bricked’ case it’s a trivial RMA - corrupt blocks tend to be a harder fight. And since ‘bricked’ is such a trivial RMA, manufacturers have more of an incentive to fix it or go broke, or avoid it in the first place.

This is why backups are important now; and always have been.

[mort96]

We're not talking about the SSD controller dying. The SSD controller in the hypothetical situation that's being described is working as intended.

[lazide]

Not as far as I can tell, where intended is ‘as any user would reasonably expect’. Bricking the drive (can’t even read) because of too many errors is not what most users would ever want.

Some would (enterprise maybe), but even then they’d want deterministic data deletes too, which doesn’t sound like are happening.

[mort96]

You can argue that controllers shouldn't behave that way. But they do, it's not a bug, and it's not a dead controller. It's a perfectly functional controller's response to dead blocks.

[lazide]

Cite? By definition it appears to not meet the definition of ‘functional’.

[coldtea]

The definition of functional in the context of the discussion is that in works in the way the manufacture explicitly designed it work, in a standard industry practice fashion, not as an unforeseen bug or malfunction.

Not some abstract notion.

[lazide]

So not enumerating as a drive, and not allowing you to read even valid blocks is ‘working’?

[asdefghyk]

RE "....This is why backups are important now; and always have been..."

Still a big problem if backup is to the "..same technology..."

[lazide]

That’s why 3-2-1 is not just a good idea.