JorgeB

Check settings for the parity check plugin (or try uninstalling it to confirm if it's that).

A reboot might actually help with that error, but post new diags if the same, also if using Firefox try a different browser, it can sometimes cause that issue (all disks unmountable) if you hit resend on a popup, a reboot would fix it.

Looks like flash drive problems, run chkdsk on it.

Stop array, type:
zpool import -f raid then
zpool export raid start array and it should import now.

Unassign the parity drive you want to use, start array, stop array, now you can use it to replace a data disk.

You are not deleting the disk, your are deleting a path, format will always fail if that path already exists before Unraid tries to create it, the question is way it exists, possibly a container has that mapping and is creating it.

You can try cloning it with ddrescue, success or not will likely depend on how large the failure is.

Unraid will monitor SMART and you can run regular scrubs, like mentioned NVMe devices don't support SMART tests.

Yes, if current filesystem is btrfs (or zfs for mirroring only).

Jul 16 16:27:41 Husky  emhttpd: unclean shutdown detected  
An unclean shutdown will result in a parity check, did you reboot the server yesterday or it's rebooting on its own?

Enable turbo write and re-test writing directly to the array.

Cache is not mounting, this may help:
 
btrfs rescue zero-log /dev/nvme0n1p1  
Then re-start array.

Disks 1 and 2 are SMR, disk1 model especially have been known to be extra slow sometimes, if you limit writes to disk3 is it normal?

Jul 22 02:22:20 halliday kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jul 22 02:22:20 halliday kernel: ? _raw_spin_unlock+0x14/0x29 Jul 22 02:22:20 halliday kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

If the pool was created with no swap on Truenas it should be imported, and it won't damage the pool if it can't be 

This may help:
btrfs rescue zero-log /dev/sdi1  
Then re-start array.

Nothing relevant logged, do you know what time it crashed? Also please post the diagnostics.

ATA errors for disk1, start by replacing those cables.

By the description looks like a hardware issue, those usually don't leave anything relevant logged, one thing you can easily test is the RAM, remove one stick, if still issues try the other one, if you get crashes with either it would basically rule out RAM issues.

You are having issues with multiple disks, check/replace cables on disks 11 and 23 and try again.

Correct.

Jul 15 16:25:46 NASkingdom emhttpd: status: One or more devices has experienced an error resulting in data Jul 15 16:25:46 NASkingdom emhttpd: corruption. Applications may be affected. Your pool has corrupt data, since it's also crashing on import you can try importing the pool read-only then backup and re-create, unassign the pool, start the array and type:
 
zpool import -o readonly=on starlight  
If it works copy what you can somewhere else, the corrupt files will fail to copy, you can get a list with:
 
zpool status -v starlight  
Also a good idea to run memtest.

Start here:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
 

Yes, at least when it's writing to those.

It's rebuilding the formatted (empty) disk, if the old disk is really dead and assuming no backups bet is a using a deleted file recovery util like UFS explorer.