JorgeB

Yes (all that have those attributes).

Don't remember seeing anything that like reported before, and I also have some, I did notice some quirks with those Samung ECO drives, I would swap controllers first.

Note that you'll need to do a new config after the update because the disk's ID will change, one of the known issues with that old firmware.

Disk looks fine on SMART, I would recommend updating the firmware first, since it's very old and has known issues, you can easily do it inside Unraid.

If it happens again grab diags before rebooting, multiple disk errors are usually not a disk problem, disk7 is failing though, assuming it's the currently unassigned WD.

It might help if you post the rest of the syslog, to see if there's something in common happening just before, this issue has usually been linked with other things interacting with /mnt/user, like a docker that directly manipulate files, e.g., renaming or moving them, also recently there was a case that was apparently caused by unmounting a remote share.

That's from disk2, and it does look healthy, I wanted to see SMART for parity, since that's the one where the initial error is logged as a disk problem, but possibly just a controller issue, since not surprisingly both were on the Marvell controller.

Very good.

It failed the extended SMART, so it is a failing disk. Yes, any WD drive.

Yes, but You can re-enable parity2 and rebuild both disk1 and disk3, use a new spare disk for disk1 in case the rebuild disk is corrupt, or just check the emulate disk before rebuilding on top. Again this will only work if parity is still valid: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including the new disks 1 and 3, replacement disk should be same size or larger than the old ones -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array -Stop array -Unassign both disks you want to rebuild -Start array (in normal mode now), ideally the emulated disks will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk(s). -If the emulated disks mounts and contents look correct stop the array -Re-assign the disks to rebuild and start array to begin, (don't rebuild on top of old disk1 if the emulated disk isn't OK).

See here for some options, you can try btrfs check --repair but make sure that any important data is backed up first.

I would use option 2 mostly because you can keep the cache online during the entire process, time it will take is going to be about the same.

Most likely, as even gigabit can do 115MB/s.

Yes.

You just need one data device assigned.

Not quite sure what you're asking, you can't transfer parity, you can replace it with another disk, but can only have one more disk disable.

But if the array was used without it parity won't be valid if you re-enabled it now, you'd need to rebuild both, again assuming parity2 is still valid, or they won't rebuild correctly.

So current disk1 is also new correct?

Once a disk gets disable it needs to be re-enable/rebuilt. Please post a screenshot of main to see current array status.

You can force enable parity2 but it will only work if parity is still valid, i.e., there weren't any more writes to the array once it got disabled.

You can't start the array with that many missing drives without doing a new config, and that would result in data loss from any missing data disk.

If it's not cables it's likely the devices, though extremely unlikely for both to fail at the same time.

Settings -> Network Settings -> Interface Rules (reboot required after)

You should really avoid the Marvell controller on those boards (first four white ports), they are are known issue, also good to post new diags since there's no SMART for a couple of disks in the previous ones, and the initial error with parity is logged as a disk problem.

One thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.