I checked my Disk Utility and it shows "Macintosh SSD - Data (APFS Volume APFS" and there's 3 of these. Sometime ago I had it repaired through an Apple Service Center because the logic board was damaged. Now, I got a new board, I tried to reformat the drive but the only option is APFS format and nothing else. Any thoughts?

If someone modifies a Big Sur or Monterrey boot disk and attaches it to my standard Big Sur or Monterrey machine booted from the internal will reads of the modified files succeed?

Recently I tried to use mac asr command to backup my mac. However, I got different error on different mac devices. While I tried to asr backup my "Intel Mac 10.15.7", following is the command i used: asr restore --source {system role volume} --target {another container's volume} --toSnapshot "{snapshot I take on both system role and data role}" --erase. After running asr, it shows "Volume replication failed - error 49157" while backing up data volume. I tried another asr backup on my "M1 Mac 12", following is the command i used: asr restore --source {system role volume} --target {another container's volume} --toSnapshot "com.apple... (the snapshot that system snapshot mount)" --erase. After running asr, it shows "Couldn't embed the APFS EFI driver - error 49174" at the end of asr. (while it's 100% done) Does anyone know any detail info / document / solution about the asr error code? Currently I cannot find anything about 49157 / 49197 error code.

Hi, I have searched github but I haven't been able to find a developer disk images to mount on my iPhone6,2 with ideviceimagemounter running iOS 12.5.5 (16H62) the closest developer disk images are 12.4 and 13.0. 12.5.5 which has not being provided is the image I would like help obtaining for my iPhone which is unable to update past the version and as Windows is my only operating system and I don't have access to a mac or xcode. Please explain how to compile the image or provide a download link. I read on HERE that renaming the folder to the required ios image version number would solve the issue 'Error: ImageMountFailed' but I assume that the folder to rename is within a macOS app directory with which I dont have access to any MacOS computers. How can I get a 12.5.5 image with only Windows, I tried installing xCode to a MacOS vmware guest machine which didn't allow installation due to needing a higher version, How can I just get 12.5.5 developer disk image please.

Hello dear kindly I need your support about this problem since I update my iOS 15.3.1 every time I have a call and get waiting I can’t close this sound beep beep beep beep beep only solution to end this sound press on lock bottom so both of call will end or I can reject and answer second call or I can reject only or I can answer and hold So please I need solution for this problem

I have an external SSD I've used for a while with no issue. I've recently been using it on my iPad on the go, also with no issue. When I wanted to use it on a Mac today (after using it on my iPad for a while), the disk wouldn't mount anymore. Still does on the iPad for some reason. Tested on MacOS 12.2 & 12.2.1 Any ideas as to how this can happen ? Here's what Disk Utility's First Aid tells me: Running First Aid on “ExtSSD” (disk8s1) Checking file system and repairing if necessary and if possible. Volume is already unmounted. Performing fsck_apfs -y -x /dev/rdisk8s1 Checking the container superblock. error: (oid 0x14e776) om: invalid o_oid (0x71ff) error: (oid 0x14e776) om: invalid o_type (0x3, expected 0x4000000b) error: (oid 0x14e776) om: invalid o_type (0x3, expected 0x4000000b) error: verification/reading of the omap object failed: Illegal byte sequence warning: checkpoint 192 (xid 26927) failed consistency check Checking the space manager. error: spaceman cib out of order: 0, expected 2 Space manager is invalid. The volume /dev/rdisk8s1 could not be verified completely. File system check exit code is 8. Restoring the original state found as unmounted. File system verify or repair failed. : (-69845) Operation failed… Or directly Via CLI: ❯ sudo fsck_apfs /dev/rdisk8s1 ** Checking the container superblock. error: (oid 0x14e776) om: invalid o_oid (0x71ff) error: (oid 0x14e776) om: invalid o_type (0x3, expected 0x4000000b) error: (oid 0x14e776) om: invalid o_type (0x3, expected 0x4000000b) error: verification/reading of the omap object failed: Illegal byte sequence warning: checkpoint 192 (xid 26927) failed consistency check Checking the checkpoint with transaction ID 26926. ** Checking the space manager. error: spaceman cib out of order: 0, expected 2 Space manager is invalid. ** The volume /dev/rdisk8s1 could not be verified completely.

I am an end user, not a developer. I have a 2019 MacBook Pro 16" 1 TB SSD running Monterey 12.3 Beta. I got it from a reseller and it's my first Mac so I don't know much about anything. Just trying to learn about Macs after 40 years with Windows. Time Machine is set up with an external 4 TB Seagate drive. Set up for encryption and automatic backups. It has completed a few back ups for about 288 GB but says a full back up would be 980 GB. Periodically I get an error message that says a back up can't be completed because a snapshot of the disk couldn't be created. Or it will say there's not enough space on the Time Machine drive, which makes no sense since it's so much larger. l've reformatted the Ext HD and started over but it's still not working right. Ideas?

Hey guys, i have recently tried to restore my 15" 2015 macbook pro after i upgraded to Monterey. Turns out half my apps dont work on it so i thought id just restore it from time machine. I booted the macbook up in recoverey mode and started the recoverey process however it has not moved from "preparing to restore" for the last 24hours. I checked the log and the last entry is: Macbook-pro OSInstaller[488] : [RESTORE] Erasing disk 'Mac' to filesystem type 'KSKDiskFileSystemAFPS', Case sensitive: No I am currently using a seagate one touch 5TB to restore from and i was just wondering is it usual to have to wait so long or has it frozen? And what am i doing wrong?

Hello everyone, here I open a post about a serious bug of the APFS Encrypted filesystem which apparently is affecting many users. Suddenly, my external drive (WD 5TB portable) stopped mounting correctly. It asks me for the password, I enter it correctly, it tells me that it is incorrect (while it is), I re-enter it and after a couple of seconds the screen disappears but the disk is not mounted on the desktop. I use Monterey 12.1 on a 16 ”i9 MBP. With disk utility I see the partition (occupied for 1.46 TB) but I cannot use it, since it gives me (com.apple.DiskManagement.disenter error 49218). Has anyone solved the problem? Is there any tool that allows me to mount the disk to copy the data? Is it possible that there is such a big bug and Apple does nothing? Thanks everyone for the answers.

Hi Team, Looking for a solution, to identify If MAC have Multiple Apple OS's installed or not. Tried searching with StartupDisk, BootableManager etc, No luck #OSX #APPLEDEVELOPPERFORUM

How do I programmatically mount an APFS encrypted device? If it is a normal device, Can be mounted using DADiskMount of Disk Arbitration Framework. However, in the case of APFS encryption, it will not be mounted even if DADiskMount is used in the same way. I think it requires a password to mount. Please tell me if there is a way to programmatically mount the APFS encrypted device. The language I'm currently using is Objective-C.

Fatal Exception: NSGenericException *** Collection <__NSArrayM: 0x28313ce10> was mutated while being enumerated. -[CAMPriorityNotificationCenter _removeObserver:fromObserversByName:] keyboard_arrow_down Fatal Exception: NSGenericException 0 CoreFoundation 0x1878e8298 __exceptionPreprocess 1 libobjc.A.dylib 0x19b642480 objc_exception_throw 2 CoreFoundation 0x1878e7c5c -[__NSSingleObjectEnumerator initWithObject:collection:] 3 CameraUI 0x1affb7e7c -[CAMPriorityNotificationCenter _removeObserver:fromObserversByName:] 4 CameraUI 0x1affb81a8 -[CAMPriorityNotificationCenter removeObserver:] 5 CameraUI 0x1b0066510 -[CAMCaptureEngine dealloc] 6 libsystem_blocks.dylib 0x1cfcbc784 _Block_release 7 libdispatch.dylib 0x18750a290 _dispatch_source_handler_dispose 8 libdispatch.dylib 0x18750935c _dispatch_source_invoke$VARIANT$armv81 9 libdispatch.dylib 0x1874fc210 _dispatch_lane_serial_drain$VARIANT$armv81 10 libdispatch.dylib 0x1874fce2c _dispatch_lane_invoke$VARIANT$armv81 11 libdispatch.dylib 0x18750666c _dispatch_workloop_worker_thread 12 libsystem_pthread.dylib 0x1cfd355bc _pthread_wqthread 13 libsystem_pthread.dylib 0x1cfd3886c start_wqthread Crashed: com.google.firebase.crashlytics.ios.exception SIGABRT ABORT 0x00000001b36927b0 FIRCLSProcessRecordAllThreads keyboard_arrow_down

I have a miniMac M1 for M1 testing and development. I had set it up for dual boot with the original Big Sur partition that came with the machine and a new partition for Monterey. I've been using this for some months. Summary: After the steps taken below, and the subsequent steps to attempt to fix the problem, it became impossible to boot into the Big Sur partition. It seems that the System volume and the Data Volume had become disassociated making the partition unbootable. I do see there might have been user error here; I had not gone into the Recovery mode on Monterey and enabled the possibility to boot from an external drive. Now, strictly speaking, both the Big Sur and Monterey partitions were internal since they were on the main hard drive. But could it have been that Monterey would not allow me to boot into Big Sur because I had not enabled the external boot possibility? Detail: I had always had the beta of Monterey installed, but because I needed to test a crash agains the release version of Monterey, I did the following: Set the startup disk to Monterey (something I'd never done before; I usually shutdown and hold the power button to select the boot drive.) I disabled the beta program in the System Preferences. System Update then showed the 12.0.1. I install that version and performed my tests. I then went to the System preferences to set Big Sur as the startup disk. I was surprised to see it wasn't listed (as it always had shown up there before). I ran Disk Utility / First Aid on the Big Sur partition, and then on the entire disk that holds both Big Sur and Monterey. They reported no problems. Then I then went into Recovery mode, and when I selected the Big Sur disk, it said "no users available for recovery". In other words, it couldn't see the data partition with the users on it. This seeming separation of System and Data partitions was confirmed whe I returned to the Finder after a reboot. I double-clicked the Big Sur partition, it only showed the System folder. It did not show "Users" or "Applications" or "Library" I went back to Disk Utility. It in fact showed the Big Sur data partition. When I chose File > Show In Finder the data partition showed up, with the "Users" or "Applications" or "Library" intact. So the Data volume was still there, but somehow the link between it and the System Volume seems to have been broken. Finally, I went to the Terminal, entered "cd /Volumes" and "ls -al". It showed the Monterey partition as a single directory. But the Apple M1 drive and it's Data partition were listed separately I sadly don't have a copy and paste, but something like this: drwxr-xr-x   5 root  wheel  160 Nov 18 07:58 . drwxr-xr-x  20 root  wheel  640 Jan  1  2020 .. lrwxr-xr-x   1 root  wheel    1 Nov 18 07:00 Monterey-> / drwxr-xr-x  21 root  wheel  672 Nov 18 00:10 BigSur drwxr-xr-x@ 19 root  wheel  608 Nov 18 00:08 Data Any ideas what could have happened and how I can prevent it in the future? Sincerely, Mark

