MP 1,1-5,1 Samsung 860 EVO - disk utility can't fix errors on the SSD

[mateo14]

Hi

I use the SSD Samsung 860 EVO, and I started to have problems with it.

The Disk utility found this issue but couldn't fix it.

warning: found orphan file extents (id 778311, size 61440)
error: found file extent (id 778311) at logical address 0 beyond the end of the dstream 18446744073709551615
warning: apfs_num_directories is not valid (expected 73485, actual 73471)

I fixed it with fsck_apfs by using a flash drive with Catalina. I restarted a Mac Pro 5,1, and I see even worse issue.

error: Cross Check : Mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (0x22b88db + 15)

I'm not sure if I judged correctly, but it looks serious.

Does it mean that my SSD starts to die?

I contacted the store, and they told me that they are able to fix different issues with the SSD. They informed me if this issue happens again, they can replace it.

What should I do with this SSD?

Do you think the expert could fix it?

I never left the HDD/SSD in the service center because I wasn't sure how reliable it would be after it.

 

[h9826790]

You are running Catalina now?

 

[mateo14]

You are running Catalina now?

Yes, on this SSD, I use Catalina and Ubuntu 22.04.

 

[h9826790]

You ran fsck_apfs from a flash drive. That flash drive has the same version of Catalina as the one that on your SSD?

Anyway, if possible, avoid multi OS on a single drive. It can work, but often cause trouble.

 

[mateo14]

You ran fsck_apfs from a flash drive. That flash drive has the same version of Catalina as the one that on your SSD?

I checked it out:

SSD:

Spoiler: sw_vers

sw_vers
ProductName: Mac OS X
ProductVersion: 10.15.7
BuildVersion: 19H2

Flash drive:

Spoiler: sw

sw_vers
ProductName: Mac OS X
ProductVersion: 10.15.7
BuildVersion: 19H15

The BuildVersion is different. I created this flash drive with Catalina yesterday, which is odd.

Anyway, if possible, avoid multi OS on a single drive. It can work, but often cause trouble.

I know about about simple issues.

Can it generate these types of errors in the file system of macOS if Linux is on the same SSD?

I was thinking about reinstalling of macOS. However, I don't know if the SSD works in a simmilar same way.

I had many issues with the HDD in the past. I reinstalled the macOS, and the DU didn't show any errors for a short period of time. Unfortunately, in these situations the issue with the HDD still existed. Later, the DU started to generate errors, and files get corrupted.

Do you think that I should give this SSD to the service center?

I frequently buy games from online stores. I don't want to lose these files by downloading them to the broken SSD. These files will get corrupted even if I immediately copy them to the flash drive.

 

[h9826790]

It may be just APFS error, not necessary SSD hardware failure.

I asked about the OS version because different macOS version actually has different version's of APFS system. And if you use a newer build to fix the older build. Then the older build may not able to read the file system correctly.

 

[mateo14]

I don't see any updates, so I don't know how can I have two different builds of the same OS. I'm guessing that my build on the SSD is older.

I can reinstall the operating system, and maybe it will fix or worse cover this issue.

Can you recommend any free tool that can check SSD hardware failure?

 

[h9826790]

I don't see any updates, so I don't know how can I have two different builds of the same OS. I'm guessing that my build on the SSD is older.

I can reinstall the operating system, and maybe it will fix or worse cover this issue.

Can you recommend any free tool that can check SSD hardware failure?

There are 18 releases of 10.15.7 in Catalina, Apple call them all 10.15.7. Can be very confusing indeed.

19H2 is the oldest one. 19H2026 is the latest one.

 

[mateo14]

Thank you for the answers.

I reinstalled the operating system, and I noticed that I have another issue:

Spoiler: SSD

Checking the fsroot tree.
warning: apfs_num_directories is not valid (expected 221945, actual 221942)

I will contact the online store and maybe they can fix this SSD or replace it.