JorgeB

Then you'll need to contact LT to transfer the basic key first, since it's been less than a year.

You just need to create a new install on the pro key then copy the complete config folder from the other key except the license.

It's not working correctly, it's full of these: Nov 16 10:36:39 Tower rsyslogd: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Check config.

If it's not a RAM issue could be corrupt LUKS headers, do you have a backup of those? In any case two simultaneously disable disks is usually not a disk problem, SMART looks OK for both and they are on a SASLP which is not recommended for Unraid and known to drop disks sometimes, so you might want to check if the actual disks mount with UD and if yes re-sync parity instead. Also I wouldn't recommend encryption unless you absolutely needed it, it's just another layer of complexity, but if you keep using it make sure you backup the LUKS headers.

Yes, it's a known issue.

File is too large to open, even with Notepad++, delete/rename that one, start a new syslog server and post that after a crash.

Nov 16 07:19:58 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Nov 16 07:19:58 Tower kernel: nvme nvme0: Removing after probe failure status: -19 Device is dropping offline, try a different m.2 slot if available, or a different NVMe device.

This is usually a flash drive issue, backup the config folder and redo it.

Enable the syslog server and post that log after a crash.

If you keep getting filesystem corruption without an apparent reason there's likely some hardware issue, start by running memtest.

Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)).

Please post the diagnostics.

Sync errors will be correct on parity disk only, nothing is written to any data disk (well except sometimes if there's a read error on a data disk, but you still need to run a correcting check now)

Run a correcting check, a few sync errors after an unclean shutdown are normal. Oct 1 20:50:16 PhelpsTower emhttpd: unclean shutdown detected

Diags are after rebooting but the btrfs dev stats do suggest that one of the devices dropped offline before, this is not necessarily a device problem, you can redo the pool and if it happens again post new diags before rebooting.

Please post the complete diagnostics, the earlier syslog snippet is irrelevant for this and looks like the device dropped offline, and that is missing.

I would expect it does, but don't have one to confirm nor do I remember someone else confirming it. Looks like it.

Btrfs is detecting data corruption, running Ryzen with above max officially supported speeds is known to cause data corruption is some cases, see here.

Try replacing or swapping cables with a different disk, but possibly disk is really failing, despite a good looking SMART.

Test failed, disk should be replaced.

LSI 93xx HBAs support trim, but only on devices with deterministic trim support. You can check that yourself: https://forums.unraid.net/topic/74493-samsung-ssd-hba-trim/?do=findComment&comment=713011

Array devices can't be trimmed, not currently anyway, you can still use them there but there could be some write speed degradation with time. Just disable SMART attribute 197 monitoring.

Try uninstalling the plugin, delete the /boot/config/plugins/ipmi folder, then re-install it.

I'm also using Chrome, and it still works with rc1, this server has multiple NICs, so I'll attach the diags in case it helps. test2-diagnostics-20211114-1437.zip