During update to Monterey beta to an external ssd, startup stopped with barred circle and unusable ssd! I have a recent time machine backup, still I don't know how to repair the respective container. In diskutil the volume is shown as "AppleAPFSMedia not initialized" and can not be repaired! 'diskutil apfs list' shows an error (Container ERROR -69808).  See partial listing: APFS Containers (3 found) | . . . | +-- Container ERROR -69808 ====================== APFS Container Reference: disk8 Size (Capacity Ceiling): ERROR -69620 Capacity In Use By Volumes: ERROR -69620 Capacity Not Allocated: ERROR -69620 | +-< Physical Store disk3s2 1C0E6E67-8751-4376-8C2E-9DAA6460C864 | ----------------------------------------------------------- | APFS Physical Store Disk: disk3s2 | Size: 599995129856 B (600.0 GB) | +-> No Volumes

Every time a try partitioning my hard drive I receive the following error message: "APFS Container Resize error code is 49212 A problem occurred while resizing APFS Container structures. : (-69606)" What am I doing wrong? I have about 500 GB free on my hard drive so I know that isn't the problem. I have also disabled Time Machine snapshots. Machine specs: iMac (27-inch, Late 2013) running macOS Catalina Version 10.15.7 3.2 GHz Quad-Core Intel Core i5 24 GB 1600 MHz DDR3 Macintosh HD NVIDIA GeForce GT 755M 1 GB

