It could be completely anecdotal but I never had this error on any other version of unraid including the the Unraid 7 release candidates.  Asking on reddit it appears a few others have been having the same issue where my system will run find for a while then suddenly docker quits working and I'm forced to do a reboot. After reboot it works fine all over again.  I'm attaching errors I'm seeing with my NVME drive. The only thing on the drive is the Appdata. It passed it's smart test without issue and says it still has 91% endurance left. Total it has about 1.5yrs of time on it. 

 

Is my drive failing or is there something that makes it arbitrarily lockup? Could doing an appdata backup cause the issue? I'm manually performing one now to see if I can recreate the problem.  Once I reboot things are fine and the system runs as intended for another couple weeks then it will happen again.

 

tower-syslog-20250219-1821.zip.crdownload

Feb 19 08:07:25 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1
Feb 19 08:07:25 Tower kernel: nvme nvme0: Disabling device after reset failure: -19

 

NVMe device is dropping offline, you can 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 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 and see if it makes a difference.

 

 

Also check filesystem on disk18:

Feb 19 08:07:01 Tower kernel: XFS (md18p1): Unmount and run xfs_repair
Feb 19 08:07:01 Tower kernel: XFS (md18p1): First 128 bytes of corrupted metadata buffer: