M
sudo tmutil deletelocalsnapshots 2020-03-29-011256
sudo tmutil deletelocalsnapshots 2020-03-29-140423
➜ ~ sudo tmutil deletelocalsnapshots 2020-03-29-011256
Password:
Deleted local snapshot '2020-03-29-011256'
➜ ~ sudo tmutil deletelocalsnapshots 2020-03-29-140423
Deleted local snapshot '2020-03-29-140423'
➜ ~ tmutil listlocalsnapshotdates
Snapshot dates for all disks:
➜ ~
diskutil ap resizeContainer disk1 220g fat32 BOOTCAMP 0b ; diskutil list
➜ ~ diskutil ap resizeContainer disk1 220g fat32 BOOTCAMP 0b ; diskutil list
Started APFS operation
Aligning shrink delta to 30 790 438 912 bytes and targeting a new physical store size of 219 999 997 952 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 207 450 189 824 bytes
Resizing APFS Container designated by APFS Container Reference disk1
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l /dev/disk0s2
Checking volume
Checking the container superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the object map
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
Checking the snapshot metadata tree
Checking the extent ref tree
Checking the snapshots
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
Checking the snapshot metadata tree
Checking the extent ref tree
Checking the snapshots
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
Checking the snapshot metadata tree
Checking the extent ref tree
Checking the snapshots
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
Checking the snapshot metadata tree
Checking the extent ref tree
Checking the snapshots
Verifying allocated space
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk0s2 from 250 790 436 864 to 219 999 997 952 bytes
Shrinking APFS data structures
Shrinking partition
Modifying partition map
4096 bytes per physical sector
/dev/rdisk0s3: 60106016 sectors in 1878313 FAT32 clusters (16384 bytes/cluster)
bps=512 spc=32 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=430098432 drv=0x80 bsec=60135424 bspf=14680 rdcl=2 infs=1 bkbs=6
Mounting disk
1 new disk created or changed due to APFS operation
Disk from APFS operation: disk0s3
Finished APFS operation
/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 220.0 GB disk0s2
3: Microsoft Basic Data BOOTCAMP 30.8 GB disk0s3
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +220.0 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 199.1 GB disk1s1
2: APFS Volume Preboot 20.8 MB disk1s2
3: APFS Volume Recovery 515.0 MB disk1s3
4: APFS Volume VM 1.1 GB disk1s4
3: Microsoft Basic Data BOOTCAMP 30.8 GB disk0s3
diskutil eraseVolume free null disk0s3 ; diskutil ap resizeContainer disk1 0b ; diskutil list
➜ ~ diskutil eraseVolume free null disk0s3 ; diskutil ap resizeContainer disk1 0b ; diskutil list
Started erase on disk0s3 BOOTCAMP
Unmounting disk
Finished erase on disk0
Started APFS operation
Aligning grow delta to 30 790 438 912 bytes and targeting a new physical store size of 250 790 436 864 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 250 789 408 768 bytes
Resizing APFS Container designated by APFS Container Reference disk1
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l /dev/disk0s2
Checking volume
Checking the container superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the object map
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
warning: invalid dstream.default_crypto_id (0x0) for encrypted volume, given apfs_fs_flags (0x8)
Checking the snapshot metadata tree
Checking the extent ref tree
Checking the snapshots
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
Checking the snapshot metadata tree
Checking the extent ref tree
Checking the snapshots
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
Checking the snapshot metadata tree
Checking the extent ref tree
Checking the snapshots
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
Checking the snapshot metadata tree
Checking the extent ref tree
Checking the snapshots
Verifying allocated space
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Growing APFS Physical Store disk0s2 from 219 999 997 952 to 250 790 436 864 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
/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 Macintosh HD 199.1 GB disk1s1
2: APFS Volume Preboot 20.8 MB disk1s2
3: APFS Volume Recovery 515.0 MB disk1s3
4: APFS Volume VM 1.1 GB disk1s4
➜ ~ 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: Apple_APFS Container disk1 211.0 GB disk0s2
3: Microsoft Basic Data OSXRESERVED 8.0 GB disk0s3
4: Microsoft Basic Data BOOTCAMP 31.8 GB disk0s4
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +211.0 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 191.3 GB disk1s1
2: APFS Volume Preboot 20.8 MB disk1s2
3: APFS Volume Recovery 515.0 MB disk1s3
4: APFS Volume VM 2.1 GB disk1s4
/dev/disk3 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: CCCOMA_X64FRE_FR-FR... +5.4 GB disk3
diskutil eraseVolume free null disk0s3 ; diskutil eraseVolume free null disk0s4 ; diskutil ap resizeContainer disk1 0b ;
➜ ~ 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: 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 Macintosh HD 191.3 GB disk1s1
2: APFS Volume Preboot 20.8 MB disk1s2
3: APFS Volume Recovery 515.0 MB disk1s3
4: APFS Volume VM 2.1 GB disk1s4
/dev/disk3 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: CCCOMA_X64FRE_FR-FR... +5.4 GB disk3
Je vais faire court, tu as un disque dur de 251 Go dont 194 Go sont occupés, il reste donc 57 Go, donc c'est mission impossible. Le minimum requis par Assistant Boot Camp sera de 40 Go, or pour fonctionner macOS aura besoin d'un espace libre entre 20/25 Go. Tu peux retourner les chiffres dans tous les sens, ce n'est pas possible. Si tu passes outre et que tu t'entêtes à faire une installation, tu vas au-devant d'un blocage total de ton disque dur au risque de perdre le contenu de macOS.J'espère qu'on va trouver une solution, je me suis demandé si la version de l'ISO pouvait ne pas être stable ... j'attends le retour de Locke
Last login: Tue Mar 31 18:37:41 on ttys000
The default interactive shell is now zsh.
To update your account to use zsh, please run [ICODE]chsh -s /bin/zsh[/ICODE].
For more details, please visit https://support.apple.com/kb/HT208050.
MacBook-Air-de-Maxence-2:~ maxenceautret$ 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_APFS Container disk1 121.1 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +121.1 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD - Données 44.6 GB disk1s1
2: APFS Volume Preboot 84.4 MB disk1s2
3: APFS Volume Recovery 526.6 MB disk1s3
4: APFS Volume VM 2.1 GB disk1s4
5: APFS Volume Macintosh HD 10.8 GB disk1s5
MacBook-Air-de-Maxence-2:~ maxenceautret$ df -H /
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
/dev/disk1s5 121G 11G 63G 15% 484173 1182358307 0% /
MacBook-Air-de-Maxence-2:~ maxenceautret$ sudo find -x / -d 1 -regex '.[I][^\.\].[/I]' -exec sudo du -shx {} +
Password:
31G /Users
1,0G /Applications
0B /opt
4,5K /dev
0B /Volumes
0B /tmp
0B /cores
MacBook-Air-de-Maxence-2:~ maxenceautret$ tmutil listlocalsnapshots /
Snapshots for volume group containing disk /:
MacBook-Air-de-Maxence-2:~ maxenceautret$
Tu m'étonnes ! A la base tu as un tout petit SSD de 121 Go dont 58 Go sont occupés, il reste donc 63 Go et tu te dis que ça roule. Eh bien pas du tout, par défaut Assistant Boot Camp va imposer un minimum de 40 Go pour Windows (on ne peut pas descendre en dessous), en pratique il resterait 23 Go pour macOS. Malheureusement ce n'est suffisant pour que macOS fonctionne correctement, il faut entre 20/30 Go et tu te dis que tu es dans les clous.Problème d'espace insuffisant sur mon disque.
csrutil disable
sudo find -x /System/Volumes/Data -d 1 -regex '.*[^\.\].*' -exec sudo du -shx {} +