I have a MacBook Air running Big Sur with a 256GB hard drive that is formatted like this: Because of this, I have extremely limited storage space to work with, even though I never set it up this way and don't care for redundant drive. I have ample iCloud storage for backups. How can this be fixed, preferably by condensing to one volume?

My Mac still boots into Windows recovery mode, automatically. I can still boot into macOS and everything works, however I want to remove this partition. When I first start my Mac it also shows up with a loading gear icon in the middle of my screen. Running "diskutil list" gave me this:

`

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *251.0 GB   disk0

   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1

   2:                 Apple_APFS ⁨Container disk1⁩         250.8 GB   disk0s2


/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      APFS Container Scheme -                      +250.8 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨Kkr dikke schijf - G...⁩ 97.1 GB    disk1s1

   2:                APFS Volume ⁨Preboot⁩                 441.2 MB   disk1s2

   3:                APFS Volume ⁨Recovery⁩                1.1 GB     disk1s3

   4:                APFS Volume ⁨VM⁩                      1.1 MB     disk1s4

   5:                APFS Volume ⁨Kkr dikke schijf⁩        15.2 GB    disk1s5

   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.2 GB    disk1s5s1

` Which partition do I need to remove?

To increase the size of Main, I have merged the Main(Encrypted APFS) with another APFS partition. But now it is showing the previous size and I am not able to use the added space (See the size of Drive and Partition). /dev/disk0 (internal): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme 121.3 GB disk0 1: EFI EFI 314.6 MB disk0s1 2: Apple_HFS Rana 12.7 GB disk0s2 3: Apple_APFS Container disk1 12.7 GB disk0s3 4: Apple_APFS Container disk2 69.8 GB disk0s4 /dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +12.7 GB disk1 Physical Store disk0s3 1: APFS Volume Untitled 819.2 KB disk1s1 /dev/disk2 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +69.8 GB disk2 Physical Store disk0s4 1: APFS Volume Main 62.9 GB disk2s1 2: APFS Volume Preboot 43.4 MB disk2s2 3: APFS Volume Recovery 510.6 MB disk2s3 4: APFS Volume VM 1.1 GB disk2s4

I want to make a replacement parition for bootcamp purposes, any way to help?

I was restarting back to mac, when I think I closed my computer or otherwise shut off during restarting. When I opened it again, I was locked out and stuck in this loop of entering password to unlock disk. I know I am entering correct password, and I know this is a semi common problem from other search results. This has previously happened to me, and the fix, without losing any files, was to just reinstall macos. Now though, there is not enough space on my mac to reinstall macos, I'm just short a few megabytes. I currently only have access to my windows partition. Is there any way to resize or delete this partition and to add that space back to the macos partition? I am a little scared of using disk utility, I know it can delete the partition but I am afraid that even if the space might be freed up, I won't be able to reclaim that space without corrupting my files on macos. Is it safe to just delete my bootcamp partition? Is there anyway to free up space from the windows side and reclaiming? I previously used minitool partition wizard to resize my partition before, but if I recall I had to first partition off some of my mac partition in macos, and then claimed that space within windows. Does disk utility have this capability, or some terminal commands to be able to do this? It is a macbook pro 2021

Same issue as related in this thread but I already did the following: - Re-created a new GPT (GUID) partition table (using GParted, Ubuntu) - Created an HFS+ partition specifically for my MacOS - Re-created an EFI system partition of +500Mb And yet, when using the Internet Recovery Mode, two things happen: 1. The wrong MacOS is being downloaded (Mac OS X Yosemite, instead of Monterrey) 2. The HFS+ partition created does not show. ----------------- **What did I miss?** A possible solution would be to reformat the hard drive using Diskutil (Terminal, Recovery Mode) but no idea how to target the correct hard drive. ----------------- This what my partition table looks like from GParted: And this is what my Disk Utility shows on Recovery Mode: ----------------- Things to take into consideration: - I used to have an APFS hard drive before. But that must have been replaced by the HFS+ partition. - I did not use FileVault or encrypted the disk (have had a lot of problems in using that).

