Volume /dev/rdisk1s1 found to be corrupt and needs to be repaired

Hi

My mac pro 13 inch 2020 has been going berserk.

Not sure what happened or what it means.

I ran first aid and got this. Do I need to take my computer to get repaired or can I repair myself in Disk Utility or something else?

Looking forward for my questions to be answered.

Thank you.



Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking snapshot 1 of 1 (com.apple.TimeMachine.2024-01-16-155342.local)

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

warning: snapshot fsroot / file key rolling / doc-id tree corruptions are not repaired; they'll go away once the snapshot is deleted

Checking the document ID tree.

Checking the fsroot tree.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Checking the extent ref tree.

Verifying volume object map space.

The volume /dev/rdisk1s1 was found to be corrupt and needs to be repaired.

Verifying allocated space.

Performing deferred repairs.

The volume /dev/rdisk1s1 appears to be OK.

File system check exit code is 0.

Restoring the original state found as mounted.

MacBook Pro 13″, macOS 13.5

Posted on Sep 25, 2024 12:26 AM

Reply
Question marked as Top-ranking reply

Posted on Sep 25, 2024 9:17 AM

your Mac is not damaged in a way that the service department can help you.


the Directory of any drive is like collection of scoreboards that keeps track of File Attributes and extents (where the data blocks are placed on the drive). Each is generally organized as a set of trees (like linked lists) of things.


Disk Utiity ONLY examines and attempts to repair DIRECTORIES -- it does not read any Files at all.


The report says you have a snapshot that is damaged, and continues to say it will not be repaired (if time machine needs it better it will reconstruct it later.) That is all very unexciting.


Then it begins to examine fsroot -- the File System Root. This is VERY important, and MUST be correct.

it finds many problems, but claims it has tried to repair them. The overall repair passed.


if you are still queasy, run Disk Utility again, and see if the number of errors has gone down.


¿What exactly is stored on rdisk?

Similar questions

4 replies
Question marked as Top-ranking reply

Sep 25, 2024 9:17 AM in response to nlouis4

your Mac is not damaged in a way that the service department can help you.


the Directory of any drive is like collection of scoreboards that keeps track of File Attributes and extents (where the data blocks are placed on the drive). Each is generally organized as a set of trees (like linked lists) of things.


Disk Utiity ONLY examines and attempts to repair DIRECTORIES -- it does not read any Files at all.


The report says you have a snapshot that is damaged, and continues to say it will not be repaired (if time machine needs it better it will reconstruct it later.) That is all very unexciting.


Then it begins to examine fsroot -- the File System Root. This is VERY important, and MUST be correct.

it finds many problems, but claims it has tried to repair them. The overall repair passed.


if you are still queasy, run Disk Utility again, and see if the number of errors has gone down.


¿What exactly is stored on rdisk?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Volume /dev/rdisk1s1 found to be corrupt and needs to be repaired

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.