I was using a APFS external USB Disk on a PC using a commercial driver. Suddenly it stopped being accessible.. Now I can´t mount the Volume inside the APFS container anymore, on PC but also not on a Mac! If I try diskutils - please see the log:

123$ diskutil verifyvolume disk4s1
Started file system verification on disk4s1 DISK-XYZ
Verifying file system
Volume is already unmounted
Performing fsck_apfs -n -x /dev/rdisk4s1
Checking the container superblock
Checking the space manager
error: (oid 0x400) sm: invalid o_cksum (0x74dfcb428a5691c4)
error: verification/reading of the spaceman object failed: Illegal byte sequence
Space manager is invalid
The volume /dev/rdisk4s1 could not be verified completely
File system check exit code is 8
Restoring the original state found as unmounted
Error: -69845: File system verify or repair failed
Underlying error: 8

Any idea how to fix it? As there is important stuff on the drive I currently draw an image to be held safely while testing on the drive. Or should I try the other way round? How do you evaluate chances to fix it with fsck? Do you know of any other handy tools? Disk Warrior does not handle APFS unfortunately.. ah- btw - mounting read only does not work unfortunately.

123$ diskutil mount readOnly /dev/disk4s1
Volume on disk4s1 failed to mount; it appears to be an APFS Volume which might be locked
Try "diskutil apfs unlockVolume"

Thanks and best, DHVD

I have an external SSD drive which has 4 bootable partitions holding monthly backups. It has a GUID partition map; each partition is MacOS Extended Journaled (HFS+); each is 250GB in size with about 120GB in use. The partitions are not encrypted; I do not think it uses Core Storage.

/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS SSDmon1                 250.0 GB   disk2s2
   3:                  Apple_HFS SSDmon2                 249.9 GB   disk2s3
   4:                  Apple_HFS SSDmon3                 249.6 GB   disk2s4
   5:                  Apple_HFS ARCH_B3                 249.9 GB   disk2s5

I recently upgraded from Mojave 10.14.6 to Catalina 10.15.7 on this 2012 MacBook Pro. I used SuperDuper! to back up the new system to a different external drive, and it needed to convert the destination to APFS. So I guess bootable backups now need to be APFS. My questions: - Can I convert the entire external SSD to APFS? How? - Or do I need to convert each partition separately? (I know I can do that with Disk Utility or 'diskutil') - If the second, will they be put into the same container, or will there be four containers with one volume each? If four containers, can they be joined into one container? I'm afraid to do something wrong and mess up the drive, so I'd like to hear suggestions and warnings before I attempt anything. It would not be the end of the world to lose the backups, but I'd rather avoid that if I could.

I saw a related post but the instructions were specific to VMware Fusion, which I am not using. With Carbon Copy Cloner, I created a bootable backup of the existing macOS Mojave installation that I want to turn into a VM. Do I need to include The Container when I convert that clone into an iso or cdr? Yesterday, I made a macOS Mojave VM directly from the macOS Mojave Installer using the instructions and tools here: AlexanderWillner/runMacOSinVirtualBox The post about doing this with VMware suggests adding the iso/cdr clone of the boot drive you want to virtualize to an existing Mojave VM. Would this work in VirtualBox, given that VirtualBox still doesn't technically support booting from APFS drives? I'm not particularly familiar with VirtualBox and I don't want to purchase VMware or Parallels. What will be the simplest way to convert my existing macOS Mojave APFS installation into a VirtualBox VM?

I found four similar questions, but they weren't exact duplicates.  I did get an impression from them that it isn't possible, but since my situation is slightly different, I thought it worthwhile to ask.
Blank is just that: no files except the unnecessary .fseventsd and Spotlight file.  But Christopher is a time machine backup that is almost full (4.78TB).  I would like to make this a single APFS container without losing any backup sets.  I have nothing else big enough to copy its contents (nor would I enjoy the hours it would take at USB 2.0 speeds).

