inode with missing Resource Fork xattr cannot be fixed.

The section you posted with those errors (or rather warnings) is for an APFS TM backup snapshot #13. Once that snapshot is deleted, then those particular errors/warnings will be gone as well. Usually macOS TM automatically deletes APFS TM backup snapshots in 24-48 hours.

If you encountered those errors or warnings on your "Data" volume, then that would be a problem.

what are the specifics of the “crash“?

Was it a kernel panic?

those warnings are just warnings. They’re not errors and not the cause of whatever crash you experienced. From other posts here the only way to get them to stop appearing is to completely erase the drive and reinstall macOS. Seems like a complete waste of time for something that’s not important.

Barney-15E wrote:

those warnings are just warnings. They’re not errors and not the cause of whatever crash you experienced.

Warnings can cause severe problems as well. I experienced this personally with one of my organization's Macs. It was so severe the volume would not mount and would cause Kernel Panics when trying to mount the volume.

However, with these warnings shown by the OP...if they are only part of the TM APFS snapshot, then they can probably be ignored since that snapshot should automatically deleted within two days assuming the TM backup drive is connected.

HWTech wrote:

Barney-15E wrote:

those warnings are just warnings. They’re not errors and not the cause of whatever crash you experienced.

Warnings can cause severe problems as well. I experienced this personally with one of my organization's Macs. It was so severe the volume would not mount and would cause Kernel Panics when trying to mount the volume.

However, with these warnings shown by the OP...if they are only part of the TM APFS snapshot, then they can probably be ignored since that snapshot should automatically deleted within two days assuming the TM backup drive is connected.

Well that might explain why erasing got rid of them as that would remove the affected snapshots.

If that’s the case, erasing and reinstalling is still a complete waste of time.

Checking snapshot...
 
The volume /dev/rdisk3s5 with UUID A9714661-08A1-4873-A356-B166B578D47B appears to be OK.
File system check exit code is 0.

I would not be concerned about these warnings "missing Resource Fork xattr "

if you are having some bigger issue(?)

then explain what and why you need to run DiskUtility>First AID to begin with for some clarification.

Gentleman_H wrote:

Thanks for your help, everyone.

Doesn't this part of the log indicate that the problem is not only occurring in all snapshots, but also on the volume itself?

The volume /dev/rdisk3s5 with UUID A9714661-08A1-4873-A356-B166B578D47B was found to be corrupt and needs to be repaired.

Snapshots are part of the volume, but are inaccessible until they are manually mounted. Since you did not provide the full First Aid report I cannot say since Apple's logs can be difficult to interpret sometimes.

Barney-15E wrote:

Well that might explain why erasing got rid of them as that would remove the affected snapshots.

If that’s the case, erasing and reinstalling is still a complete waste of time.

Most likely, but we never had the complete report or details.

My guess is since the OP was attempting to restore a file from TM, they may have been accessing a local snapshot instead of the external TM backup drive....very hard to say. Would have been easier to delete the APFS snapshot if that was the case. It is one of the downsides of providing assistance on a forum...the longer wait times to resolve an issue with all of the back & forth.