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 am trying to format a USB drive, however I am faced with the following error: sh-3.2# diskutil unmountDisk force /dev/disk3 Forced unmount of all volumes on disk3 was successful sh-3.2# diskutil eraseDisk JHFS+ MacOS /dev/disk3 Started erase on disk3 Unmounting disk Error: -69760: Unable to write to the last block of the device sh-3.2# lsof | grep disk3 sh-3.2# Could someone help me to figure out what to do to resolve this issue? EDIT 2: # fdisk -f boothfs /dev/disk3 Disk: /dev/disk3 geometry: 121601/255/63 [1953525168 sectors] Signature: 0x0 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ 1: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused sh-3.2# fdisk -i -a boothfs /dev/disk3 fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory ----------------------------------------------------- ------ ATTENTION - UPDATING MASTER BOOT RECORD ------ ----------------------------------------------------- Do you wish to write new MBR and partition table? [n] y sh-3.2# sh-3.2# diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *121.3 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_CoreStorage Macintosh HD 120.5 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 (internal, virtual): #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Macintosh HD +120.1 GB disk1 Logical Volume on disk0s2 7887C476-CBE0-4D10-B95A-5C79F83B20D7 Unencrypted /dev/disk3 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: *1.0 TB disk3 sh-3.2# EDIT 3 **(In CentOS 7)** # mkfs.ext4 /dev/sdc mke2fs 1.42.9 (28-Dec-2013) /dev/sdc is entire device, not just one partition! Proceed anyway? (y,n) y Warning: could not erase sector 2: Attempt to write block to filesystem resulted in short write Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 61054976 inodes, 244190646 blocks 12209532 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=2392850432 7453 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848 Allocating group tables: done Warning: could not read block 0: Attempt to read block from filesystem resulted in short read Warning: could not erase sector 0: Attempt to write block to filesystem resulted in short write Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: 0/7453 Warning, had trouble writing out superblocks.

I am on 11.1 Big Sur beta. I have a partition with no disk identifier called (free space) I would like to remove this, and then make the APFS container take up the free space. Here is a screenshot of my GPT and Disks

I am a long-term user of MacBooks / macOS, and I never experienced this many generated disks, not created by me. How concerning is that? Here is the output of the diskutil list:

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:             Apple_APFS_ISC Container disk1         524.3 MB   disk0s1
   2:                 Apple_APFS Container disk3         494.4 GB   disk0s2
   3:        Apple_APFS_Recovery Container disk2         5.4 GB     disk0s3

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +494.4 GB   disk3
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD            13.2 GB    disk3s1
   2:              APFS Snapshot com.apple.os.update-... 13.2 GB    disk3s1s1
   3:                APFS Volume Preboot                 12.3 GB    disk3s2
   4:                APFS Volume Recovery                1.9 GB     disk3s3
   5:                APFS Volume Data                    254.6 GB   disk3s5
   6:                APFS Volume VM                      20.5 KB    disk3s6

And this is the snapshot from **Disk Utility**:

After restoring Boot Camp (to remove it), the space hasn't been reclaimed by my AFPS partition and can not be seen in Disk Utility: The Physical Disk shows the correct size (1.92TB), but the APFS Container (Container 1) doesn't (1.47TB) when selecting each of them in Disk Utility. Using diskutil list the (free space) is shown, but with no identifier:

#:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.9 TB     disk0
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         1.5 TB     disk0s2
   3:       Microsoft Basic Data ⁨KRYPTONITE⁩              255.9 MB   disk0s3
                    (free space)                         448.2 GB   -

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.5 TB     disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨D1 - Data⁩               1.3 TB     disk1s1
   2:                APFS Volume ⁨Preboot⁩                 300.4 MB   disk1s2
   3:                APFS Volume ⁨Recovery⁩                1.1 GB     disk1s3
   4:                APFS Volume ⁨VM⁩                      1.1 MB     disk1s4
   5:                APFS Volume ⁨D1⁩                      23.4 GB    disk1s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 23.4 GB    disk1s5s1

How to I get my disk space back? I've restarted twice, run first aid with no issues and read 10+ questions relation to missing partitions after removing Boot Camp, with and without answers and non of them seem to adress this exact situation with no identifier for the free space. This question seems to be similar, but I have no WINDOWS RECOVERY partition in listed in diskutil, which the accepted answer revolves around. The KRYPTONITE partition needs to be preserved, so my EGPU is supported in MacOS. My memory is muddy, but I believe the KRYPTONITE partition was created after the (now deleted) BOOTCAMP partition. If that's of any importance. I'm running MacOS Monterey 12.6.5.