I have a mid-2012 Intel Macbook Air (256GB) which is physically fine. I had bought it second-hand in 2017 & the seller specified that it was only running Windows 10 & did not have macOS installed. He had updated Bootcamp Windows 7 to Windows 10. Now I want to use it for macOS but I can't access the Mac partition because it doesn't exist on that machine. I tried all the Command+R, Command+Option+R key combinations, but nothing worked. The Bootcamp assistant software is also missing. Also tried to use a USB stick to boot from but wasn't successful. :( The disk partitions currently looks like this: How can I restore macOS function while preserving my windows installation?

I have an external hard drive that I put a linux operating ISO on, but now I am trying to erase the external back into ExFat format to store files on it. When I go into DiskUtil, and try to erase it, it just tells me the process failed. I then went through the steps of trying to delete the APFS Container, I find the identifier using diskutil list then typing diskutil apfs deleteContainer disk2s2. It then just gives me a message that it is unable to find the reference to the container Unable to look up the APFS Container Reference for the given Physical Store. I cannot find anything online on how to get this back to a state I can use it, any advice?

I have a Mac Mini with two hard drives inside. The 1st one has an OS installed, and the files I work from. But I wanted to have the second one be used partly for storage, and partly have an OS installed in case the first HD crashes. I'm imagining that if my main drive fails one day, I will be able to keep working uninterrupted by updating drive 2 with **Time Machine**. However in the meanwhile, I'd like to use Drive 2 for storage (while booting from drive 1). I found this article , but it doesn't really say if this scenario would let the user use the rest of the partition for storage if the computer is booted from another drive. **Does this sound like a logical plan, and how would I format and instal the second drive?**

I am having problem dealing with this situation: after I deleted a system that I don't want via eraseVolume, I don't have the access to this 119.4 GB space below. I have no idea how to recover it, even with disk drill. Now all I want it to be is at where the Macintosh HD is at and make it a part of the main partition. I have the diskutil list output below and the sudo gpt -r show disk0 output.

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.

I'm new to mac I just got my first macbook used last week. I was trying to install Windows 10 via boot camp and it told me it could not due to some issue and to check Disk Utility. I have used Linux and Windows to a lesser degree most of my life, but I am embarrassed to say I don't fully understand this. I ran diskutil list & diskutil apfs list and this is the output. I saw these commands on some other post and thought they may be helpful. This is probably completely normal. I am sure I just want to understand. I am on the newest update of Catalina MBP Mid 2017. Also, it is not super important to get Boot Camp running Windows. I was just experimenting, but does anyone see an obvious reason why there would be an issue? Thank you! /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *251.0 GB disk0 1: EFI EFI 314.6 MB disk0s1 2: Apple_APFS Container disk1 250.7 GB disk0s2 /dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +250.7 GB disk1 Physical Store disk0s2 1: APFS Volume Untitled - Data 127.1 GB disk1s1 2: APFS Volume Preboot 83.8 MB disk1s2 3: APFS Volume Recovery 528.5 MB disk1s3 4: APFS Volume VM 1.1 GB disk1s4 5: APFS Volume RJ 11.2 GB disk1s5 SuperSecretCPU:~ adminMan$ diskutil apfs list APFS Container (1 found) | +-- Container disk1 A7F6C36A-FBDB-4322-831A-9FC2CEF2606A ==================================================== APFS Container Reference: disk1 Size (Capacity Ceiling): 250685575168 B (250.7 GB) Capacity In Use By Volumes: 140339167232 B (140.3 GB) (56.0% used) Capacity Not Allocated: 110346407936 B (110.3 GB) (44.0% free) | +- Volume disk1s1 A7C6B5CE-2F45-3C34-B29C-317C531A82E8 | --------------------------------------------------- | APFS Volume Disk (Role): disk1s1 (Data) | Name: Untitled - Data (Case-insensitive) | Mount Point: /System/Volumes/Data | Capacity Consumed: 127352475648 B (127.4 GB) | FileVault: No | +-> Volume disk1s2 1A886DD1-7F92-4787-B32A-02620DF632E8 | --------------------------------------------------- | APFS Volume Disk (Role): disk1s2 (Preboot) | Name: Preboot (Case-insensitive) | Mount Point: Not Mounted | Capacity Consumed: 83750912 B (83.8 MB) | FileVault: No | +-> Volume disk1s3 5806096A-0C66-4F74-9773-20B8D47F2E2A | --------------------------------------------------- | APFS Volume Disk (Role): disk1s3 (Recovery) | Name: Recovery (Case-insensitive) | Mount Point: Not Mounted | Capacity Consumed: 528502784 B (528.5 MB) | FileVault: No | +-> Volume disk1s4 5E468A33-0424-49C6-9249-42F0CDF2CFDE | --------------------------------------------------- | APFS Volume Disk (Role): disk1s4 (VM) | Name: VM (Case-insensitive) | Mount Point: /private/var/vm | Capacity Consumed: 1074810880 B (1.1 GB) | FileVault: No | +-> Volume disk1s5 612780D1-B6D1-47E4-9678-E5AE176EB13A --------------------------------------------------- APFS Volume Disk (Role): disk1s5 (System) Name: RJ (Case-insensitive) Mount Point: / Capacity Consumed: 11161202688 B (11.2 GB) FileVault: No

