OS Catalina Boot Camp impossible !

[Membre supprimé 1060554]

Tout m'a l'air en ordre -->

- veux-tu qu'on fasse un test de repartitionnement (destiné à prouver que ça marchera ensuite avec l'Assistant BootCamp) ?​

 

[poussmouss]

Allez, on y va pour un p'tit test... Ensuite j'essayerai l'install...

 

[Membre supprimé 1060554]

Passe la commande :

diskutil ap resizeContainer disk2 1800g fat32 BOOTCAMP 0b ; diskutil list internal

• la commande rétrécit le Conteneur apfs à 1,8 To et crée une partition indépendante de 300 Go (volume BOOTCAMP > format FAT-32) > puis affiche la configuration interne. Ça peut mettre du temps avec toutes tes données.

Poste le retour complet.

 

[poussmouss]

Et Voilà !!!

Last login: Sun Nov  3 11:16:09 on ttys004
fred@imac-5k-de-fred ~ % diskutil ap resizeContainer disk2 1800g fat32 BOOTCAMP 0b ; diskutil list internal
Started APFS operation
Aligning shrink delta to 321 207 386 112 bytes and targeting a new physical store size of 1 678 981 791 744 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 1 411 232 301 056 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk1s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /dev/disk0s2
Checking the container superblock
Checking the fusion superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking the Fusion data structures
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD - Données was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Recovery was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume VM was formatted by apfs.util (1412.11.7) and last modified by apfs_kext (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Verifying allocated space
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk1s2 from 2 000 189 177 856 to 1 678 981 791 744 bytes
Shrinking APFS data structures
Shrinking partition
Modifying partition map
4096 bytes per physical sector
/dev/rdisk1s3: 627204480 sectors in 9800070 FAT32 clusters (32768 bytes/cluster)
bps=512 spc=64 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=3279671296 drv=0x80 bsec=627357696 bspf=76568 rdcl=2 infs=1 bkbs=6
Mounting disk
1 new disk created or changed due to APFS operation
Disk from APFS operation: disk1s3
Finished APFS operation
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk2         121.0 GB   disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         1.7 TB     disk1s2
   3:       Microsoft Basic Data BOOTCAMP                321.2 GB   disk1s3

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.8 TB     disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD - Données  1.4 TB     disk2s1
   2:                APFS Volume Macintosh HD            10.9 GB    disk2s2
   3:                APFS Volume Preboot                 81.1 MB    disk2s3
   4:                APFS Volume Recovery                528.5 MB   disk2s4
   5:                APFS Volume VM                      22.5 GB    disk2s5

fred@imac-5k-de-fred ~ %

le BOOTCAMP est bien là !!!

 

[Membre supprimé 1060554]

Oui : ça fonctionne. Passe la commande :

diskutil eraseVolume free null disk1s3 ; diskutil ap resizeContainer disk2 0b ; diskutil list internal

• qui : supprime la partition BOOTCAMP > récupère son espace au Conteneur apfs > affiche la configuration interne

Poste le retour.

 

[poussmouss]

Et Voilà :

fred@imac-5k-de-fred ~ % diskutil eraseVolume free null disk1s3 ; diskutil ap resizeContainer disk2 0b ; diskutil list internal
Started erase on disk1s3 BOOTCAMP
Unmounting disk
Finished erase on disk1
Started APFS operation
Aligning grow delta to 321 207 386 112 bytes and targeting a new physical store size of 2 000 189 177 856 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 2 000 188 149 760 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk1s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /dev/disk0s2
Checking the container superblock
Checking the fusion superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking the Fusion data structures
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD - Données was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Recovery was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume VM was formatted by apfs.util (1412.11.7) and last modified by apfs_kext (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Verifying allocated space
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Growing APFS Physical Store disk1s2 from 1 678 981 791 744 to 2 000 189 177 856 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk2         121.0 GB   disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         2.0 TB     disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +2.1 TB     disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD - Données  1.4 TB     disk2s1
   2:                APFS Volume Macintosh HD            10.9 GB    disk2s2
   3:                APFS Volume Preboot                 81.1 MB    disk2s3
   4:                APFS Volume Recovery                528.5 MB   disk2s4
   5:                APFS Volume VM                      22.5 GB    disk2s5

fred@imac-5k-de-fred ~ %

 

[Membre supprimé 1060554]

Tout fonctionne sans anicroche - à l'aller comme au retour (partitionnement / départitionnement).

- tu n'auras pas effectué toutes tes tribulations pour rien.​

Tu n'as qu'à te lancer dans l'opération BOOTCAMP.

 

[poussmouss]

Ok j'essaye !

Bon le problème s'est décalé ; L'assistant BootCamp formate bien le disque, et tout ce passe bien jusqu'au début de l'installation de windows. J'ai ce message d'erreur :

 

[Membre supprimé 1060554]

Là > je vais passer le relais à Locke qui a l'expérience des installations de Windows (moi aucune).

 

[poussmouss]

Last login: Sun Nov  3 18:30:53 on console
fred@imac-5k-de-fred ~ % diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk2         121.0 GB   disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         1.6 TB     disk1s2
   3:       Microsoft Basic Data BOOTCAMP                371.2 GB   disk1s4

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.7 TB     disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD - Données  1.3 TB     disk2s1
   2:                APFS Volume Macintosh HD            10.9 GB    disk2s2
   3:                APFS Volume Preboot                 81.1 MB    disk2s3
   4:                APFS Volume Recovery                528.5 MB   disk2s4
   5:                APFS Volume VM                      21.5 GB    disk2s5

fred@imac-5k-de-fred ~ %

Par contre j'avais demander 250Go il me l'a fait à 371,2Go ???

 

[poussmouss]

@macomaniac Un grand merci à toi en tout cas !!!

 

[Membre supprimé 1060554]

Si tu as des problèmes de partitions => je reviendrai aider.

 

[poussmouss]

@Locke une idée pour continuer ???

 

[Locke]

@Locke une idée pour continuer ???

N'ayant pas de Mac avec une option de disque dur en FusionDrive, je vais être dans l'incapacité de te venir en aide. Pour moi, le problème est lié avec un fichier d'installation (encadré en rouge), mais je ne comprends pas pourquoi il y a un tel problème récurrent avec tous les Mac en option FusionDrive !

Apple mentionne pourtant un réel problème avec les Mac mini et iMac en FusionDrive... https://support.apple.com/fr-fr/HT209149 ...par le biais d'une mise à jour...



...mais sans donner plus d'informations.