I recently ran Boot Camp Assistant to remove the Windows partition from my 2017 MacBook Pro, but during the partitioning step I quit Boot Camp Assistant. After restarting the computer the next time, I got a flashing drive icon and macOS was no longer booting. My only option at this point was Internet recovery. I tried running Disk Utility, unfortunately First Aid seems to be unable to fix the problem: Looks like the APFS Container got corrupted. **diskutil apfs list**

Containers (2 found)
|
+-- Container ERROR -69808
|   ======================
|   APFS Container Reference:     disk1
|   Size (Capacity Ceiling):      ERROR -69620
|   Capacity In Use By Volumes:   ERROR -69620
|   Capacity Not Allocated:       ERROR -69620
|   |
|   +- No Volumes

Next, I tried diskutil repairVolume on the APFS Volume, but again, no luck:

diskutil repairVolume disk0s2
Started file system repair on disk0s2
Repairing storage system
Performing fsck_apfs -y -x /dev/disk0s2
warning: nx_block_count is 122061322, while device block count is 110107642
error: object (oid 0x1): o_cksum (0x50eca9de0b97f54e) is invalid for object
Checking the container superblock
Storage system check exit code is 8
Error: -69716: Storage system verify or repair failed
Underlying error: 8

**GPT partitions:**

-r show /dev/disk0  
Password:
      start       size  index  contents
          0          1         PMBR
          1          1         Pri GPT header
          2          4         Pri GPT table
          6      76800      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      76806  110107642      2  GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC
  110184448   11953680         
  122138128          4         Sec GPT table
  122138132          1         Sec GPT header

Also, recovery tools like iBoysoft do see the APFS volumes and all the files after I provide the encryption password, so the volumes seems to be OK: Is there any way I can re-build the partitions/APFS container so the disk will boot again? Any help would be much appreciated. Thanks! Note: currently I am running a fresh install of Catalina on an external HDD.

I have a MacBook Air 2017. Out of the blue, I opened the MacBook and was confronted with the question mark. The Mac would only boot in recovery mode. In internet recovery mode, I copied the internal disk (dd conv=noerror,sync) to an external hard drive. Whilst I did create a 250GB disk image, I'm not sure of the quality of it, as I received many ‘disk not configured’ messages in the process. With that disk image from the external drive in another MacBook Air 2017, I used hdiutil imageinfo which said there were seven partitions on the disk image. I then used test disk/ file system utils which showed two partitions an EFI partition and an APFS. I created an image of the APFS partition which was 250GB but when I run **photorec** on that (writing to a second external hard drive) it hasn’t recovered any files. Any advice on next best steps or things that I need to do/ haven’t done. Would be hugely appreciated. Edit: A previous attempt at running photo rec on the full disk image yielded a 250GB plist file. Edit2: I can now use target disk mode to see the disk on another MacBook. However it fails to mount. DDRescue currently running and making slow progress.

What is the best way to add quotas to filesystems in MacOS? I know it can be done to Volumes, however interested where quotas can be modified later (Volumes are only at creation). Specifically, to prevent a DOS on disk space consumption and best practice to cover this for users.

I would like to understand the Format Partition APFS on Linux Side. I made this question https://unix.stackexchange.com/questions/597308 I have a USB External SSD with 4 disk partitions. The file system of partitions are - APFS - ExFAT - ext4 - NTFS Now I would like to find the Label (The Volume is named 'APFS') on my APFS partition.... Using the command diskutil list Can you see the /dev/disk3. Checking the https://developer.apple.com/support/downloads/Apple-File-System-Reference.pdf Here another blogs 1. https://blog.cugu.eu/post/apfs/ 2. https://www.ntfs.com/apfs-structure.htm 3. https://digital-forensics.sans.org/media/FOR518-Reference-Sheet.pdf 4. https://link.springer.com/content/pdf/10.1007/978-3-030-98467-0_1.pdf *(last addition)* Here a resume that I made of the First structure or Format Header of APFS Partition. I would like the position of Label ('APFS' I named like File System) of my Volume. Checking my First 4096 first bytes on my disk **after NXSB** **nx_block_size** (4 bytes) is located at position 24(16) = 36(10) with value of 1000(16) = 4096(10) bytes. **nx_block_count** (8 bytes) is located at position 28(16) = 40(10), here 037E0E80(16) = 58592896(10). **nx_xp_desc_blocks** (4 bytes) is located at position 68(16) = 104(10) used with value of 0118(16) = 280(10) blocks (the checkpoint descriptor area consists of 280 blocks). **nx_xp_desc_len** (4 bytes) is located at position 8C(16) = 140(10) used with value of 02(16) = 2(10). (About the picture above)**Point 4:** What does it mean that nx_efi_jumpstart_t have 00 00 00 00 | 00 00 00 00, where is there supposed to be an address? (About the picture above)**Point 2:** nx_xp_desc_base How must be interpreted the bytes 45 81 00 00 | 00 00 00 00?, is it a relative memory position or absolute memory position or Jump? Little-endian: 45 81 00 00 00 00 00 00 Big-endian: 00 00 00 00 00 00 81 45 **Decimal**: 33093 (About the picture above)**Point 6:** nx_omap_oid How must be interpreted the bytes 46 7e 09 00 | 00 00 00 00?, is it a relative memory position or absolute memory position or Jump? Little-endian: 46 7E 09 00 00 00 00 00 Big-endian: 00 00 00 00 00 09 7E 46 **Decimal**: 622150 (About the picture above)**Point 7:** nx_fs_oid How must be interpreted the bytes 02 04 00 00 | 00 00 00 00?, Little-endian: 02 04 00 00 00 00 00 00 Big-endian: 00 00 00 00 00 00 04 02 **Decimal**: 1026 is it a relative memory position or absolute memory position or Jump? NXSB APSB Thanks a lot in advance!

MacBook Pro 2015, 256GB SSD disk I have created a second partition on my disk to try Linux. Everything was fine, but at some point, macOS disappeared from the boot menu. After some googling and trying some things, I thought it was a problem with the boot manager. I installed rEFInd but it didn't help. So I tried torecover everything using recovery mode. But there was no option to reinstall macOS on the first partition. I could only erase it. I also couldn't mount it to macOS Recovery. I installed OS X 10.10 Yosemite (base for my MacBook) on the second partition and updated it to macOS 10.14 Mojave (to be able to mount that first APFS partition). But I still can't mount it:

daniils-MacBook-Pro:Volumes daniilkk_yose$ sudo mount -t apfs /dev/disk0s2 plz/
mount_apfs: mount: Inappropriate file type or format

Also, diskutil outputs many F's instead of type and name:

daniils-MacBook-Pro:Volumes daniilkk_yose$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *251.0 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF               129.2 GB   disk0s2
   3:                 Apple_APFS Container disk1         121.6 GB   disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +121.6 GB   disk1
                                 Physical Store disk0s3
   1:                APFS Volume disk1s3                 12.8 GB    disk1s1
   2:                APFS Volume Preboot                 43.1 MB    disk1s2
   3:                APFS Volume Recovery                510.4 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4

Disk Utility doesn't show this partition at all: Is there a way to mount it and get my data back?

I want to manually create, delete, and restored to snapshots on my APFS volumes (external, for data use, so not limited by SIP). I'm using snaputil , but maintaining APFS snapshots require two entitlements: com.apple.developer.vfs.snapshot and com.apple.private.apfs.revert-to-snapshot. However, I neither have access to nor intend to enroll (buy) in Apple's developer program, which grants permission to use these entitlements. On my old Intel MacBook, I was able to sign it ad-hoc with these two entitlements and disable AMFI to run the program. On my new M1 MacBook, I don't want to degrade the security, so I want to search for another solution. I find this article explaining how to sign gdb with the permission to debug other programs (create and trust your own signing certificate, then use it to sign gdb), but using the same steps (replacing com.apple.security.cs.debugger with com.apple.developer.vfs.snapshot) failed (get SIGKILL immediately) with these messages in Console:

ERROR	21:05:32.777057+0800	taskgated-helper	Disallowing snaputil because no eligible provisioning profiles found
DEFAULT	21:05:32.777558+0800	kernel	mac_vnode_check_signature: /Volumes/Data/snaputil: code signature validation failed fatally: When validating /Volumes/Data/snaputil:
  Code has restricted entitlements, but the validation of its code signature failed.
Unsatisfied Entitlements:
DEFAULT	21:05:32.777568+0800	kernel	proc 23718: load code signature error 4 for file "snaputil"
DEFAULT	21:05:32.777446+0800	amfid	/Volumes/Data/snaputil signature not valid: -67671

What do these error messages mean? Is it impossible to run snaputil and manage APFS snapshots without paying Apple or degrading the system security?

Currently, my iMac has no active macOS on it. And the Fusion Drive shows up as two volumes. I am trying to come up with ways to fix the Fusion Drive, install macOS on it(but then how to make Fusion Drive APFS to make it usable as a boot drive for macOS without destroying the logical volume structure?), and then partition the Fusion Drive into three partitions. Environment: 11.5 GB partition on SSD, main contents are a base macOS recovery image (internet installer) and macOS install drive (Catalina). The rest of the SSD is a free partition (formatted in APFS). All of HDD is a free partition (formatted in APFS). Currently, I tried: 1. Fixing my Fusion Drive, then partitioning it. (Partition Fusion Drive breaks its ability to be a valid install drive for macOS, also unknown if the corestorage system still works after being partitioned.) 2. Add multiple volumes into a logical volume group to achieve multiple drives. (Currently not possible, requires older versions of diskutil.)

I'm trying to create a Chrome OS Flex USB install drive, to install it via Parallels, on macOS 13.4 (2019 i9 MBP). I'm able to create it both via the Chrome browser extension, and the terminal sudo dd if=chromeos.bin of=/dev/disk2 bs=4M status=progress method... but after both methods, it shows the same wya in Disk Utility, however it's not readable in macOS, so Parallels cannot install *from it* -- there's no way to pick it as the USB drive source, or open the .bin image. Am I missing something simple? I cannot find this as a known issue, and there are instructions on how to do this with a Mac.. here's what I used: - https://support.google.com/chromeosflex/answer/11552529?hl=en - https://www.parallels.com/blogs/run-chrome-os-flex-in-parallels-desktop-for-mac/ I tried using the USB band new, and again formatted to APFS first — but both create the same thing when creating the ChromeOS Flex USB drive, so I don't think the starting point matters.. but here's the drive: - https://www.westerndigital.com/products/usb-flash-drives/sandisk-cruzer-glide-usb-2-0#SDCZ60-032G-B35 The latest ChromeOS Flex .bin is here: - https://dl.google.com/chromeos-flex/images/latest.bin.zip Additional info I've found already: https://www.reddit.com/r/ChromeOSFlex/comments/swl5q9/chromeos_flex_links/

➜  ~ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk1         4.0 TB     disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +4.0 TB     disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD            9.1 GB     disk1s1
   2:              APFS Snapshot com.apple.os.update-... 9.1 GB     disk1s1s1
   3:                APFS Volume Macintosh HD - Data     2.2 TB     disk1s2
   4:                APFS Volume Preboot                 2.0 GB     disk1s3
   5:                APFS Volume Recovery                1.1 GB     disk1s4
   6:                APFS Volume VM                      20.5 KB    disk1s5

