JorgeB

Start by running memtest.

Unraid driver crashed, try rebooting, the rebuild will re-start from the beginning, then hopefully it won't crash again.

That is normal until you make a change in the network settings, which is your main NIC? No link is being detected on either one.

If possible try switching that share to SMB.

Problem with the onboard SATA controller, quite common with Ryzen boards, though it appears to be much less common with recent Unraid releases, so suggest updating to v6.11.5

Disk3 appears to be failing but since there's a single error let the rebuild continue for now, note that we don't recommend USB disks in the array/pools.

Nothing relevant logged, did you take care of the Ryzen specific issues mentioned in the link above?

That is strange, there could be a board/CPU issue, though is the other DIMM doesn't give any errors after multiple runs it could just be a bad batch. Anbd if you run another scrub there are no errors? I yes it suggests there's still a RAM problem, or other hardware issue still causing data corruption.

You can just stop the array, unassign parity, start array, stop array, re-assign parity, click on parity and chose the "erase" option, then re-sync parity.

Looks good fore now, disk1 is already mounting, just need to wait for the rebuild to finish, and you can now format the new disk3.

Wait for the rebuild to finish then try booting in safe mode.

You can.

That looks more like a device problem, most SSDs cannot sustain max write speed for long.

Don't know what mean by main folder, either way and like mentioned those folders cannot be created before array start, if you remove what is creating them it should be fix your shares issue, also you should not use /mnt/user for any extra mappings.

That suggests a plugin issue, uninstall all plugins (or rename the *.plg files) to see if you can find the culprit.

If memtest finds errors there's a problem, try testing the DIMMs one by one.

Try setting the Google DNS as #1 to see if it's DNS timeout issue.

Assuming the RAM issue is corrected, you can also run memtest to see if there's a bad DIMM, delete/restore from backups the corrupt files listed on the syslog after the scrub.

That's a clear, not a format, just don't format once the clear is complete, before fixing the disk1 problem.

That's enough. Yep.

That suggests a plugin problem, remove them all then re-install one by one to see if you can find the culprit.

If Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array.

That's expected until it's rebuilt. emhttp is crashing, does it start in safe mode?

You can, you can do a new config (Tools -> New config) with the remaining good drives.

Nov 22 07:07:32 TVServer01 kernel: md: disk18 read error, sector=41446120 Nov 22 07:07:32 TVServer01 kernel: md: disk18 read error, sector=41446128 Nov 22 07:07:32 TVServer01 kernel: md: disk18 read error, sector=41446136 Nov 22 07:07:32 TVServer01 kernel: md: disk18 read error, sector=41446144 Nov 22 07:07:32 TVServer01 kernel: md: disk18 read error, sector=41446152 ..... Nov 22 07:14:12 TVServer01 kernel: md: disk10 read error, sector=8 Nov 22 07:14:12 TVServer01 kernel: md: disk10 read error, sector=16 Nov 22 07:14:12 TVServer01 kernel: md: disk10 read error, sector=24 Nov 22 07:14:12 TVServer01 kernel: md: disk10 read error, sector=32 Nov 22 07:14:12 TVServer01 kernel: md: disk10 read error, sector=40 Nov 22 07:14:12 TVServer01 kernel: md: disk10 read error, sector=48 Nov 22 07:14:12 TVServer01 kernel: md: disk10 read error, sector=56 Nov 22 07:14:12 TVServer01 kernel: md: disk10 read error, sector=64 See what's going with those disks, looks like they dropped offline and reconnected, this is usually a power/connection problem, since there are two emulated disks all other disks must work for Unraid to be able to emulate them.