JorgeB

Jul 1 13:48:56 Tower kernel: general protection fault, probably for non-canonical address 0x9c0101000034: 0000 [#1] SMP PTI Now there's something, but no Linux module/driver is mentioned, so don't know if it was a software or hardware issue.

You can delete/rename network.cfg and network-rules.cfg then reboot to restore defaults.

It's notoriously difficult to keep Unraid booting with Apple hardware.

Unlikely that is the problem, but you can, if you upgraded using the GUI there's a restore option (Tools -> Update OS)

The pool.

Filesystem might have other damage, like the other issue, recommend backup and re-format.

This is usually flash drive related, try re-creating it or use a different one without a key, just to test.

Strange the call traces not being in the log, cannot see the reason for the one in the screenshot.

Jul 1 16:29:19 Tower kernel: mpt2sas_cm0: SAS host is non-operational !!!! It's a problem with the HBA, it stops responding and Unraid loses contact with all disks, make sure it's sufficiently cooled, well seated and/or try a different PCIe slot if available, failing that try a different HBA.

If the power supply idle control setting change doesn't help enable the syslog server and post that after a crash.

I replied above.

Then please post that.

Was taking a second look since the first one was on the phone and it's not so easy to look at the log, and I did miss this line: Jun 30 17:43:58 Kaokulk kernel: BTRFS error (device nvme0n1p1): incorrect extent count for 19382927360; counted 1535, expected 1532 Fs is not going read-only, so this might not be the problem, but it is a problem, first time I remember seeing this error, so not sure how serious it is, you should make sure backups are up to date and attempt to repair the filesystem, or backup and re-format the pool, there's also this which I saw before: Jun 30 17:43:51 Kaokulk kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 Jun 30 17:43:51 Kaokulk kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Some data corruption was found at some time earlier, it might be from a while ago, still this is usually a sign of bad RAM or other hardware issue, if you don't re-format the pool you should reset the stats ad keep monitoring.

Correct. Before this was done by the GUI, but IIRC it was kind of a hack, and it didn't always work correctly, so it has to be done manually for now.

Try a different NIC if available, ideally an Intel one.

Resume from sleep it's not officially supported, in part because it's difficult to confirm all hardware works correctly with it, if you'd like to keep using it I suggest connecting that disk to a different controller if available or using a different model disk.

Did you notice if the 2 errors are on the same sectors? They are very close together, if you didn't correct parity and post new diags when it finds more sync errors.

That confirms it's a network problem, usually, NIC, switch, cables, etc.

Docker image is corrupt, delete and re-create.

It should mount after running xfs_repair.

Yes, but it's not 20.00.07.00

Start by running a single stream iperf test in both directions to see if it's network related.

Crashing while idle is a known Ryzen issue, see here.

You should also enable the syslog server and post that after a crash.

With 6.10 Unraid makes you disable spindown before being able to run a SMART test to avoid this exact issue.