/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *31.4 GB    disk2
   1: FE3A2A5D-4F32-41A7-B725-ACCC3285A309               16.8 MB    disk2s2
   2: FE3A2A5D-4F32-41A7-B725-ACCC3285A309               16.8 MB    disk2s4
                    (free space)                         136.3 MB   -
   3:           Linux Filesystem                         16.8 MB    disk2s8
   4:                        EFI EFI-SYSTEM              67.1 MB    disk2s12
   5: 3CB8E202-3B7E-47DD-8A3C-7FF2A13CFCEC               2.1 MB     disk2s5
   6: 3CB8E202-3B7E-47DD-8A3C-7FF2A13CFCEC               2.5 GB     disk2s3
   7:           Linux Filesystem                         4.3 GB     disk2s1

I recently attempted to clone a failing external drive to a new external drive. The clone failed part-way into the process. The original drive hardware has now fully failed, so I'm trying to recover as much as I can from the clone. When I plug in the clone, macOS gives me an error reading "The disk 'Volume_Name' can't be unlocked. A problem was detected with the disk that prevents it from being unlocked." Disk Utility shows 1.6 TB used. I tried unlocking it from the command line and the Terminal output was Passphrase incorrect or user does not exist. I am certain I'm entering the passphrase correctly. A scan in Data Rescue shows a recognizable list of files and folders. I can copy a file from the clone, but I can't open it. I am guessing that the files are encrypted individually while the folder structure is not. From my research, macOS creates a separate cryptouser on an encrypted disk (separate from a Mac account/user) so that one password can open the disk on any Mac. When I used diskutil apfs listcryptousers /dev/Volume_Name in Terminal, the output is No cryptographic users for Volume_Name when it *should* output something like this: I believe I've recovered the clone volume's cryptouser string from Keychain Access on two separate Macs (they match), so I have both the user and the passphrase. Is there a way to enter these manually and decrypt the drive? Either via the Terminal or a third-party piece of software? For reference, I got a lot of information from this page even though it outlines boot drives instead of external ones. Thank you in advance!

