MacOS partition isn't working properly

Disk Utility Error Invalid fsroot and apfs_num_other_fsobejcts Running Disk Utility FIrst Aid on the Macintosh Hd Volume has following error :- warning: apfs_num_other_fsobjects (60) is not valid (62) The whole Detail as appeared in mac is as follows:- Running First Aid on “Macintosh HD” (disk1s1) NOTE: First Aid will temporarily lock the startup volume. 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. The volume Macintosh HD was formatted by hfs_convert (748.31.8) and last modified by apfs_kext (945.275.7). Checking the object map. Checking the snapshot metadata tree. Checking the snapshot metadata. Checking the extent ref tree. Checking the fsroot tree. warning: apfs_num_other_fsobjects (60) is not valid (62) Verifying allocated space. The volume /dev/rdisk1s1 appears to be OK. File system check exit code is 0. Restoring the original state found as mounted. Operation successful. i had searched internet but i can’t find any solution to this error. Also i had done 1 step before coming to this as i was getting error :fsroot tree is invalid Following is the message which appeared on running first aid:- NOTE: First Aid will temporarily lock the startup volume. 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. The volume Macintosh HD was formatted by hfs_convert (748.31.8) and last modified by apfs_kext (945.275.7). Checking the object map. Checking the snapshot metadata tree. Checking the snapshot metadata. Checking the extent ref tree. Checking the fsroot tree. error: btn: invalid btn_btree.bt_key_count (expected 2000421, actual 2000470) fsroot tree is invalid. 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. So in order to solve i had first of all Boooted in Recovery Mode and then Run first aid on Mac HD Volume. After that the error was removed. And when i came back to normal boot and run first aid i got the error (as mentioned above) : apfs_num . So i went on to try my best be searching on web but i could not find anything else. And then i tried 2nd thing from Single User mode. (CMD S on boot) . Start up Mac in single-user mode by restarting then press and hold Command + S. Type /sbin/fsck -fy into the command line and press Enter. This will initiate a file system check. You will see the same error, however in this case the repair will continue and fix the issue. Type reboot and press Enter. Login as normal and run First Aid on Disk and the error should be gone. Still this did not solve the APFS error. :- warning: apfs_num_other_fsobjects (60) is not valid (62) . All. the methods i used , i found on apple disscussion . FOllowing is the link to the Thread:- 1)https://discussions.apple.com/thread/8564919 2)https://discussions.apple.com/thread/8564919?answerId=34084121022#34084121022 3).https://discussions.apple.com/thread/8564919?answerId=250148557022#250148557022 Also that i have tried Stellar Recovery software and i found that because of these errors, recovering files from macbook is not possible. I am Using Mojave 10.14.6 as of now. The Stellar website suggests to go for complete reformatting Macintosh HD which by the way means to reformat my mac. Here is the link to Stellar's Post:- https://www.stellarinfo.com/blog/fix-apfs-fsroot-tree-is-invalid-error-on-macos-mojave/#:~:text=What%20exactly%20is%20the%20%E2%80%9Cfsroot,user%2Dcreated%20directories%20as%20subdirectories. Please find a solution as because of this i can not recovery my files through any recovery software as APFS is problematic. Also that i don’t think reformating is an option i can go for as i being. a music producer i have got VSTs (music softwares )on my mac and this would mean long hours of backup and then reinstallation on formatted mac. It is highly unproductive to reformat . Please find a a proper solution for APFS Drives.

2777 4

Need hlep with a corrupt macOS partition To cut a long story short, I decided to dual boot macOS Monterey with Ubuntu 22.04 as I needed it for some tasks that were easier on Linux. I found Bluetooth support to be janky and had to use a wired USB keyboard and mouse to get my tasks done. So I decided I did not want to keep Ubuntu on my system long-term. The simplest solution I read online was to delete the Ubuntu partition from within macOS and remerge the volumes to recover the space. While this worked for swap, this did not work for the Ubuntu partition and I ended up with a FFFFFF on my macOS volume. Attaching the diskutil info below: diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI ⁨EFI⁩ 209.7 MB disk0s1 2: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF ⁨⁩ 459.9 GB disk0s2 (free space) 8.1 GB - 3: Apple_HFS ⁨UNTITLED⁩ 31.6 GB disk0s4 (free space) 268.4 MB - /dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +459.9 GB disk1 Physical Store disk0s2 1: APFS Volume ⁨Macintosh HD - Data⁩ 205.8 GB disk1s1 2: APFS Volume ⁨Preboot⁩ 231.3 MB disk1s2 3: APFS Volume ⁨Recovery⁩ 1.1 GB disk1s3 4: APFS Volume ⁨VM⁩ 1.1 GB disk1s4 5: APFS Volume ⁨Macintosh HD⁩ 15.4 GB disk1s5 6: APFS Snapshot ⁨com.apple.os.update-...⁩ 15.4 GB disk1s5s1 I have read some articles on apple.stackexchange to fix this but am running into more errors when I try them. Doing this https://apple.stackexchange.com/questions/451126/linux-messed-up-guid-partition-table-for-apfs-container-on-external-drive with an ubuntu live usb leads to the following error: Found invalid GPT and valid MBR; converting MBR to GPT format in memory Warning! Main partition table overlaps the first partition by 32 blocks! You will need to delete this partition or resize in another utility. Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize in another utility. Could not change partition 2’s type code to 7C3457EF-0000-11AA-AA11-00306543ECAC! Error encounter, not saving changes. Can someone kindly give me stamp by step guide to correct this error and restore my mac to its original state with just a single partition having only macOS? My data is backed up to iCloud so if absolutely needed I can reinstall macOS from scratch. However, I would prefer to use recovery tools to solve the problem if possible.