So I used the procedures in this link to try and set up windows in my iMac , but when it reached the part where they asked where do you want install Windows and after I select BOOT CAMP, I got an error - " We couldn't create a new partition or locate an existing one."

I have tried in vain to get my MacBook Air back up and running. I did a system restore or reinstall a while back and something broke. I've tried command+R and a bootable USB, there doesn’t appear to be a time machine partition or option. Which partition should I format? Can I clear them all and start from scratch? If someone could show me how to get this issue resolved so I can use my laptop again that’d be great.

I have a USB hard drive that I want to use as my Time Machine backup disk. I want it to be encrypted. If I partition it as an encrypted disk, it finishes fine; but then if I run First Aid, it says it's corrupt. If I partition it UNencrypted, First Aid says it's fine. I've repeated it multiple times. Encrypted = corrupt. Unencrypted = okay. Why would the disk only read as corrupt when encrypted? Running OS 10.15 on a 2014 MacBook This is the First Aid log when I get the error. If it's unencrypted, it's short and sweet -- all "okay". Running First Aid on “WD easystore 25FA Media” (disk2) Checking prerequisites Checking the partition list Checking the partition map size Checking for an EFI system partition Checking the EFI system partition’s size Checking the EFI system partition’s file system Checking the EFI system partition’s folder content Checking all HFS data partition loader spaces Checking booter partitions Checking booter partition disk2s3 Verifying file system. Volume is already unmounted. Performing fsck_hfs -fn -x /dev/rdisk2s3 Checking Journaled HFS Plus volume. Checking extents overflow file. Checking catalog file. Checking multi-linked files. Checking catalog hierarchy. Checking extended attributes file. Checking volume bitmap. Checking volume information. The volume Boot OS X appears to be OK. File system check exit code is 0. Restoring the original state found as unmounted. Checking Core Storage Physical Volume partitions Verifying storage system Performing fsck_cs -n -x --lv --uuid 0AD74A3C-D0D6-42F5-B0D4-9FB8486ABC99 Checking volume disk2s2: Scan for Volume Headers disk2s2: Scan for Disk Labels Logical Volume Group 0AD74A3C-D0D6-42F5-B0D4-9FB8486ABC99 on 1 device disk2s2: Scan for Metadata Volume Logical Volume Group has a 24 MB Metadata Volume with double redundancy Start scanning metadata for a valid checkpoint Load and verify Segment Headers Load and verify Checkpoint Payload Load and verify Transaction Segment Load and verify Transaction Segment Incorporate 1 newer non-checkpoint transaction Load and verify Virtual Address Table Load and verify Segment Usage Table Load and verify Metadata Superblock Load and verify Logical Volumes B-Trees Logical Volume Group contains 1 Logical Volume Load and verify 2C6C36E4-9E7A-433B-847C-BEE4D39BFBF2 Load and verify B8B932A7-B825-48D5-A577-5485DDD0DE76 Load and verify Freespace Summary Load and verify Block Accounting Blocks on device 26EC24D8-82B4-4CA5-B361-FB2194641A72 are not accounted for by CoreStorage Unable to bootstrap transaction group 6: inconsistent crosscheck Continue scanning metadata for an older checkpoint Load and verify Segment Headers Load and verify Checkpoint Payload Load and verify Transaction Segment Incorporate 0 newer non-checkpoint transactions Load and verify Virtual Address Table Load and verify Segment Usage Table Load and verify Metadata Superblock Load and verify Logical Volumes B-Trees Logical Volume Group contains 0 Logical Volumes Load and verify Freespace Summary Load and verify Block Accounting Blocks on device 26EC24D8-82B4-4CA5-B361-FB2194641A72 are not accounted for by CoreStorage Unable to bootstrap transaction group 5: inconsistent crosscheck Continue scanning metadata for an older checkpoint Load and verify Segment Headers Load and verify Checkpoint Payload Load and verify Transaction Segment Incorporate 0 newer non-checkpoint transactions Load and verify Virtual Address Table Load and verify Segment Usage Table Load and verify Metadata Superblock Load and verify Logical Volumes B-Trees Logical Volume Group contains 0 Logical Volumes Load and verify Freespace Summary Load and verify Block Accounting Blocks on device 26EC24D8-82B4-4CA5-B361-FB2194641A72 are not accounted for by CoreStorage Unable to bootstrap transaction group 4: inconsistent crosscheck Continue scanning metadata for an older checkpoint Load and verify Segment Headers Load and verify Checkpoint Payload Load and verify Transaction Segment Incorporate 0 newer non-checkpoint transactions Load and verify Virtual Address Table Load and verify Segment Usage Table Load and verify Metadata Superblock Load and verify Logical Volumes B-Trees Logical Volume Group contains 0 Logical Volumes Load and verify Freespace Summary Load and verify Block Accounting Blocks on device 26EC24D8-82B4-4CA5-B361-FB2194641A72 are not accounted for by CoreStorage Unable to bootstrap transaction group 3: inconsistent crosscheck No valid commit checkpoint found The volume 0AD74A3C-D0D6-42F5-B0D4-9FB8486ABC99 was found corrupt and needs to be repaired Storage system check exit code is 1. Problems were found with the partition map which might prevent booting Storage system verify or repair failed. : (-69716) Operation successful.

