You a not suppose to remove the EFI partition. This partition was created when macOS was installed. To remove the Ubuntu files from the FA32 formatted volume stored in this partition, take the following steps.
Note: I realize, it is to late for you to follow these steps. I post the steps for others who may have the same question.
Boot to macOS and open a ...
Thanks to a comment from @benwiggy I was able to solve my problem. Appears you need to explicitly unmount the disk before partitioning it. Not sure why it was mounted anyway. In any case, after unmounting with
> diskutil unmountDisk force /Volumes/my_disk_name
Partitioning went without error.
Neither is actually correct.
The problem has nothing at all to do with APFS. As the linked answer describes, it has to do with the location of the partitioning tables.
If your source and destination drives have the same sector sizes, you can just copy using ordinary dd without any special parameters.
If they do not have the same sector size (as in the linked ...
Firstly, you should always have a backup of your files, so there should be no question of losing anything. Files without a backup are waiting to be lost.
If the Recovery partition is indeed on Lion, then it won't read the new APFS formatted disk that Big Sur uses.
Your first port of call should be to whoever wrote the patch, and ask them about whether it ...
It seems like the partition may have been deleted.
Try the -f option.
sudo gpt create -f /dev/disk2
By default, one cannot create a GPT when the device contains a
MBR, however this can be overridden with the -f option. If the
-f option is specified, an existing MBR is destroyed and any par-
titions described by the MBR are lost. - [GTP Man Page] https://...
This is quite normal under BigSur and it is not a partition, but a snapshot of your drive. E.g. mine looks quite similar:
There is nothing you need to worry about and you should not try to delete it. This exact layout has been also discussed in Apple Forums, on MacRumors and on reddit.
To quote from reddit (user "Advanced_Path"):
Big Sur changes ...
I had the same problem, with VMware Fusion 15.5.3 and macOS 10.13.6.
Here's another way I solved this - although I had to do this BEFORE I increased the disk size in VMware (after I ran into the same problem as Michael the first time, I restored the VM from a backup). It does not work if you have already increased the size in VMware's settings.
The trick is ...
I managed to resolve that. For those who are interested here is the solution:
Install gdisk with the following command:
brew install gdisk
After that, run gdisk passing the disk that has the FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF.
sudo gdisk /dev/disk3
Then you will be prompted with the following questions. Answer like I did below.
Command (? for help): t
What you suggest is no longer possible with Big Sur. When booting to Recovery, you are required to enter a password of an existing account. AFAIK, these passwords are not stored in the Recovery volume. This would make it impossible to boot from a standalone Recovery disk.
Before Big Sur, there is no reason the an AFPS Recovery volume could not be placed on a ...