JorgeB

I don't have an explanation, but I did observe similar behavior, but only sometimes, usually for a short while, and not in a reproducible way, so I never tried to investigate further, but is likely related to btrfs (or COW in general) since all my servers are also btrfs.

With the full diagnostics it would be easy to see it's an Asmedia controller, with just the syslog it doesn't show Asmedia, it just shows a two port controller loading after the first 6 Intel ports, but using the motherboard model I could see it has a 2 port Asmedia controller.

Since kernel 4.4 balance is not needed, at least not regularly.

Most likely. At least that one is, it's using one of the two Asmedia ports.

Yes, looks like a connection/power issue, disk dropped offline out of the blue, like if the power or SATA cable was pulled.

Start by redoing the flash drive: backup config folder, recreate flash, restore config folder.

That's incorrect and should be updated. It shouldn't be ignored, that's the value you need to keep an eye on.

The link explains ou to read the actual errors on Seagate drives, just looking at the total RAW value is pointless for those, not for WD drives, the RAW value is the actual number of errors, so 0 = good, anything above 0 not so good, though low values can be OK.

They should be saved after the disk gets disabled, and before rebooting, without the syslog and based on the SMART report disk looks OK, CRC errors like mentioned aren't a disk problem, so likely it's the slot/cable.

If there are errors there's a problem, and it's not the drive. Without any diags posted we can only guess.

That's for Seagate drives: https://forums.unraid.net/topic/86337-are-my-smart-reports-bad/?do=findComment&comment=800888

CRC errors are a connection problem, 9 times out of 10 a bad SATA cable, but could also be the backplane, even the controller, though much less likely.

RAW_VALUE

Forgot to say, you can still swap backplane slots to rule that out, but like mentioned I don't think that is the problem.

Besides the normal pending/reallocated sector attributes, on WD drivers there are couple more that should be monitored: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 51 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 26 Both should be 0, or close to that on a healthy drive, higher numbers are usually bad news (especially if they keep climbing) and the disk will likely return read errors sooner or later, but there are exceptions, or disks that give a few errors then work fine for some time.

You need to delete/move data from the cache pool, deleting docker containers won't do much for this, and the docker image will always need to be recreate since current one is corrupt, likely from running out of space, recreating the image is very easy.

Yes, but since the SMART test passed those are "false positives", still pretty sure the read errors on both disks are disk related and they will likely fail again soon, still good to rule out connection issues since on rare cases they are logged as media/UNC errors.

Please don't double post, threads merged.

See if this helps: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173 P.S. Ryzen 3 3200G is a second gen Ryzen, not third as the model implies.

Two visible issues: -CPU is overheating, check cooling -There are what look like connection/power issues with multiple disks, check all connections and/or use a different PSU if available

It's already using latest firmware: Mar 8 08:15:24 NAStheRIPPER kernel: mpt2sas_cm0: LSISAS2116: FWVersion(20.00.07.00), ChipRevision(0x02), BiosVersion(07.39.02.00) BIOS version (or if there's one) it's not important for Unraid.

Both SMART tests completed successfully, when there are no pending sectors these errors can sometimes be intermittent, I suggest replacing/swapping cables on both disks (power and SATA cables) then try again, post new diags if there are more errors.

Parity disk appears to be failing, you can run an extended SMART test to confirm. This was before the period covered on the posted diags, but if there were read errors on the parity disk during another disk's rebuild that disk will now have some corrupt data.

If that's the writing part of preclear it's normal, when disks get these slow sectors the problem is on reads, writes usually work normally.

Yes.