I tried partitioning my Apple Fusion Drive (32GB Flash on it) in Disk Utility and it results in an error that one of the partitions I created is < than the minimum size of 24GB. Is anyone else having this problem as well? Can you partition your Fusion Drive for another operating system? Perhaps with alternate software like fdisk using a Linux bootable USB drive?

My late 2012 MacBook Pro is running Catalina. I used the Bootcamp Assistant to format a blank flash drive, copy my Windows 10 ISO file (downloaded from the provided Bootcamp assistant link) onto the flash drive, download the latest Windows software support from Apple, and create a new Windows partition to install it on (in other words, I checked all three boxes on the bootcamp assistant menu). It took about 4 hours for the computer to finish it all, but after I confirmed my password a few times and it finally finished, my computer restarted automatically, booting to the windows partition by default. But, instead of any kind of Windows 10 install menu (even though it seems like the install should have already been completed by the bootcamp assistant), it just says "NO BOOTABLE DEVICE - INSERT BOOT DISK AND PRESS ANY KEY." I restarted and booted back to OS X, removed the Windows partition using the bootcamp assistant, and then did it all again, even re-formatting and re-copying windows to the newly blank flash drive. Same result. Then, I tried it again using a different flash drive, with the same result. When I restart the computer and hold alt/opt, It only shows my OS X drive, as well as "Windows" and "EFI BOOT". When I boot onto "Windows", it takes me to what looks like the install menu for Windows 10 on a blank computer, but when the option comes up for which drive to install Windows on, and I try to click the 300GB partition that I created using Bootcamp, it says "Windows cannot be installed on this disk." I'm not sure what's wrong with it. A few months ago, when I was running Mojave instead of Catalina, I installed Windows 10 in the exact same way, and it worked fine.

I'm having a MacBook Pro with M2 chip from the company I work for. It is allowed to use the device with a separate OS installed on it. That's why I currently have two partitions, each with another version of MacOSX installed (one for the company and one for my private purposes). I made the mistake to give the first partition (the company OS partition) too less space (100GB) and I need to extend it to have more. Else I cannot install required updates and so on. The problem is, that by shrinking the second partition, free space is added AFTER it. But to extend the first partition, it would be necessary to move the shrinked partition to the end, to have the free space BEFORE it. Is this somehow possible? I remember, that with GParted (on a "normal" PC) it was possible to move partitions around (which took more time, of course). Can this be done on this ARM device? Do you know a tool? Is it probably possible with a Ubuntu Linux on an USB stick? Thanks for your help!