I'm trying to delete all backups of specific items backed up with TimeMachine on a backup drive formatted as HFS+ but using a Mac running Ventura. For a long time this was possible using the method described [here](https://apple.stackexchange.com/questions/333767/delete-all-backups-of-specific-file-folder-with-tmutil) and [here](https://apple.stackexchange.com/questions/180214/is-it-possible-to-use-tmutil-delete-or-another-command-to-delete-one-file-from) : The gist of it is don't bother with tmutil, use rm with the bypass helper script from TMSafetyNet.kext. I've used it successfully many times. Unfortunately, with newer versions of macOS TMSafetyNet.kext is gone -- not sure when exactly it disappeared, but it's no longer there as discussed [here](https://apple.stackexchange.com/questions/459407/macbook-pro-m2-missing-tmsafetynet-kext) (in a different context). Now, I've tried the following: First, using what seems to be the official method as described in man tmutil I have tried: sudo tmutil delete -d /Volumes/ -p /Volumes//Backups.backupdb///Macintosh\ HD/path/to/file/ I get: Invalid deletion target (error 22), Total deleted: Zero KB Now, the same backup from which I want to delete a specific file also has a backup of my system files, including TMSafetyNet.kext. I thought let's try the old method, pointing it to the backup of the bypass helper script: sudo /Volumes//Backups.backupdb///Macintosh\ HD/System/Library/Extensions/TMSafetyNet.kext/Contents/Helpers/bypass rm -rfv /Volumes/ -p /Volumes//Backups.backupdb///Macintosh\ HD/path/to/file/ It fails, because, as @nohillside points out in the comment below, TMSafetyNet.kext is not loaded. How can I delete all backups of a file on an HFS+-formatted TM volume on newer machines running a macOS version that no longer has TMSafetyNet.kext?

I'd like to use a clean install of the latest Big Sur (11.4 or 11.5) on a machine that currently has Yosemite installed. I'd like to keep using Yosemite due to some legacy apps/licenses. - Ideally I'd like to edit the same files from both Yosemite and Big Sur - I've also considered accessing data and installing/running an app on a different partition to the one with the OS - However, I'm realising that there could be challenges due to the HFS and APFS formatting --- I have Yosemite (10.10.3) installed on the Macintosh HD partition. I have two other partitions which I use as data storage (e.g. Word, Excel files). P1) Macintosh HD (480GB, Yosemite already installed) P2) 2 - 430GB P3) 5 - 90gb Scenario (i): P1) Macintosh HD (480GB, Yosemite already installed) P2) 2 - 430GB (Big Sur would be installed) P3) 5 - 90gb Scenario (ii): P1) Macintosh HD (480GB, Yosemite already installed) P2) 2 - 430GB P3) 5 - 90gb (Big Sur would be installed) All three partitions according the disk util are: File System Personality: Journaled HFS+ Type (Bundle): hfs **Question that arises:** 1) With reference to the two scenarios above, is it possible to access (both read & write) files (e.g. a Word document) and or run apps stored on a different partition than the one with the running OS?...Or will the partition (with the other OS installed) no longer be visible? A.) If yes, how does this work if one of the drives is JHFS+ and the other is APFS? B.) If not, would it be better to store data on a partition that doesn't have any OS installed (used almost like an external SDD except that it's internal)? C.) Would there be any issues from installing apps not on the same partition as the one with OS-installed? E.g. app files that need to be located in the system, caches, application support and library folders Machine: MacBook Pro (Retina, 15-inch, Mid 2015) 1TB SSD (3 Partitions): /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS Macintosh HD 479.5 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 4: Apple_HFS 2 - 430GB 430.3 GB disk0s4 5: Apple_HFS 5 - 90gb 89.7 GB disk0s5 I've made an attempt to answer my question below but I'm still unclear on a few points (I've added my research with links there).

I have a MacBook Pro (Retina, 15-inch, Mid 2015) running Mac OS Mojave. When I boot it up, it shows a grey screen with a question mark on a folder. I have figured out that the issue is with the internal SSD as I can boot from a USB installer with Mojave just fine. I can see the internal disk with diskutil and also see /Volumes/Macintosh\ HD/ from the terminal. I was able to recover the few files this way that I hadn't backed up earlier. However this was too slow as even an ls command on the Macintosh HD Volume takes a couple of minutes to execute and the system.log in /var/log shows loads of error messages of this type: Kernel: disk1: I/O error. But, I managed to get the files I needed. Now I want to wipe the SSD or atleast erase the data from the /Volumes/Macintosh\ HD/, but I am not able to do that. I tried Disk Utility but it just hangs every time I open it and running diskutil from the terminal on always ends up with some error. I have tried verifyVolume, repairVolume, eraseVolume, deleteVolume, deleteContainer and eraseDisk with diskutil but they all end with an error which looks something like this: Error: -69877: Couldn't open device or similar to this. I found this answer [here](https://discussions.apple.com/thread/251710920) to delete the APFS partition using a bootable USB with Linux Mint. This ended with an error message too saying Input/output error. Is there any way I can wipe the SSD clean? The disk and the volume are not encrypted and I have also tried resetting NVRAM, PRAM and SMC but none of that helped. Booting up into Recovery Mode doesn't help either. It shows a spinning globe but there is no progress bar, and nothing happens.

I have automatic backup enabled and local TimeMachine snapshots take a large amount of disk space. This space is listed as purgeable in disk info, but cannot be actually used until the system decides to free it up. How can I force TimeMachine to delete those snapshots?

Trying to update an iMac (2015, I believe?) a friend gave me. They've fully signed out of it, and I have erased the hard drive in disk utilities, but I cannot get it to boot to anything. When I choose to install OS, it loads El Capitan, and when I try to sign in, it says "This item is temporarily unavailable." The message boards I've read say to wipe the drive and format to APFS, but that doesn't show up in the options. I'm generally computer-literate, but this is just deeply frustrating me. Any help would be appreciated.

I have a Macbook Pro Early 2011 version 10.13.6 (17G66) What happened is I was having macOS High Sierra and I did install macOS Sonoma using openCore. After that I took off my hard drive to upgrade to SSD and I think took it before the computer shut it off completely. So I had a problem with new installation so I try to plug back my old hard drive. Not booting black screen just BOOTCAP (WINDOWS) so I used terminal to see what happened is I get FFFF.FFFF.FFFFFFF.FFFFFFFFF on my GUID. I try to delete the partition and re-crate them but I still cant access to my partition. I am hoping to fix my setup and recover data from the storage if I can’t make it boot correctly. I tried this method but im still have the same problem

sudo gpt destroy disk1
sudo gpt create -f disk1

Re-add all the partitions:

sudo gpt add -i 1 -b 40 -s 409600 -t C12A7328-F81F-11D2-BA4B-00A0C93EC93B disk1
sudo gpt add -i 2 -b 409640 -s 820115416 -t 7C3457EF-0000-11AA-AA11-00306543ECAC disk1
sudo gpt add -i 3 -b 820525056 -s 156248064 -t EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 disk1

I'm using rsync on top of a [mount_apfs snapshots](https://apple.stackexchange.com/a/347257/238365) , to backup a consistent file system view and without having to stop applications during the backup. After having investigated the rsync error 'file has vanished', I've discovered that tmutil doesn't create real snapshots:

15:50:34 [admin@MyMac ~]$ tmutil snapshot /
Created local snapshot with date: 2020-12-21-155054
15:52:08 [admin@MyMac ~]$ sudo mount_apfs -o rdonly -s "com.apple.TimeMachine.2020-12-21-155054.local" / /tmp/snap
Password:
15:52:30 [admin@MyMac ~]$ cat /etc/profile
# System-wide .profile for sh(1)

if [ -x /usr/libexec/path_helper ]; then
	eval /usr/libexec/path_helper -s
fi
...
15:53:20 [admin@MyMac ~]$ vi /etc/profile

  

15:58:42 [admin@MyMac ~]$ cat /tmp/snap/etc/profile
# System-wide .profile for sh(1)
#             <====
# TEST CHANGE <====
if [ -x /usr/libexec/path_helper ]; then
...

As you can see, all changes are reflected in the mounted snapshot. I've also tried file additions and deletions. I think the problem is that Catalina has started to split the whole file system into a read-only system volume plus a data volume (plus maybe something else?):

16:07:33 [admin@MyMac ~]$ df -h
Filesystem                                                   Size   Used  Avail Capacity iused      ifree %iused  Mounted on
/dev/disk1s6                                                466Gi   11Gi  176Gi     6%  488281 4881964599    0%   /
devfs                                                       197Ki  197Ki    0Bi   100%     682          0  100%   /dev
/dev/disk1s5                                                466Gi  276Gi  176Gi    62% 2492125 4879960755    0%   /System/Volumes/Data
/dev/disk1s4                                                466Gi  2.0Gi  176Gi     2%       2 4882452878    0%   /private/var/vm
/dev/disk1s1                                                466Gi  804Ki  176Gi     1%      88 4882452792    0%   /Volumes/Macintosh HD - Data
map auto_home                                                 0Bi    0Bi    0Bi   100%       0          0  100%   /System/Volumes/Data/home
map -fstab                                                    0Bi    0Bi    0Bi   100%       0          0  100%   /System/Volumes/Data/Network/Servers
/dev/disk3s1                                                 25Gi   com.apple.TimeMachine.2020-12-21-155054.local@/dev/disk1s6  466Gi   11Gi  176Gi     6%  488281 4881964599    0%   /private/tmp/snap
16:07:35 [admin@MyMac ~]$

I could try to mount the more specific file systems, but the problem is I want to make the whole / visible to rsync, to perform a system backup. Is there a way?