Problem with SSD

[Aravisian]

@adiditm

I have also found similar reports from other users in this forum (Bavaria98, Thhunder, Haku) describing identical symptoms. This appears to be a consistent and reproducible issue across multiple Zorin versions (16.1, 16.2, and 17/18).

Relevant threads, here:

SSD destroyed after update

With Space the output is: bash: cd: /dev/sdb/: Not a directory (bash: cd: /dev/sdb/: Ist kein Verzeichnis)

Boot Issue on Laptop Due to Corrupted OS

Well, now I would suggest to create an USB Stick with Windows on it and then try it with repair it.

Problem after Installation with my SSD and the whole GiB

You're contradicting yourself. Either you want Zorin to use the whole disk or you don't. Which is it? Nothing is being damaged by Zorin, nothing. Well there's part of your problem right there by your own words that has nothing whatsoever to do with Zorin. Your hard drive already has bad sectors. I'm not sure why you felt the need to "clean" the drive before installing Zorin. Perhaps whatever you used to clean the drive also broke the drive. When installing, you should choose something els…

I cannot call these "Identical symptoms."

In Bavaria98's case, we see a case consistent with a failed SSD controller, failed firmware, or failed USB-SATA bridge. Nothing that Zorin OS would alter or damage.

The other two match only in that in each, the O.P. fears SSD damage.

Zorin OS is based on Ubuntu, itself based on Debian. Were this inherited, we would see many reports from all three distros.
And for it to be exclusive to Zorin OS, this would require a Zorin OS specific configuration within the operating system that changes SSD read/write behavior - none of which actually exists (and can be searched for by any user to verify.)

I hope that the warranty honors you a replacement SSD. And given your report, I think it is best for the ZorinGroup to review this feedback:
@AZorin
@zorink

There is a lot of information that we on this forum do not know - how many read/write cycles both of those SSD's have experienced and so on. But I would caution against jumping to correlation conclusions on meager evidence.