Volume /dev/rdisk3s1 is corrupt and needs repair

M0ndayTuesday wrote:

Thank you for your suggestion. All Options tried. I am looking specifically for a fix of the corrupt Volume /dev/rdisk3s1. Reinstalling Ventura, Disk utility First aid, total erase and reinstall fro TimeMachine do not fix the problem.

Erase and gradual reset up from Time Machine might work but a) takes along time and b) is complex in finding all Library stuff to re-establish things like email on Mac.

The Internet Recovery sounded like a good possibility but I cannot get it to start in that mode.

Sorry the Apple Silicon Computer Recovery Method did not work ?

Or, was the repair of the corrupt Volume /dev/rdisk3s1 while in Recovery Mode did not work ?

FYI - Time Machine Backup does not contain a Full and Working Copy of the Operating System so I am not sure what is meant by " reinstall fro TimeMachine " ?

Use macOS Recovery on a Mac with Apple silicon - Apple Support (CA)

It is a different method than on Intel Computers

Excerpt from above link

Start up your computer in macOS Recovery

1. On your Mac, choose Apple menu  > Shut Down.
2. Wait for your Mac to shut down completely. A Mac is completely shut down when the screen is black and any lights (including in the Touch Bar) are off.
3. Press and hold the power button on your Mac until the system volume and the Options button appear.
4. Click the Options button, then click Continue. 
5. If asked, select a volume to recover, then click Next.
6. Select an administrator account, then click Next.
7. Enter the password for the administrator account, then click Continue.
8. When the Recovery app appears in the menu bar, you can choose any of the available options in the window or the menu bar.

M0ndayTuesday wrote:

I am having a set of problems with my M1 Mac (4 port 2021). Running disk first aid in Recovery mode tells me that the Volume /dev/rdisk3s1 is corrupt and needs repair. It also tells me that it would be worth trying to run fsck against the entire APFS container.

I have erased and restored from TimeMachine but that has the error in its saved data so no cure.

My questions are

a) what does this mean?

b) how do I run fsck against the entire container?

c) what else to cure this issue.

Latest Ventura installed, TimeMachine back-ups ready.

Boot into Internet Recovery (Option Command R) and from the dropdown menu: Utilities>  Disk Utility> run the First Aid on your Macintosh HD (and the "Macintosh HD-Data" volume as well if Catalina/Big Sur/Monterey/Ventura) If errors are found and repaired, run again until no errors reported.

Disk Utility>View>Show All Devices The best sequence is —

Volume level

Container level

Parent drive

How to repair a Mac disk with Disk Utility

How to repair a Mac disk with Disk Utility - Apple Support

internet recovery— to get to Disk Utility

How to reinstall macOS - Apple Support

Matt W (TechnicalMac) wrote:

This is the antithesis of regular maintenance,

Worst still, if they employ Third Party Maintenance programs

ie > > Disk Cleaner 

This will include CleanMyMac , aka “ BrickMyMac “

MacKeeper,

Dr Cleaner Pro Plus

Open Cleaner one Pro

Macmechanic

Clean my Mac x.

M0ndayTuesday wrote:

I am having a set of problems with my M1 Mac (4 port 2021).

What problems are you having? Please be specific.

Running disk first aid in Recovery mode tells me that the Volume /dev/rdisk3s1 is corrupt and needs repair. It also tells me that it would be worth trying to run fsck against the entire APFS container.

Are these the problems you are talking about? That's not my question.

What was the reason for running disk first aid to begin with?

My questions are

a) what does this mean?

Nothing. It's a bug.

b) how do I run fsck against the entire container?

Don't.

c) what else to cure this issue.

Again, what's the problem?

I'm not sure what you have done at this point, or what changes you have made. The internet is absolutely full of very bad ideas. If you have tried something you found on the internet, don't do that. At this point, my recommendation would be to get back to a clean slate. Don't even bother trying to erase the hard drive. Modern hard drives and file systems are so complicated that there is no guarantee that will succeed. Instead, follow instructions here to reset your computer completely: Erase your Mac and reset it to factory settings - Apple Support

Then, don't go looking for problems. If you notice something you don't like and think it should behave differently, post a new question. Describe what is happening. Describe how you think it should work. Do not attempt to install any 3rd party hacks, "clean up", etc. Don't try any command line "fixes" from the internet. Just ask.

"Then don't go looking for problems..."

This is the antithesis of regular maintenance, y'know, trying to head off problems before they cost a lot of money trying to fix after a failure when someone forgot to plug in a backup drive for 3 weeks. With Apple's less-than-stellar support of APFS, bugs that go unfixed through 4+ versions of macOS, and near-constant under-the-hood changes—purportedly to assure us that everything is "secure"—there is no way to be confident that anything is as it seems.

When I see this in Disk First Aid, and nothing appears to be "wrong," sure, I chalk it up to another Apple unfixed bug, and when DFA can't fix the problems it reports, I just have to sigh and move on, right? I do see this enough that I have begun to hope that it's just a dumb programming error and assume that it won't get fixed for the next two years, but that, at best, leads me off into red-herring territory, wasting a lot of time when something does go wrong. At worst, it drops my confidence in using a Mac. We don't have third-party tools to give us a second opinion, and I don't like rebuilding a system that's crying wolf every other week.

Linux, anyone?

Matt W (TechnicalMac) wrote:

"Then don't go looking for problems..."

This is the antithesis of regular maintenance,

I’ve used Macs since the original 128k and have never done “regular maintenance” on any of them.

If you want to fidget with your computer doing “maintenance” you probably should just run Linux.

Matt W (TechnicalMac) wrote:

"Then don't go looking for problems..."

This is the antithesis of regular maintenance

Mac's don't need regular maintenance. They take of themselves. The vast majority of problems come from users attempting to perform some kind of maintenance on them.

Good work there and hope the issue does not return