JorgeB

Yes, but for best results do the rebuild in maintenance mode.

Lots of errors like these: Nov 21 17:47:08 NODE kernel: CIFS: VFS: \\GC02DF65ZMD6TE has not responded in 180 seconds. Reconnecting... Nov 21 17:47:25 NODE kernel: CIFS: VFS: \\NZXT\Laurent error -11 on ioctl to get interface list Nov 21 17:50:06 NODE kernel: CIFS: VFS: \\GC02DF65ZMD6TE\lecoutre error -11 on ioctl to get interface list Nov 21 17:57:47 NODE kernel: CIFS: VFS: \\NZXT\Laurent error -11 on ioctl to get interface list Nov 21 18:00:28 NODE kernel: CIFS: VFS: \\GC02DF65ZMD6TE\lecoutre error -11 on ioctl to get interface list Are these UD mounts?

Do you have a monitor connected or IPMI? Do you see that Unraid finished booting? If yes grabs diags or the syslog from the console.

Not really, this is one the slowest SSDs you can get, and they then to get slower with time, recommend getting a better one like the Crucial MX500 or Samsung 870EVO.

This has been reported to help with that: https://forums.unraid.net/bug-reports/stable-releases/6103-samsung-980-temp-warning-r2007/?do=findComment&comment=20180

Diags you posted don't show any disk7 errors, maybe you've posted the wrong ones?

Disk5 was already disabled in the diags and it looks healthy, parity dropped offline, because of that there's no SMART but this is usually a power/connection problem, if you've already changing everything else the backplane is a good possibility.

See if you can get the diagnostics, if not at least get the syslog: cp /var/log/syslog /boot/syslog.txt then type 'reboot' in the console.

It's not a quirk issue, also quirks are only needed for some devices when there are two of the same model: Nov 26 12:50:40 Tower kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 Nov 26 12:50:40 Tower kernel: nvme nvme0: Does your device have a faulty power saving mode enabled? 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.

Looks like the VMs are not suspending in the set time, you can test by stopping the array, and see how long it takes.

SMART for parity was missing from the previews diags, now it's there and showing pending sectors, so it looks like the disk failed, you can confirm by running an extended SMART test.

Recommend using COW even if using a single device pool, pretty much required with multi device pools.

Looks like you are missing some files, backup current flash drive, recreate it manually or by using the USB tool, restore the config folder from the backup.

That would point to appdata being the problem, you can move to the array share by share to see what it is.

Your are missing the 1 in the end: /dev/sdX1

Cannot see what exactly happened since the diags are after rebooting but no btrfs filesystem is being detected on either cache device, try this in case one or both were wiped: btrfs-select-super -s 1 /dev/sdX1 Do it for both devices, replace X with correct letter, if the command is successful for one or both reboot and post new diags.

WD Black should be very similar to WD Red Pro for performance and reliabilty, but Red Pro should have better vibration protection for multi disk use, if the marketing is to be believed, WD Black are geared more for desktop use.

@dlandonmight be able to help.

You also need to re-add the apps, basically follow the instructions from the screenshot you posted above.

Do this.

get at least the syslog: cp /var/log/syslog /boot/syslog.txt

Post new diagnostics.

That will depend on the state of the disk, not much more you can other than wait.

This.

Please post the diagnostics.