JorgeB

It's a known issue and already fixed, v6.11.3 should be available very soon.

Please post the diagnostics.

Try a different browser, also make sure there's no ad-blocker or firewall blocking the GUI access.

Should be available very soon, possibly later today, in the meantime you can safely downgrade to v6.11.1 by downloading the zip and extracting all the bz* files and changes.txt to the flash drive overwriting existing files.

Look at the syslog for the list of corrupt files, for example: Nov 7 16:47:51 1mehien kernel: BTRFS warning (device md22): checksum error a/t..t/... logical 274136035328 on dev /dev/md22, physical 275218165760, roo/t..t/... 5, inode 28500, offse/t..t/... 45453312, leng/t..t/...h 4096, links 1 (pa/t..t/...h: music/Thuong Music/1. CD RIP VINHSTUDIO/3. NHAC VIET TRU TINH TRONG NUOC/Mỹ Tâm Vol.9/My Tam - Lanh Lung.wav) md22 means disk22, then delete/restore those files from backups, when all files are deleted or replaced run another scrub to confirm there are no more errors.

Disk dropped offline, so there's no SMART, check/replace cables and post new diags.

Try recreating the flash drive, first backup current one, then recreate it manually or using the USB tool, then restore from the backup only the bare minimum: key file, super.dat and the pools folder, test if the array works correctly.

Enable the syslog server and post that after a crash.

There's nothing relevant logged, this usually points to a hardware related issue, make sure you take a look here, even if it was working before, there have also been some reports that with some boards you need to completely disable C-states for stability with Ryzen.

So you are using the old parity drives? And yes it's normal for the speed to be slower when it's correcting errors.

For now I would recommend not using Firefox with the GUI, might be resolved with a newer Firefox release.

If you're using v6.11.2 it's a known issue, v6.11.3 with that fixed should be available very soon, but for now you can downgrade to v6.11.1

If you're using v6.11.2 it's a known issue, v6.11.3 with that fixed should be available very soon, but for now you can downgrade to v6.11.1

You can do a parity check after the sync, but if the sync completes at a normal speed without any errors all should be OK.

Log is lost after every reboot, if it keeps happening enable the syslog server and post that after a crash.

That suggests a vdisk already exists in that path (/mnt/user/domains/Windows 10/vdisk1.img)

If you are using v6.11.2 it's a known issue, you need to wait for v6.11.3 or downgrade to 6.11.1 to format any disks >2TB.

No, SATA controller does not work with a SAS expander, in some Intel chipsets the 4 SCU ports support SATA and SAS, those could be connected to a SAS expander, e.g., Supermicro X9DR3-LN4F+.

It's detecting new errors after the correcting check, start by running memtest.

The GUI does not reflect the checkbox, but parity won't be overwritten if it is checked.

If there's no reason to suspect issues with any of the data drives you can replace the parity drives now, but in that case do not check "parity is already valid", parity will be synced after first array start.

There's no HBA/IT mode for the onboard SATA, it's a regular AHCI SATA controller, but it can be used with Unraid without any issues, and the Intel SATA controller is one of the best you can use.

Redoing the flash drive should solve it in that case, backup, recreate, restore the config folder.

You can use the onboard SATA controller for 10 devices, but if the backplane include a SAS expander you cannot connect it to the onboard SATA controller, you need a SAS HBA, like the LSI 9211-8i, 9207-8i, etc in IT mode, MegaRAID models are not recommended.

If the backplane includes a SAS expander you just need one miniSAS cable from the HBA to access all devices, chek the model, it should be printed on the backplane. That's a MegaRAID controller and those usually cannot be flash to IT mode.