mount and df show that disk1s5 is a mounted volume:

bash-3.2$ mount
/dev/disk1s4s1 on / (apfs, sealed, local, read-only, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk1s2 on /System/Volumes/Preboot (apfs, local, journaled, nobrowse)
/dev/disk1s6 on /System/Volumes/VM (apfs, local, noexec, journaled, noatime, nobrowse)
/dev/disk1s5 on /System/Volumes/Update (apfs, local, journaled, nobrowse)
/dev/disk1s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
bash-3.2$ df -h
Filesystem       Size   Used  Avail Capacity iused      ifree %iused  Mounted on
/dev/disk1s4s1  233Gi  8.5Gi  149Gi     6%  356049 1561586480    0%   /
devfs           209Ki  209Ki    0Bi   100%     722          0  100%   /dev
/dev/disk1s2    233Gi  1.7Gi  149Gi     2%    2019 1561586480    0%   /System/Volumes/Preboot
/dev/disk1s6    233Gi  4.0Gi  149Gi     3%       4 1561586480    0%   /System/Volumes/VM
/dev/disk1s5    233Gi  3.8Mi  149Gi     1%      21 1561586480    0%   /System/Volumes/Update
/dev/disk1s1    233Gi   69Gi  149Gi    32%  594098 1561586480    0%   /System/Volumes/Data
map auto_home     0Bi    0Bi    0Bi   100%       0          0  100%   /System/Volumes/Data/home

However, disk1s5 does not appear in diskutil list:

bash-3.2$ diskutil list
/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 Macintosh HD - Data     74.2 GB    disk1s1
   2:                APFS Volume Preboot                 1.9 GB     disk1s2
   3:                APFS Volume Recovery                1.2 GB     disk1s3
   4:                APFS Volume Macintosh HD            9.2 GB     disk1s4
   5:              APFS Snapshot com.apple.os.update-... 9.2 GB     disk1s4s1
   6:                APFS Volume VM                      4.3 GB     disk1s6

diskutil info _does_ show information about disk1s5:

bash-3.2$ diskutil info disk1s5
   Device Identifier:         disk1s5
   Device Node:               /dev/disk1s5
   Whole:                     No
   Part of Whole:             disk1

   Volume Name:               Update
   Mounted:                   Yes
   Mount Point:               /System/Volumes/Update

   Partition Type:            41504653-0000-11AA-AA11-00306543ECAC
   File System Personality:   APFS
   Type (Bundle):             apfs
   Name (User Visible):       APFS
   Owners:                    Enabled

   OS Can Be Installed:       No
   Booter Disk:               disk1s2
   Recovery Disk:             disk1s3
   Media Type:                Generic
   Protocol:                  PCI-Express
   SMART Status:              Verified
   Volume UUID:               BE235512-940B-4A80-A1C7-7B6CB924E1D6
   Disk / Partition UUID:     BE235512-940B-4A80-A1C7-7B6CB924E1D6

   Disk Size:                 250.7 GB (250685575168 Bytes) (exactly 489620264 512-Byte-Units)
   Device Block Size:         4096 Bytes

   Volume Used Space:         4.0 MB (4034560 Bytes) (exactly 7880 512-Byte-Units)
   Container Total Space:     250.7 GB (250685575168 Bytes) (exactly 489620264 512-Byte-Units)
   Container Free Space:      159.9 GB (159881302016 Bytes) (exactly 312268168 512-Byte-Units)
   Allocation Block Size:     4096 Bytes

   Media OS Use Only:         Yes
   Media Read-Only:           No
   Volume Read-Only:          No

   Device Location:           Internal
   Removable Media:           Fixed

   Solid State:               Yes
   Hardware AES Support:      Yes

   This disk is an APFS Volume.  APFS Information:
   APFS Container:            disk1
   APFS Physical Store:       disk0s2
   Fusion Drive:              No
   Encrypted:                 No
   FileVault:                 No
   Sealed:                    No
   Locked:                    No

So why doesn't diskutil list show it? I thought diskutil list would always show all volumes, but it seems that certain mounted volumes are hidden.

I backup my Apple Silicon Mac (running macOS Sonoma) to an external, directly attached drive via Time Machine. All backup snapshots on that external drive I can list via $ ls -1 /Volumes/.timemachine// (\ is here a long hexadecimal number identifier.) In this directory are all the snapshots, for example /Volumes/.timemachine//2024-03-14-123547.backup However _inside_ the snapshot folder is no accessible Data directory. So I think I need to _mount_ the snapshot before I can access its data in the Terminal. So I tried

$ mkdir ~/TM_Backup
$ mount_apfs  -s com.apple.TimeMachine.2024-03-14-123547 / ~/TM_Backup

But I always get the error message "_mount_apfs: volume could not be mounted: Resource busy_" (I get this error with _all snapshots, so there must be something wrong with the command.) How can I mount the TimeMachine Backup snapshot via a Terminal command?

I'm working with multiple OS X versions frequently and I'd like to have an image which contains a particular OS version's system partition and its recovery partition. Is this possible? (the disk where these partitions are, contains several other partitions which I don't want, so full-disk image is not an option) I'm guessing this cannot be done as a single-step process, so I've already created an appropriately-sized sparsebundle image with GPT layout: hdiutil create -size 35g -layout GPTSPUD -type SPARSEBUNDLE /path/to/new_image.dmg The next step would be to copy the relevant partition onto this image, but I don't know how to do this. My Linux experience tells me the partitioning utility should be the place to look for this, but I don't see anything in diskutil's manual which looks like it does what I want. Hints/ideas?

I have a USB drive which is not showing up on finder or disk utility (in fact disk utility stuck on loading when inserted) running diskutil activity shows this log:

***DiskPeek ('disk4s1') Time=20240604-17:27:19.2469
***DiskAppeared ('disk4s1', DAVolumePath = '', DAVolumeKind = 'exfat', DAVolumeName = 'SD 128GB') Time=20240604-17:27:19.2539
***DiskMountApproval ('disk4s1', DAVolumePath = '', DAVolumeKind = 'exfat', DAVolumeName = 'SD 128GB') Comment=Approving Time=20240604-17:27:19.2553

Nothing else appears after DiskMountApproval. Why is this happening. I tried on a different Mac with same results. How can I get this to work without erasing anything on disk? ## Update Tried diskutil list but this command hangs indefinitely when the usb stick is inserted.

I tried making a bootable macOS Sierra DVD and now I'm stuck with 2 disk images whenever I boot into Recovery Mode. The DVD is no longer inside the optical unit obviously. Ejecting doesn't work. Unmounting doesn't work. I tried resetting the PRAM with no result. I tried "diskutil unmountdisk force" with no result. These images weren't there prior to my failed attempt at installing from a DVD. There must be some sort of registry/cache somewhere.

I was trying to remove Ubuntu (dual boot) from my 2017 Macbook Air. Now my computer can not start successfully in either macOS or Linux. When I restart it, it now opens refind, then gnu rnu in both macOS and Linux. I used Disk Utility when trying to remove Ubuntu. I don't completely remember what I did. However, I could not remove the partition Ubuntu uses. Then, I opened macOS in recovery mode and did some changes using diskutil. The disk now looks like this: Can you help me fix this without losing my data? Is my data gone for good?  gpt -r show /dev/disk0 shows:  Disk utility shows:       Edit: Output of :

export LC_CTYPE="ASCII"
diskutil unmountdisk disk0
dd if=/dev/disk0 count=1 bs=16 skip=13108482 | vis -cw;echo

 Edit: It says resource busy when I entered the command gpt add -i 2 -b 409640 -t apfs disk0. 

I'm learning/trying diskutil, newfs_apfs and other disk command on macOS.
My idea is actually this: a) Create a 1 GiB container b) Add 5 volumes of 200 MiB size in the 1 GiB container I run these commands. Delete container diskutil apfs deleteContainer disk5 Container1 OK Create container diskutil apfs createContainer disk0s1 OK Now, I start to create the volumes, 200 MiB each (1 GiB can contain 5 volumes of 200 MiB) newfs_apfs -v "Volume1" -s 200M -A disk5 OK newfs_apfs -v "Volume2" -s 200M -A disk5 OK newfs_apfs -v "Volume3" -s 200M -A disk5 newfs_apfs: unable to format volume inside /dev/disk5: Result too large Why?
The command diskutil list reports this situation: /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.1 GB disk0 1: Apple_APFS Container disk5 1.1 GB disk0s1 /dev/disk5 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +1.1 GB disk5 Physical Store disk0s1 1: APFS Volume Volume1 209.7 MB disk5s1 2: APFS Volume Volume2 209.7 MB disk5s2 As you can see the container's volume uses only 420 MB of space and I have at least space for two other volumes.
What's wrong?

