Hello, good evening, how are you? When it happened to me, you helped me with these steps that I have saved since then:
- Reboot MacOS into Recovery Mode
- Open Disk Utility, mount the Data volume and quit Disk Utility
- Launch the Terminal in Recovery Mode
- Search for the file by inode id with the following command:
find /Volumes/Data/ -inum ########
(where ######## is the inode id number of the file)
Now in your results you may find the file but for me there were no results but a few errors like:
/Volumes/Data/.Spotlight-V100: No such file or directory
So to get around this I searched directly within the directories they say didn't exist as follows:
find /Volumes/Data/.Spotlight-V100 -inum ########
Once I did that I was able to find each of the files within the Spotlight directory hierarchy. Now I could not find a way to add the missing resource fork so it was easier to rebuild the Spotlight index. To ensure I did that cleanly, I rebooted into normal mode and did the following:
- Within the System Settings rebuild the Spotlight index by adding the Macintosh HD to the Privacy pane
- Next, reboot MacOS into Recovery Mode
- Open Disk Utility, mount the Data volume and quit Disk Utility
- Launch the Terminal in Recovery Mode
- Confirm that the file in question has been marked for removal by the following command:
find /Volumes/Data/.Spotlight-V100 -inum ########
In the results you will note that the file is still present but is within the following path:
/Volumes/Data/.Spotlight-V100/Store-V2/DeadFiles
You can remove this entire path manually by issuing the following command:
rm -rf /Volumes/Data/.Spotlight-V100/Store-V2/DeadFiles
Once this path is removed you can rerun the Disk Utility to confirm that the errors regarding "Resource Fork xattr is missing for compressed file" have all been resolved. You can then re-enable your Spotlight index by removing the Macintosh HD from the Privacy pane.
P.S. If you have other files showing up as warnings, they may exist in other paths and you can manually search these paths as well. Do so with caution since Terminal in Recovery Mode is a very powerful tool and can cause harm to your Mac if not used responsibly. But, in any case the best advice I can give being just an Apple user just like you, is to go to an authorized physical store to get the necessary repair done. Good luck, and excuse my broken English! 😅