JorgeB

Assuming you are using btrfs only for the pool(s) you can try clearing the space cache, it should be pretty safe to run but always good to make sure backups are up to date: With the array stopped: btrfs check --clear-space-cache v2 /dev/sdX1 If this is an old pool that might have v1 space cache also run: btrfs check --clear-space-cache v1 /dev/sdX1 It won't hurt if there's no v1 cache

You cannot remove a drive from a pool using the single profile (or other non redundant profile), please post current diags after a new reboot and before array start.

Try with just one cable, Unraid doesn't support SAS multipath.

MC won't work AFAIK, if you have enough space on cache you can use mv /mnt/path/to/vdisk.img /mnt/path/to/vdisk.old cp --sparse=always /mnt/path/to/vdisk.old /mnt/path/to/vdisk.img rm /mnt/path/to/vdisk.old If there's not enough space on cache move to array then copy back with --sparse=always.

Safe mode is a boot option in the Unraid boot menu.

Disk problem, IMHO best bet is to clone that disk with ddrescue then run xfs_repair again, you can then used the cloned disk with old disk3 since that one looks healthy and re-sync parity.

Does it happen right after boot or after some time? If after boot try booting in safe mode.

Can you see where in the boot process it reboots? Also safe boot still works correct?

Not sure, don't remember previous complains, but let me see if I can duplicate that.

Different apps crashing, start by running memtest.

Restarting the server might bring it back, recommend checking/replacing the cables for that device.

Try to get new diags during the problem but with the VM shutdown.

That was sdb.

OK, there have been a couple of other reports, so there's possibly some issue the the latest releases validating some keys, I've already reported the issue to LT so Tom can find out what's going on.

Do you know which was the previous release you were running?

Nov 23 16:12:44 tower kernel: ata7: hard resetting link Nov 23 16:12:54 tower kernel: ata7: softreset failed (device not ready) Nov 23 16:12:54 tower kernel: ata7: hard resetting link Nov 23 16:13:04 tower kernel: ata7: softreset failed (device not ready) Nov 23 16:13:04 tower kernel: ata7: hard resetting link Nov 23 16:13:14 tower kernel: ata7: link is slow to respond, please be patient (ready=0) Nov 23 16:13:39 tower kernel: ata7: softreset failed (device not ready) Nov 23 16:13:39 tower kernel: ata7: limiting SATA link speed to 3.0 Gbps Nov 23 16:13:39 tower kernel: ata7: hard resetting link Nov 23 16:13:44 tower kernel: ata7: softreset failed (device not ready) Nov 23 16:13:44 tower kernel: ata7: reset failed, giving up Nov 23 16:13:44 tower kernel: ata7.00: disable device One of the devices dropped offline, looks like it was cache, syslog rotated so can't see the beginning.

Nov 22 16:54:06 BIGDADDY kernel: ata1: link is slow to respond, please be patient (ready=0) Nov 22 16:54:11 BIGDADDY kernel: ata1: COMRESET failed (errno=-16) Nov 22 16:54:11 BIGDADDY kernel: ata1: hard resetting link Nov 22 16:54:16 BIGDADDY kernel: ata1: link is slow to respond, please be patient (ready=0) Nov 22 16:54:21 BIGDADDY kernel: ata1: COMRESET failed (errno=-16) Nov 22 16:54:21 BIGDADDY kernel: ata1: hard resetting link Nov 22 16:54:26 BIGDADDY kernel: ata1: link is slow to respond, please be patient (ready=0) Nov 22 16:54:56 BIGDADDY kernel: ata1: COMRESET failed (errno=-16) Nov 22 16:54:56 BIGDADDY kernel: ata1: limiting SATA link speed to 3.0 Gbps Nov 22 16:54:56 BIGDADDY kernel: ata1: hard resetting link Nov 22 16:55:01 BIGDADDY kernel: ata1: COMRESET failed (errno=-16) Nov 22 16:55:01 BIGDADDY kernel: ata1: reset failed, giving up Nov 22 16:55:01 BIGDADDY kernel: ata1.00: disable device Cache device dropped offline, this is usually a cable/connection problem.

Does it get better if you shutdown the CCTV VM?

Nov 23 15:07:27 Khaleesi emhttpd: device /dev/sdk problem getting id Nov 23 15:07:27 Khaleesi emhttpd: device /dev/sdy problem getting id These usually mean the same devices are being detected twice, do you have more than on cable connecting the HBA to the NetApp enclosure?

Please post the diagnostics

You can try installing this driver https://forums.unraid.net/topic/123638-unraid-6115-最新的r8125和r8152网卡驱动补丁/

Might be a good idea to enable the syslog server to see if it catches something if it happens again.

You can do that with cp --sparse=always

Du is not reliable with btrfs, GUI/df will show correct used space.

Difficult to say where the problem is, if you can I would start by testing with a different RAM pair, and yes you can just use 1 stick.