10.13 High Sierra Session ne s'ouvre pas
- Créateur du sujet SwedenOff
- Date de début
M
Membre supprimé 1060554
Invité
Une question (et je vais arrêter pour ce soir car il se fait tard) -->
- quand tu as utilisé l'Assistant de migration à la fin de l'installation dans Clone => est-ce que tu as choisi le volume Macintosh HD - Données en source ou Macintosh HD ?
M
Membre supprimé 1060554
Invité
C'est donc pour ça !
- il faudrait que tu relances l'Assistant de migration (Applications > Utilitaires > Assistant de migration) > et que tu choisisses Macintosh HD - Données en source (ou Macintosh HD si l'autre volume n'est pas disponible). L'Assistant récupérera ton compte et les applications tierces. Si tu as créé un compte avec les mêmes identifiants que dans Macintosh HD - Données => il faudra que tu optes pour un remplacement de ton compte par celui de la source.
Migration terminée ! Cela a mis plus de 8h....
J'avoue ne plus trop comprendre les manip', la session que j'avais créée précédemment est nommée " utilisateurs supprimés " et je ne peux pas accéder aux dossiers
Bloc de code:
MBP-de-Marine:~ marine$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 499.9 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +499.9 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD - Données 89.2 GB disk1s1
2: APFS Volume Preboot 79.2 MB disk1s2
3: APFS Volume Recovery 1.0 GB disk1s3
4: APFS Volume VM 4.3 GB disk1s4
5: APFS Volume Macintosh HD 10.8 GB disk1s5
6: APFS Volume Clone - Données 78.6 GB disk1s6
7: APFS Volume Clone 10.8 GB disk1s7
MBP-de-Marine:~ marine$J'avoue ne plus trop comprendre les manip', la session que j'avais créée précédemment est nommée " utilisateurs supprimés " et je ne peux pas accéder aux dossiers
M
Membre supprimé 1060554
Invité
Tu as bien 78,6 Go dans Clone - Données (au lieu de 8,5 Go) -->
- la session marine que tu ouvres actuellement : est-ce que tu y retrouves toutes tes anciennes données ?
en fait il m'a rétablit exactement la même session qu'avant le dysfonctionnement
M
Membre supprimé 1060554
Invité
C'est ce qui était voulu.
- ta restriction : c'est que tu avais des données dans le compte neuf que tu avais créé > et que tu voudrais récupérer ?
M
Membre supprimé 1060554
Invité
Oui : il faut purger le Conteneur des volumes de l'installation antérieure.
Poste les retours.
- passe les commandes (séparément) :
Bloc de code:
diskutil ap deleteVolume disk1s1
diskutil ap deleteVolume disk1s5- qui suppriment Macintosh HD - Données & Macintosh HD
Poste les retours.
Bloc de code:
MBP-de-Marine:~ marine$ diskutil ap deleteVolume disk1s1
Started APFS operation
Deleting APFS Volume from its APFS Container
Unmounting disk1s1
Erasing any xART session referenced by 1641A504-A4BE-398C-A648-15AEED66C2B7
Deleting Volume
Removing any Preboot and Recovery Directories
Finished APFS operation
MBP-de-Marine:~ marine$ diskutil ap deleteVolume disk1s5
Started APFS operation
Deleting APFS Volume from its APFS Container
Unmounting disk1s5
The volume "Macintosh HD" on disk1s5 couldn't be unmounted because it is in use by process 110 (kextd)
Error: -69888: Couldn't unmount disk
MBP-de-Marine:~ marine$
J'ai réessayé de passer par le Cmd+R, impossible, il essaie de récupérer le système par internet je n'ai pas les 4 utilitaires
M
Membre supprimé 1060554
Invité
Le volume-Données a bien été supprimé. Pas le volume-Système.
Poste les retours => que je voie la situation actuelle dans le Conteneur.
- passe les 2 commandes :
Bloc de code:
diskutil list internal
diskutil ap list- affichant : la configuration interne & un tableau détaillé de l'apfs
Poste les retours => que je voie la situation actuelle dans le Conteneur.
Bloc de code:
Last login: Tue Feb 4 23:52:52 on console
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
MBP-de-Marine:~ marine$ diskutil list internal
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 499.9 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +499.9 GB disk1
Physical Store disk0s2
1: APFS Volume Preboot 53.0 MB disk1s2
2: APFS Volume Recovery 1.0 GB disk1s3
3: APFS Volume VM 4.3 GB disk1s4
4: APFS Volume Macintosh HD 10.8 GB disk1s5
5: APFS Volume Clone - Données 78.9 GB disk1s6
6: APFS Volume Clone 10.8 GB disk1s7
MBP-de-Marine:~ marine$ diskutil ap list
APFS Container (1 found)
|
+-- Container disk1 AC67BFCA-2D24-4FB3-9D17-E9C6A9CA326D
====================================================
APFS Container Reference: disk1
Size (Capacity Ceiling): 499898105856 B (499.9 GB)
Capacity In Use By Volumes: 106258743296 B (106.3 GB) (21.3% used)
Capacity Not Allocated: 393639362560 B (393.6 GB) (78.7% free)
|
+-< Physical Store disk0s2 00004286-186E-0000-5D06-00004C150000
| -----------------------------------------------------------
| APFS Physical Store Disk: disk0s2
| Size: 499898105856 B (499.9 GB)
|
+-> Volume disk1s2 41333630-2C79-4115-8B97-063DCF19AAD3
| ---------------------------------------------------
| APFS Volume Disk (Role): disk1s2 (Preboot)
| Name: Preboot (Case-insensitive)
| Mount Point: Not Mounted
| Capacity Consumed: 53002240 B (53.0 MB)
| FileVault: No
|
+-> Volume disk1s3 7C30753D-25EC-44C7-B790-4CD6844FD3CE
| ---------------------------------------------------
| APFS Volume Disk (Role): disk1s3 (Recovery)
| Name: Recovery (Case-insensitive)
| Mount Point: Not Mounted
| Capacity Consumed: 1048948736 B (1.0 GB)
| FileVault: No
|
+-> Volume disk1s4 AC0CC732-4209-4DDB-9FB7-9CF8E3DF1095
| ---------------------------------------------------
| APFS Volume Disk (Role): disk1s4 (VM)
| Name: VM (Case-insensitive)
| Mount Point: /private/var/vm
| Capacity Consumed: 4296036352 B (4.3 GB)
| FileVault: No
|
+-> Volume disk1s5 BE3331B6-BF8A-45A6-B0FF-9290B2743219
| ---------------------------------------------------
| APFS Volume Disk (Role): disk1s5 (System)
| Name: Macintosh HD (Case-insensitive)
| Mount Point: Not Mounted
| Capacity Consumed: 10828718080 B (10.8 GB)
| FileVault: Yes (Locked)
|
+-> Volume disk1s6 00798827-B892-47B9-9067-5C3651E77EB1
| ---------------------------------------------------
| APFS Volume Disk (Role): disk1s6 (Data)
| Name: Clone - Données (Case-insensitive)
| Mount Point: /System/Volumes/Data
| Capacity Consumed: 78915043328 B (78.9 GB)
| FileVault: No
|
+-> Volume disk1s7 511AF3AC-4CA9-4671-9131-848FA206B5AD
---------------------------------------------------
APFS Volume Disk (Role): disk1s7 (System)
Name: Clone (Case-insensitive)
Mount Point: /
Capacity Consumed: 10829856768 B (10.8 GB)
FileVault: No
MBP-de-Marine:~ marine$
M
Membre supprimé 1060554
Invité
Donc Macintosh HD (ci-devant volume-Système de la précédente installation de Catalina) => est toujours présent > et il est verrouillé par FileVault = non monté).
Poste le retour.
- on va explorer les variantes permettant sa suppression. Passe la commande :
Bloc de code:
diskutil ap deleteVolume disk1s5- scénario : suppression directe du volume tel quel (verrouillé - non monté)
Poste le retour.
Bloc de code:
MBP-de-Marine:~ marine$ diskutil ap deleteVolume disk1s5
Started APFS operation
Deleting APFS Volume from its APFS Container
Unmounting disk1s5
Erasing any xART session referenced by BE3331B6-BF8A-45A6-B0FF-9290B2743219
Deleting Volume
Removing any Preboot and Recovery Directories
Finished APFS operation
MBP-de-Marine:~ marine$
Bloc de code:
MBP-de-Marine:~ marine$ diskutil list internal
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 499.9 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +499.9 GB disk1
Physical Store disk0s2
1: APFS Volume Preboot 26.5 MB disk1s2
2: APFS Volume Recovery 523.5 MB disk1s3
3: APFS Volume VM 4.3 GB disk1s4
4: APFS Volume Clone - Données 78.9 GB disk1s6
5: APFS Volume Clone 10.8 GB disk1s7
MBP-de-Marine:~ marine$ diskutil list internal
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 499.9 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +499.9 GB disk1
Physical Store disk0s2
1: APFS Volume Preboot 26.5 MB disk1s2
2: APFS Volume Recovery 523.5 MB disk1s3
3: APFS Volume VM 4.3 GB disk1s4
4: APFS Volume Clone - Données 78.9 GB disk1s6
5: APFS Volume Clone 10.8 GB disk1s7
M
Membre supprimé 1060554
Invité
Ça a marché : exit le volume Macintosh HD.
Poste les 3 retours.
- on effectue des finitions. Passe les commandes (l'une après l'autre) :
Bloc de code:
diskutil rename disk1s6 "Macintosh HD - Données"
diskutil rename disk1s7 "Macintosh HD"
diskutil list internal- qui renomment : Clone - Données => Macintosh HD - Données & Clone => Macintosh HD ; puis réaffichent la configuration interne
Poste les 3 retours.
Bloc de code:
MBP-de-Marine:~ marine$ diskutil rename disk1s6 "Macintosh HD - Données"
Volume on disk1s6 renamed to Macintosh HD - Données
MBP-de-Marine:~ marine$ diskutil rename disk1s7 "Macintosh HD"
Volume on disk1s7 renamed to Macintosh HD
MBP-de-Marine:~ marine$ diskutil list internal
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 499.9 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +499.9 GB disk1
Physical Store disk0s2
1: APFS Volume Preboot 26.5 MB disk1s2
2: APFS Volume Recovery 523.5 MB disk1s3
3: APFS Volume VM 4.3 GB disk1s4
4: APFS Volume Macintosh HD - Données 79.0 GB disk1s6
5: APFS Volume Macintosh HD 10.8 GB disk1s7
M
Membre supprimé 1060554
Invité
Tout a l'air en ordre.
Poste le retour.
- passe la commande :
Bloc de code:
diskutil verifyVolume disk1- qui vérifie l'apfs
Poste le retour.
Bloc de code:
Last login: Thu Feb 6 20:00:04 on console
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
MBP-de-Marine:~ marine$ diskutil verifyVolume disk1
Started file system verification on disk1
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l /dev/disk0s2
Checking the container superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by hfs_convert (945.275.7) and last modified by apfs_kext (1412.81.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 (945.275.7) and last modified by apfs_kext (1412.81.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 (945.275.7) and last modified by apfs_kext (1412.81.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 - Données was formatted by diskmanagementd (1412.61.1) and last modified by apfs_kext (1412.81.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.81.1) and last modified by apfs_kext (1412.81.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
warning: overallocation detected on Main device: (0x3+3) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x7+2) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xc+3) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x13+5) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x19+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x1c+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x1e+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x20+2) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x25+3) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x2b+3) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x31+11) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x3e+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x42+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x46+2) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x49+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x4b+2) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x53+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x55+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x57+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x59+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x5c+2) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x5f+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x62+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x64+2) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x67+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x69+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x6b+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x6e+9) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x78+10) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x84+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x87+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x8a+2) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x8f+4) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x94+4) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0x9a+11) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xa6+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xa8+2) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xab+5) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xb1+4) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xb6+4) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xbb+9) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xc5+7) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xcd+2) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xd1+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xd3+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xd6+6) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xde+4) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xe3+6) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xee+1) bitmap address (0x42b20)
warning: overallocation detected on Main device: (0xf0+1) bitmap address (0x42b20)
Too many warnings of this type generated; suppressing subsequent ones
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Finished file system verification on disk1
MBP-de-Marine:~ marine$
M
Membre supprimé 1060554
Invité
Tu as une sur-allocation de blocs occupés en ce qui concerne Macintosh HD. Ce qui n'a rien de bloquant. Tout le reste est sans erreur.
Sujets similaires
