Time Machine issue after updating to macOS Ventura

Question

Level 1

32 points

Time Machine issue after updating to macOS Ventura

Occasionally, I run Disk Utility and diskutil via Terminal to check things. Prior to this update, which was done about 4 days ago, there were no warnings. Now all of the snapshots and fsroot tree are repetitively followed by these two lines:

warning: inode (id 3496332): Resource Fork xattr is missing for compressed file

warning: inode (id 9549766) Resource Fork xattr is missing for compressed file

In spite of this, the volume of course appears to be OK. The computer runs fine.

Over the past three or four days I have done the Safe restart several times. The external HD and SSD that this MacBook Pro are backed up to have been checked. So far, those have no warnings about inode or resource forks. Backups done since the update have shown no problem during the course of their runs.

Finally, the SSD of this MacBook Pro M1 is newfs_apfs (1933.80.3) and last modified by apfs_kext (2142_41.2)

Suggestions?

MacBook Pro 16″, macOS 13.0

Posted on Oct 26, 2022 7:24 AM

Reply

Answer 1

Oct 26, 2022 7:50 AM in response to jordanfelk

jordanfelk wrote:

Occasionally, I run Disk Utility and diskutil via Terminal to check things. Prior to this update, which was done about 4 days ago, there were no warnings. Now all of the snapshots and fsroot tree are repetitively followed by these two lines:

warning: inode (id 3496332): Resource Fork xattr is missing for compressed file

warning: inode (id 9549766) Resource Fork xattr is missing for compressed file

In spite of this, the volume of course appears to be OK. The computer runs fine.

Over the past three or four days I have done the Safe restart several times. The external HD and SSD that this MacBook Pro are backed up to have been checked. So far, those have no warnings about inode or resource forks. Backups done since the update have shown no problem during the course of their runs.

Finally, the SSD of this MacBook Pro M1 is newfs_apfs (1933.80.3) and last modified by apfs_kext (2142_41.2)

Suggestions?

Repair a storage device in Disk Utility on Mac - Apple Support

Reply

Answer 2

jordanfelk Author

Level 1

32 points

Oct 31, 2022 7:47 PM in response to leroydouglas

I have been out of town intentionally without the computer so I just found your response leroydouglas. Here is a quick summary of diskutil list internal:

As I said earlier, the APFS Volume of Data that is now disk3s1 use to be and had been disk3s5 for sometime without a problem. Like you, I doubt the problem was simply the volume's location. Rather, something went wrong in the first laying out of Ventura. Rather than just wait and see if things kept working with just the those few blips I saw, I decided take the steps I took last week.

Reply

Answer 3

jordanfelk Author

Level 1

32 points

Oct 26, 2022 12:47 PM in response to leroydouglas

Disk Utility is the source of the information I have posted and has been run several times making no difference, whatsoever. Via Terminal, I have run diskutil's verifyVolume and was given the same information.

What steps have I missed on the Apple Support page that might make a difference?

Reply

Answer 4

jordanfelk Author

Level 1

32 points

Oct 27, 2022 6:19 AM in response to jordanfelk

I will reply to myself on solving this problem.

I, simply restarted in Recovery mode, after a Time Machine backup, to erase and then reinstall Monterey. After putting my data back in, I ran both Disk Utility and diskutil and did not find the warnings posted earlier. After upgrading to Ventura I checked things out via both Disk Utility and diskutil and still found none of the warnings.

Note, before wiping the SSD and reinstalling everything my data was stored on "disk3s5" now it is "disk3s1".

Could the problem have been the fact of my original installation of Monterey not making this change? Is it possible that it if you see most of the significant problems being posted we should always back off and take the necessary time to backup, erase and reinstall?

Reply

Answer 5

Oct 27, 2022 6:45 AM in response to jordanfelk

jordanfelk wrote:

I will reply to myself on solving this problem.

I, simply restarted in Recovery mode, after a Time Machine backup, to erase and then reinstall Monterey. After putting my data back in, I ran both Disk Utility and diskutil and did not find the warnings posted earlier. After upgrading to Ventura I checked things out via both Disk Utility and diskutil and still found none of the warnings.

Note, before wiping the SSD and reinstalling everything my data was stored on "disk3s5" now it is "disk3s1".

Could the problem have been the fact of my original installation of Monterey not making this change? Is it possible that it if you see most of the significant problems being posted we should always back off and take the necessary time to backup, erase and reinstall?

Good computing jordanfelk

Trouble shooting —backup, erase, reinstall only as necessary.

Rule of thumb— if it ain't broke don't fix it.

If it is broke then proceed with known methodologies to resolve the issue. Full stop.

Hard to speculate on your exact issue.

What I can say is the disk numbering system is relative not absolute.

From the Terminal app you can see the complete disk structure, copy and paste:

diskutil list internal

Reply

Time Machine issue after updating to macOS Ventura

Similar questions