I have a virtual disk of 1 GB, on which I want to create two volumes of 400 MB. With diskutil partitionDisk /dev/disk0 2 GPT APFS VOLUME1 400M APFS VOLUME2 400M it created one APFS container of 400 MB and another one of 600 MB. How can I create two containers of 400 MB?

I'm trying to recover data from an encrypted sparsebundle on macOS Mojave (10.14.6) that I just discovered became corrupted at some point in the past. It was created several years ago. I have the password for it but I can't get it to mount, and attaching it via hdiutil (hdiutil attach -nomount -noverify -noautofsck -stdinpass Personal.sparsebundle) reveals that it has no file system anymore. My issue seems similar to the one in this thread , but I don't have the expertise to be able to work out a solution specific to my situation from what's been presented in klanomath's answer . Here are the same info results posted by that thread's op: **diskutil list /dev/disk3** /dev/disk3 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: +4.6 GB disk3 **diskutil info /dev/disk3** Device Identifier: disk3 Device Node: /dev/disk3 Whole: Yes Part of Whole: disk3 Device / Media Name: Disk Image Volume Name: Not applicable (no file system) Mounted: Not applicable (no file system) File System: None Content (IOContent): None OS Can Be Installed: No Media Type: Generic Protocol: Disk Image SMART Status: Not Supported Disk Size: 4.6 GB (4613734400 Bytes) (exactly 9011200 512-Byte-Units) Device Block Size: 512 Bytes Read-Only Media: No Read-Only Volume: Not applicable (no file system) Device Location: External Removable Media: Removable Media Removal: Software-Activated Virtual: Yes **fdisk /dev/disk3** Disk: /dev/disk3 geometry: 560/255/63 [9011200 sectors] Signature: 0x70F0 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ 1: E6 654 20 31 - 129 246 12 [1624655050 - 2384870584] 2: 74 860 66 38 - 581 106 0 [1253546114 - 3399439981] 3: 1E 517 38 4 - 333 65 17 [ 709288943 - 2881760601] 4: C4 32 116 61 - 816 121 22 [2129857911 - 2037640686] DRDOSs < 32M **gpt recover /dev/disk3** gpt recover: /dev/disk3: no primary or secondary GPT headers, can't recover **gpt -r -vv show /dev/disk3** gpt show: /dev/disk3: mediasize=4613734400; sectorsize=512; blocks=9011200 gpt show: /dev/disk3: MBR not found at sector 0 start size index contents 0 9011200 I'd really appreciate any help in trying to recover files from this bundle! Thank you.

I wanted to format and merge 2 partitions on my external hard drive. I used the command : diskutil erasevolume "Free Space" "" /dev/disks4s4. But now I lost 30go on 2TB and I can't merge the 30go I deleted. So now it looks like this:

/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk4
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk4s1
   2:                  Apple_HFS ⁨Maxtor⁩                  299.6 GB   disk4s2
                    (free space)                         134.3 MB   -
   3:       Microsoft Basic Data ⁨Donné⁩                   1.7 TB     disk4s3
                    (free space)                         30.9 GB    -

How can I merge the 30,9go to "Donné" which is in ExFat without losing data in "Donné"

I deleted the partition container by using the Terminal. Now I'm unable to create a partition. Photo of a System Recovery Terminal window showing the output of 'diskutil list': How can I delete all the partitions and create a new partition?

How can an external disk be initialized, partitioned and formatted in macos Sonoma commandline? I tried checking out my external drive with the command diskutil list:

...
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                                                   *2.0 TB     disk2

I can see that there is no partition or file system, I verified this with diskutil info disk2:

...
Volume Name:               Not applicable (no file system)
Mounted:                   Not applicable (no file system)
File System:               None
...

I just need one big partition formatted as APFS, I guess APFS should be the detault these days. I know I could have done it with Disk Utility, but I am looking to do this on the commandline.

