JorgeB

Maybe.

Server was constantly running out of memory, check your RAM usage, also the cache filesystem detected write time tree block corruption, this is usually bad RAM or or some other kernel memory corruption. To run memtest from the boot flash drive you need to boot in legacy mode, it doesn't support UEFI boot.

From the release notes:

blkdiscard -f /dev//dev/nvmeXn1

Then something else was done after the wipe, you can try the recovery options in the FAQ.

Stop array, unmount the temp mount (umount /x), then on the console type: btrfs-select-super -s 1 /dev/nvme1n1p1 After that, unassign the other cache device (leave the cache pool without any devices assigned), start array for Unraid to "forget" current cache config, stop array, reassign both 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), start array, pool should now mount normally. If you then want to remove a device it can be done manually while pool is raid0 but easiest way is for you to first convert the pool to raid1 then remove one device.

Do you mean raid0? Raid1 would only have 1TB usable. GUI only supports removing devices from redundant pools, like raid1. Pool might still be salvage, if you didn't reboot yet please post the diagnostics: Tools -> Diagnostics

Disk5 dropped offline, this is usually a connection/power problem, replace cables and post new diags after array start.

Please use the existing plugin support thread:

Disk is OK for now, keep monitoring.

If you have console access you can get the diags by typing "diagnostics", also see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

Not just reformat, but you need to delete the existing partition so the new layout is used.

Log is missing some hours, including the start of the problem, but possibly a controller issue, RAID controllers are not recommended, I would recommend replacing the RIAD controller with an LSI HBA, if that's an option.

Tools -> Update OS

According to the syslog there's nothing connected to any of the SATA ports except a 1GB SATA DOM: Aug 1 05:05:18 NAS1 kernel: ata1: SATA link down (SStatus 0 SControl 0) Aug 1 05:05:18 NAS1 kernel: ata2: SATA link down (SStatus 0 SControl 0) Aug 1 05:05:18 NAS1 kernel: ata3: SATA link down (SStatus 0 SControl 0) Aug 1 05:05:18 NAS1 kernel: ata4: SATA link down (SStatus 0 SControl 0) Aug 1 05:05:18 NAS1 kernel: ata5: SATA link down (SStatus 0 SControl 0) Aug 1 05:05:18 NAS1 kernel: ata6: SATA link down (SStatus 0 SControl 0) Aug 1 05:05:18 NAS1 kernel: ata7: SATA link down (SStatus 0 SControl 0) Aug 1 05:05:18 NAS1 kernel: ata8: SATA link down (SStatus 0 SControl 0) Aug 1 05:05:18 NAS1 kernel: ata9: SATA link down (SStatus 0 SControl 300) Aug 1 05:05:18 NAS1 kernel: ata10: SATA link down (SStatus 0 SControl 300) Aug 1 05:05:18 NAS1 kernel: ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 1 05:05:18 NAS1 kernel: ata11.00: ATA-8: AFAYA MDS 1GB, 20111007A10600003959, 111007, max UDMA/133 Aug 1 05:05:18 NAS1 kernel: ata12: SATA link down (SStatus 0 SControl 300) Aug 1 05:05:18 NAS1 kernel: ata13: SATA link down (SStatus 0 SControl 300) Aug 1 05:05:18 NAS1 kernel: ata14: SATA link down (SStatus 0 SControl 300)

Yes. You needed to swap the cable to eth0.

It's because of the RAID controller, used onboard SATA if available, or a HBA.

A brief push of the power button will imitate a shutdown, you can then delete/rename network.cfg and network-rules.cfg (config folder of the flash drive) to reset the lan config, default is DHCP, you can set a fixed IP after.

You don't need to do a new config, just stop the array, unassign parity, start array.

Disks were already disable at boot, so we can't see what happened, check if they have something in common other than the controller, like a power splitter, etc.

No, you can still run the trim plugin, it won't hurt.

Most likely, disk looks healthy.

Yes, I remember sometime ago someone using a 9th/10th gen CPU on a 7th/8th gen Supermicro board, or vice versa, and it posted but it kept crashing.

Cache device dropped offline, this is a hardware issue: Aug 1 08:28:28 Tower kernel: ata6: link is slow to respond, please be patient (ready=0) Aug 1 08:28:33 Tower kernel: ata6: COMRESET failed (errno=-16) Aug 1 08:28:38 Tower kernel: ata6: link is slow to respond, please be patient (ready=0) Aug 1 08:28:43 Tower kernel: ata6: COMRESET failed (errno=-16) Aug 1 08:28:48 Tower kernel: ata6: link is slow to respond, please be patient (ready=0) Aug 1 08:29:18 Tower kernel: ata6: COMRESET failed (errno=-16) Aug 1 08:29:18 Tower kernel: ata6: limiting SATA link speed to 1.5 Gbps Aug 1 08:29:23 Tower kernel: ata6: COMRESET failed (errno=-16) Aug 1 08:29:23 Tower kernel: ata6: reset failed, giving up Aug 1 08:29:23 Tower kernel: ata6.00: disabled See if new cables help.

Looks more like a connection/power problem on disk2 and parity, replace those cables.