I've used AppleScript occasionally over the years, but am a novice. I have many files from a now defunct drawing package (fooDraw, file extension FOO). I'd like to convert them all to Adobe Illustrator files. One way to do this would be to crawl through my Documents folder, to find any .FOO files. This should be doable, but I'm not sure how to. When the script finds one, can it get the file name and path? If so, it could tell application fooDraw to open that file, select all, and copy. Then it could tell application Illustrator to open a new file, and paste. But then, I need to tell Illustrator to save the file in the same directory, with the same file name. Any help, or ideas where I might search? TIA

On my MacPro Big Sur I do not have access to the internal hard drive, when attempting to add my name as a user I receive. "'This operation can't be completed because you don't have the necessary permission. I attempted running csrutil disable but this did not solve the issue. Also went into disk utility and ran a verification on the hard drive. Looks like I never used my hard drive since I had my MacPro I have been using iCloud. Volume name : Macintosh HD Volume type : APFS System Volume BSD device node : disk1s5 File system : APFS (Encrypted) Connection : PCI-Express Device tree path : IODeviceTree:/PCI0@0/RP01@1C/SSD0@0/AppleS3XController Writable : No Is case-sensitive : No File system UUID : FF5BA9F1-D8CE-4418-BCD2-2E0762F5E47B Volume capacity : 121,018,208,256 Owners enabled : No Is encrypted : Yes Can be verified : Yes Can be repaired : Yes Bootable : No Journaled : No Disk number : 1 Partition number : 5 Media name : Media type : Generic Ejectable : No Solid state : Yes S.M.A.R.T. status : Not Supported Parent disks : disk1

Wile researching api/frameworks for the backup solution for iOS, I slowly came to realize that there is no effective method for the corporate to monitor/audit file-system on their iOS fleet. Ie - api is there, but limited and the user can always kill your app. Not to mention that you're quite limited in terms of background processing/monitoring Am I missing something?