I wish to resize my main macOS (High Sierra, HFS+) partition to use free space on the disk. I use console in Recovery Mode, as I suspect I won't be able the change the disk in use in standard mode. I however still cannot resize the partition, as the **system seems to fail to decide whether it is or not a coreStorage partition**:

-bash-3.2# diskutil list disk0
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage macOS                   20.0 GB    disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
-bash-3.2# diskutil resizeVolume disk0s2 limits
Resize limits for partition disk0s2:
  Current partition size on map:              20.0 GB (19999997952 Bytes)
  Minimum size (constrained by file usage):   14.4 GB (14392414208 Bytes)
  Recommended minimum size (if used for OS):  19.8 GB (19761123328 Bytes)
  Maximum size (constrained by map space):    999.3 GB (999344099328 Bytes)
-bash-3.2# diskutil resizeVolume disk0s2 R
Disk is a Core Storage Physical Volume (use a diskutil coreStorage verb instead to resize)
-bash-3.2# diskutil coreStorage resizeVolume disk0s2 R
disk0s2 does not appear to be a valid Core Storage Logical Volume UUID or disk

Ideally, I would like to keep the Recovery partition at the end of the physical disk, and the macOS partition to use all the space left. Any idea how I could solve this? I add here other disks (but still skipping the myriad of disks following, as I am in Recovery Mode) and diskutil cs list:

-bash-3.2# diskutil list | head -n 19
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage macOS                   20.0 GB    disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

/dev/disk1 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +2.1 GB     disk1
   1:                  Apple_HFS OS X Base System        2.0 GB     disk1s1

/dev/disk2 (internal, virtual):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS macOS                  +19.6 GB    disk2
								 Logical Volume on disk0s2
								 4F9A836A-6B15-4AEE-A4D7-51D0492069DF
								 Unencrypted

-bash-3.2# diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group A341966B-0864-44D2-9C72-821608B2DE0E
	=========================================================
	Name:         macOS
	Status:       Online
	Size:         19999997952 B (20.0 GB)
	Free Space:   18989056 B (19.0 MB)
	|
	+- Logical Volume Family 334245CF-35A1-42E8-AFBF-4EFE14DD2E9A
		----------------------------------------------------------
		Encryption Type:         None
		|
		+-> Logical Volume 4F9A836A-6B15-4AEE-A4D7-51D0492069DF
			---------------------------------------------------
			Disk:                  disk2
			Status:                Online
			Size (Total):          19628687360 B (19.6 GB)
			Revertible:            Yes (no decryption required)
			LV Name:               macOS
			Volume Name:           macOS
			Content Hint:          Apple_HFS

I accidentally unplugged my hard drive without properly ejecting it, and now the drive does not mount when plugged in. What can I do to make it work again? I can see the disk in lsusb and diskutil list. So far, I've tried: - sudo diskutil unmountDisk force /dev/disk2 - sudo diskutil unmount force /dev/disk2 - Reboot with disk. - Reboot without disk. It seems that the disk is working because it's vibrating very slowly, but I can't see it in Finder.

On my macbook M1, I created two volumes (one for my professional activity and one for my personal activity). Each volume has it's own macOS. The goal is to prevent remote administrators of one of the OSs (the one used for the professional activity) to be able to even see the content of the other volume. Here are some diskutil infos seen from each OS. **Volume 1 info seen from OS in Volume 1**: Volume type : APFS Startup Snapshot BSD device node : disk3s1s1 System : macOS 13.2.1 (22D68) File system : APFS (Encrypted) Owners enabled : Yes Is encrypted : Yes Bootable : Yes **Volume 2 info seen from OS in Volume 2**: Volume type : APFS Startup Snapshot BSD device node : disk3s8s1 System : macOS 12.3 (21E230) File system : APFS Owners enabled : No Is encrypted : No (Encrypted at rest) Bootable : Yes and **Volume 2 info seen from OS in Volume 1**: Volume type : APFS System Volume BSD device node : disk3s8 System : macOS 12.3 (21E230) File system : APFS Owners enabled : Yes Is encrypted : No (Encrypted at rest) Bootable : Yes I wanted to encrypt **Volume 1** and enabled FileFault. However, from within **Volume 2**, I'm still able to read (and even write) to **Volume 1**. Is it expected behaviour? LMK if more info are required, I will update the question.