JorgeB

Some olders CPUs may not be correctly supported by the stock Linux drivers, or the board is not passing through the correct info.

Disable and reenable the Discord agent; that's needed to make the change

You can uise this https://forums.unraid.net/topic/46802-faq-for-unraid-v6/#findComment-511923

Yes, it starts a normal shutdown like the other one.

Disk dropped offline, check/replace its cables and post new diags after array start.

Reset the pool stats and scrub the pool, then post the scrub results if there are any new errors.

Btrfs is detecting data corruption on both pool devices, this is most often bad RAM, first suggestion is to run memtest.

14600K could be the Intel 13/14 gen issues, but enable the syslog server and post that after the next crash.

Correct. It also depends on the size of drives, but typically up to around 8 drives can be OK with raidz1

If you are running Windows 11 24H2 or newer see https://forums.unraid.net/topic/177975-formatted-my-pc-and-installed-fresh-windows-11-now-cant-access-smb-shares/?do=findComment&comment=1478526

Yep, those are no longer needed with 7.3

May 14 13:17:19 Highbrow kernel: BTRFS info (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 0, flush 0, corrupt 862, gen 0 May 14 13:17:19 Highbrow kernel: BTRFS info (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 850, gen 0 Btrfs is detecting a lot of data corruption. This is typically bad RAM, and could be related to xfs_repair failing, if the RAM really is failing, recommend running memtest first.

Try disabling the stock UPS service and using the NUT plugin instead; there appears to be an issue with the newer kernel and a few APC models.

NVMe devie is droping offline: May 11 13:07:16 Enterprise kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 May 11 13:07:16 Enterprise kernel: nvme nvme1: Disabling device after reset failure: -19 See if this helps: on Main click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off Reboot (or power cycle the server if just a reboot doesn't bring the device back) and then see if it makes a difference.

Please start a new thread in the general support forum and post the diagnostics.

This is normal; parity can't help with filesystem issues. My first recommendation would be to update to 7.3.0 since it includes newer xfs-progs, then try running xfs_repair again. If it still fails, post the diagnostics.

Make sure this has been taken care of: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Export the pool manually by typing zpool export cache Then, on main click on the first device for that pool and then "remove pool" back on main, create a new pool with the same name and number of slots assign the pool device(s), leave the filesystem set to auto start the array to import the pool

I saw another user with the same issue, so it appears there is some problem there, LT is aware.

The devices are not being partitioned; please post the diags after trying to create a boot pool but before rebooting.

There are two invalid disks with single parity, so it's not possible to recover the array as is. If you still have the missing disk2 you can then resync parity; if not, you will likely lose the data from disk2, in case it's important.

Pool health is now monitored by Unraid; because of that, users can get a warning that one or more pool devices have issues after upgrading. The upgrade doesn't cause the warnings; they were just not monitored before. Anyone needing help with that should create a new thread in the general support forum and post the diags.

Couple of read errors, likely old; click on the first pool device and then RESET stats, after that keep monitoring; if more errors show, you post the diags before rebooting.

This was a fix for 7.3 beta/rc, 7.2 was not affected by that.

7.2 will have the same pool errors; it just won't warn you about them. If you need further help, please create a new post in the general support forum and post the diags, this thread is not the best place for troubleshooting