JorgeB

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

You need to find what's causing the cache unmount to fail, are you on v6.12.10?

You just need to copy the config folder, everything config/settings related is there, the rest of the flash drive can be recreated.

Any errors should be logged in the syslog, but if a device is just being extra slow, but without timing out, nothing will be logged.

Nope, there's nothing out of the ordinary logged.

I'm not, but I'm familiar with other IPMI implementations, from Supermicro for example, and those should don't interfere with the other NICs, main issue as I see it, it that no link is being detected on the Intel NICs, only on the "phantom" USB NIC.

If you do it after typing reboot it should be OK, since most times it can unmount the array disks.

Apr 15 05:08:58 Serenityv2 kernel: usb 2-4: USB disconnect, device number 2 Apr 15 05:08:58 Serenityv2 kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. Apr 15 05:08:58 Serenityv2 kernel: usb 2-4: new SuperSpeed USB device number 3 using xhci_hcd Apr 15 05:08:58 Serenityv2 kernel: usb-storage 2-4:1.0: USB Mass Storage device detected Apr 15 05:08:58 Serenityv2 kernel: scsi host32: usb-storage 2-4:1.0 Apr 15 05:08:58 Serenityv2 emhttpd: Unregistered Flash device error (ENOFLASH5) Apr 15 05:08:58 Serenityv2 emhttpd: error: put_config_idx, 610: No such file or directory (2): fopen: /boot/config/shares/Movies.cfg Apr 15 05:08:58 Serenityv2 emhttpd: error: put_config_idx, 610: No such file or directory (2): fopen: /boot/config/shares/Music.cfg Flash drive dropped offline, try a different USB port, ideally USB 2.0

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. P.S. I see that you have CoreFreq installed, would recommend removing that one first and re-testing, since it has been known to crash some servers.

Reboot is the same, it will try a clean shutdown first, failing that will try an unclean one, and

Also make sure you do the above, and reset the btrfs stats to see if new corruptions are detected.

According to the diags, there's no disk activity going on, I do see you have a SMR disk for parity, try unassigning parity to leave that disk out and retest.

Correct, other drivers won't matter. The strange thing here, is that based on the diags, you have 5 NICs on the server, 1 USB NIC, 2 Intel gigabit NICs, 2 Intel 10GbE NICs, and the only one with a cable connected is the USB NIC, and you say there's no USB NIC... But it should work if you use one of the Intel gigabit NICs, they are using the correct driver, but they don't have a link, or at least one is not detected.

Not sure what you mean, the drivers are loaded by Unraid and cannot be updated. Post new diags with the cable connected to the other gigabit NIC.

Diags appear to be after a reboot, when it happens again post new diags before rebooting. Also see that btrfs is detecting data corruption in the pool: Apr 14 16:58:16 Tower kernel: BTRFS info (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 526, gen 0 Run a scrub and delete/restore from a backup the corrupt files, also a good idea to run memtest