266 7

Battle of the Disk Utilities (Multi-Boot APFS Internal SSD) Hello all, I recently upgraded an internal Fusion drive to a 2TB SSD in a 2017 iMac. The fusion drive contained three volumes/partitions: HFS+ (High Sierra/32-bit app support), Catalina (APFS) and Ventura (APFS sub-container). I used Carbon Copy Cloner for High Sierra and Catalina but decided to skip the Ventura APFS container because I intend to upgrade Catalina and no longer want a third macOS. First thing I notice after booting my upgraded iMac up, is that a 28GB partition showed up on the SSD. It appeared as a third choice when holding down "option" at startup, but upon selecting it the boot did not complete. Then, upon running Disk Utility, it didn't even *see* this partition. After a lot of hunting around to figure out how to "reveal" the partition using Terminal, I can now erase or re-partition the 28GB in Disk Utility — but am unable to delete it. I tried a force-removal in Terminal, multiple boots into Safe Mode, running Disk Utility in Recovery, reinstalling macOS on the bootable partitions — and still I can't get rid of this 28GB partition and return the free space to the remaining volumes. As part of the troubleshooting, I noted that despite booting successfully with no apparent issue into High Sierra and Catalina, Disk Utility throws all kinds of errors. It ranges from the apparently common issue of drives refusing to dismount so that First Aid can execute repairs to reporting that one of the volumes (Disk3s1) is corrupt. In booting from an external USB key containing various macOS installers, and launching Disk Utility from there, I was able to delete faulty Time Machine snapshots, and that got rid of the scariest message about my High Sierra volume being corrupt. (I was on the verge of wiping the drive because that sort of message from Disk Utility tends to mean there is no fix. Fortunately, there was.) Unfortunately, there's more: When I "view all" in Disk Utility (Ventura edition) to test the parent SSD while booted from a thumb drive, it reports errors on the parent volume but when I run other versions of Disk Utility, it does not. Conversely, when I run Ventura's version of Disk Utility on the individual APFS containers, there are no warnings/errors but when I use earlier versions of Disk Utility there are so many warnings on Disk3 (High Sierra container) that Disk Utility reports that it has suppressed the duplicating error entries. Depending on the version of Disk Utility, I get results that are all over the map, ranging from nothing found to orphaned files, warnings about invalid files (inode_val: object…), dstream, unable to verify the drive completely, references to suppressed warnings, etc. — only for Disk Utility to report that my volumes are "OK". I then decided to boot into Single User Mode, only to find that fsck_apfs -y can't be run in Single User Mode (unable to dismount the volume). However, I did find in Single User Mode a repeating entry called "sanity check" that reports an "fs_alloc_count mismatch" at the root nodes. (Caveat being, I can't be sure if that's a valid error, either, because it's not running off a fully dismounted SSD.) My last ditch effort was to search for an alternative to Disk Utility. I ended up buying an app called DriveDX. It reports that the drive health is good, with no errors of any kind. (Back in the day, I would have turned to the likes of TechTool Pro or DiskWarrior but apparently Apple never released the full APFS documentation so competitors to Disk Utility are unable to rebuild APFS volumes. Consequently, I am unaware of any third-party software that overcomes these limitations.) The original Fusion drive was itself new and had no Disk Utility errors before cloning. (I say "new" because this 2017 iMac was purchased off of an auction site still new in a sealed Apple box less than two months ago, probably one of the last 2017s on the planet with no mileage on it. My only reason for upgrading was to get a larger internal drive. Ugh.) In the end, I suspect this ties into the fact that I failed to exactly duplicate the original fusion drive. Although I can't be sure why I ended up with a persistent 28GB partition that I can't delete, I suspect the presence of allocation mismatches reported in Single User mode may explain some (if not all) of this. Q: Since the latest version of Disk Utility available to me (Ventura) doesn't find a problem with the bootable containers, should I worry about the fact that other versions of Disk Utility report numerous "warnings"?

243 10

MacOS partition isn't working properly

Similar questions