MacOS.....

[Radical1233]

Why does macOS suck?

 

When I run Disk Utility, this comes up. My MacBook Air 2015 has been crashing so many times randomly. Like even when I just have a browser open, it crashes.

Running First Aid on “Macintosh HD - Data” (disk1s1)

Verifying the startup volume will cause this computer to stop responding.

Verifying file system.
Volume could not be unmounted.
Using live mode.
Performing fsck_apfs -n -l -x /dev/rdisk1s1
Checking the container superblock.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking volume.
Checking the APFS volume superblock.
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 1 (com.apple.TimeMachine.2021-07-08-095315.local)
error: directory valence check: directory (oid 0x60053): nchildren (1) does not match drec count (0) 
warning: snapshot fsroot/file key rolling tree corruptions are not repaired; they'll go away once the snapshot is deleted
Checking the extent ref tree.
Checking the fsroot tree.
error: directory valence check: directory (oid 0x60053): nchildren (1) does not match drec count (0) 
Verifying allocated space.
Performing deferred repairs.
error: Unable to perform deferred repairs without full space verification
error: Try running fsck against the entire APFS container instead of a volume
The volume /dev/rdisk1s1 could not be verified completely.
File system check exit code is 0.
Restoring the original state found as mounted.

Operation successful.

 

[Bombastinator]

1 hour ago, Radical1233 said:

Why does macOS suck?

 

When I run Disk Utility, this comes up. My MacBook Air 2015 has been crashing so many times randomly. Like even when I just have a browser open, it crashes.

Running First Aid on “Macintosh HD - Data” (disk1s1)

Verifying the startup volume will cause this computer to stop responding.

Verifying file system.
Volume could not be unmounted.
Using live mode.
Performing fsck_apfs -n -l -x /dev/rdisk1s1
Checking the container superblock.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking volume.
Checking the APFS volume superblock.
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 1 (com.apple.TimeMachine.2021-07-08-095315.local)
error: directory valence check: directory (oid 0x60053): nchildren (1) does not match drec count (0) 
warning: snapshot fsroot/file key rolling tree corruptions are not repaired; they'll go away once the snapshot is deleted
Checking the extent ref tree.
Checking the fsroot tree.
error: directory valence check: directory (oid 0x60053): nchildren (1) does not match drec count (0) 
Verifying allocated space.
Performing deferred repairs.
error: Unable to perform deferred repairs without full space verification
error: Try running fsck against the entire APFS container instead of a volume
The volume /dev/rdisk1s1 could not be verified completely.
File system check exit code is 0.
Restoring the original state found as mounted.

Operation successful.

 

Intel macs will run other things too.  You could always try a Linux liveCD on it. I rather doubt it’s MacOS specifically that is the issue. Macs down deep actually run a heavily modified version of an older Unix called BSD, so their command line stuff is actually often better than microsoft stuff by a good margin.  If you’re used to windows stuff it likely won’t help much though. 
 

the Mac GUI is just a front end for command line stuff which is why it’s giving you a list of what it is doing while it is doing it.  Not as pretty as a moving bar or a cartoon dog or something (though iirc microsoft removed the dog because too many people complained) I suppose but a lot more informative. 
 

From what I read it seems to think there is a problem that goes beyond just that volume.

[maplepants]

2 hours ago, Radical1233 said:

Try running fsck against the entire APFS container instead of a volume

What happens when you do this?

 

If you haven't done it yet, try following this tutorial.

[Flannelist]

11 hours ago, maplepants said:

What happens when you do this?

 

If you haven't done it yet, try following this tutorial.

This. I would also use First Aid in Recovery mode/Internet recovery mode rather than while macOS is booted since i suspect that's what's been done. Imagine trying to repair a car while it's moving. That's what First Aid live mode essentially is. Trying to repair the file structure of a disk that's in use.