JorgeB

Run a correcting check, then a non correcting one without rebooting, if the 2nd one finds new errors post new diags.

Try this:
https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009
 

It's up to you, if the server is not being heavily used probably the same risk to leave it on, btw the disk dropped offline, most likely a power/connection issue, but since it dropped there's no SMART report.

Yes, do that.

If the log tree is the only problem this may help:
btrfs rescue zero-log /dev/sdb1  
Then re-start the array

Parity is SMR, so it will slowdown all writes.

Make sure the shares are being exported, default is no, click on the share(s) and scroll down to Export:

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.

Yep.

It's a logged as a disk error, and the disk has pending sectors, so likely it's failing, you can run an extended SMART test to confirm.

Disk needs to be replaced.

Create a new flash drive and restore the config folder, that's all you need, then need to replace the key.

Nov  6 20:55:29 As-NAS kernel: BTRFS critical (device loop2): unable to find logical 18413109156024856576 length 4096 Nov  6 20:55:29 As-NAS kernel: BTRFS critical (device loop2): unable to find logical 18413109156024856576 length 16384  
Docker image is corrupt, delete and recreate.

The NVMe device is dropping offline, try this, on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot"
nvme_core.default_ps_max_latency_us=0 pcie_aspm=off e.g.:
append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off
Reboot and see if it makes a difference.

 

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
 

Nov  4 11:02:03 NAS kernel: mpt2sas_cm0: SAS host is non-operational !!!! Nov  4 11:02:04 NAS kernel: mpt2sas_cm0: SAS host is non-operational !!!! Nov  4 11:02:05 NAS kernel: mpt2sas_cm0: SAS host is non-operational !!!! Nov  4 11:02:06 NAS kernel: mpt2sas_cm0: SAS host is non-operational !!!! Nov  4 11:02:07 NAS kernel: mpt2sas_cm0: SAS host is non-operational !!!! Nov  4 11:02:08 NAS kernel: mpt2sas_cm0: SAS host is non-operational !!!!  
HBA problem, make sure it's well seated and sufficiently cooled, or try a different PCIe slot if possible.

Type:
 
zpool import -f bignfast zpool import -f superfast zpool export bignfast zpool export superfast Then re-start array
 

You are using a controller with a SATA port multiplier, and 4 of the disks are sharing the same SATA port, so bandwidth is affected a lot, see here:
 

Just copy the key to the new flash drive (delete any other existing keys) and then use the replace option, if your key was last replaced less than a year ago, you will need to contact support.

Suggest just restoring the bare minimum to the new flash drive, like the key, super.dat and pools folder for the assignments, docker user templates, then just reconfigure the rest or restore a few files at a time until you find the culprit.

Oct 4 13:46:56 BigNAS nginx: 2023/10/04 13:46:56 [error] 10889#10889: *211567 limiting requests, excess: 20.851 by zone "authlimit", client: 192.168.0.185, server: , request: "PROPFIND /login HTTP/1.1", host: "192.168.0.34"  
I assume "client: 192.168.0.185" is your desktop? If yes try closing all browser windows opened to the GUI, only open when you need to interact with it and then close.

You can try force-enable parity and see if they can emulated disk6, it 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
-IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked)
-Stop array
-Unassign disk6
-Start array (in normal mode now) and post new diags.

A lot of call traces, they look more hardware related, try with just RAM stick, if the same try a different one, that will basically rule out RAM.

Avoid controllers with SATA port multipliers, see here: