JorgeB

Can you access the flash drive if you export that publicly?

You can try at least to replace the cables/splitters for the affected disks, then try rebuilding again (check that the emulated disks are still mounting and contents look correct before rebuilding on top)

Disks were already disabled at boot, so we can't see what happened, but they look healthy, so most likely a power/connection issue. If you are happy with the emulated disk1 contents, check/replace cables for those disks, especially if they share something like a power splitter, then rebuild: https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

Not logged as a disk problem, do those disks share anything like a power splitter?

Parity disk doesn't have a partition; open a terminal window and type sgdisk -o -a 8 -n 1:32K:0 /dev/sdX Replace X with the correct parity identifier, sdg from the diags, but this can change if you reboot. After that, reboot the server and see if it now works.

Device is still dropping. If it still happens on a different m.2 slot, best bet it to use a different brand/model device (or a different board if that's easier)

That is for LT internal use, you should disable Enable Developer Sandbox in Settings - Management Settings - Unraid API settings.

Also looks like a power/connection issue with disk1. Any power splitters in use?

Diags still show plugins being installed, can you confirm what you mean by plugins gone? Don't they not show in the plugins page?

Read bandwidth increased substantially; the last one shows 743MB/s, but writes still seem low, any improvements in the expected resilver time?

How are you trying to re-enable the disk, are you doing this? https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

Don't see any obvious issues logged; is it better in safe mode?

When it's the CPU, it's not detected by memtest; the best way to detect it is what you are seeing, Unraid driver crashing during a parity check or sync, there can also be other issues logged.

Please post the diagnostics to see if there's something there

Since no errors were found, clear the stats for the pool and keep monitoring, they are likely old errors.

This suggests some hardware issue, did you save those diags?

Sorry, my mistake, this is a different issue, the issue that is resolved is when you get sent back to the login page: https://product.unraid.net/b/unraid-os-bugs/p/7-3-1-connect-login-loop-from-unraid-api-socket-path-mismatch For the issue you are having, you can follow this bug report: https://product.unraid.net/b/unraid-os-bugs/p/cannot-register-server-into-connect

It's not logged as a disk problem and SMART looks fine, so most likely a power/connection issue. Check/replace cables for that disk, then start the array, confirm the emulated disk is still mounting, and if yes and contents look correct you can then rebuild on top https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

There was an issue with the account app; it should be fixed now, please try again.

There was an issue with the account app; it should be fixed now, please try again.

Unraid driver is crashing; this is almost always a hardware issue, and considering you are using a 14600K, it's by far the #1 suspect.

There was an issue with the account app, it should be fixed no, please try again.

Yep

Jun 13 16:28:11 NAtaSha kernel: device offline error, dev sda, sector 8799 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): FAT read failed (blocknr 607) Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): unable to read inode block for updating (i_pos 38223365) Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): FAT read failed (blocknr 607) Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): FAT read failed (blocknr 607) Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): unable to read inode block for updating (i_pos 38223365) Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30176) failed Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30177) failed Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30178) failed Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30179) failed Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30180) failed Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30181) failed Syslog shows flash drive problems, try recreating it, if they persist, use a new one

This is normal if there's no parity2 Please post the diagnostics.