MacBook Pro Bug lors de l'instal High Sierra

damartine · 1 Juin 2018

Bonsoir Macomaniac je reviens vers vous car depuis depuis 2 jours mon mac de s'allume plus
quand je fais SOS sur mon disque macinstosh HD il apparaît "le processus SOS a échoué" pourriez vous m'aider ?

damartine · 2 Juin 2018

j'ai réalisé les manip que vous aviez conseillé sur une autre conversation, quand pensez-vous ?

Bloc de code:

-bash-3.2# diskutil list
/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 Macintosh HD            999.3 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 Macintosh HD           +999.0 GB   disk2
                                 Logical Volume on disk0s2
                                 7A0211C7-8BF6-4A0F-8C16-C9071D40F49C
                                 Unencrypted

/dev/disk3 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +5.2 MB     disk3

/dev/disk4 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk4

/dev/disk5 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk5

/dev/disk6 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk6

/dev/disk7 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk7

/dev/disk8 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk8

/dev/disk9 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk9

/dev/disk10 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +12.6 MB    disk10

/dev/disk11 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +4.2 MB     disk11

/dev/disk12 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +1.0 MB     disk12

/dev/disk13 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk13

/dev/disk14 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk14

/dev/disk15 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk15

/dev/disk16 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +1.0 MB     disk16

/dev/disk17 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +6.3 MB     disk17

/dev/disk18 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +6.3 MB     disk18

/dev/disk19 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk19

/dev/disk20 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk20

damartine · 2 Juin 2018

-bash-3.2# diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 72B02EFC-2C40-462C-BD78-152FE2F07CCC
=========================================================
Name: Macintosh HD
Status: Online
Size: 999345127424 B (999.3 GB)
Free Space: 18907136 B (18.9 MB)
|
+-< Physical Volume 89BDA998-E347-452B-8A37-E460D92358C2
| ----------------------------------------------------
| Index: 0
| Disk: disk0s2
| Status: Online
| Size: 999345127424 B (999.3 GB)
|
+-> Logical Volume Family E40BD771-60C3-4763-A1F6-A47315D6C664
----------------------------------------------------------
Encryption Type: None
|
+-> Logical Volume 7A0211C7-8BF6-4A0F-8C16-C9071D40F49C
---------------------------------------------------
Disk: disk2
Status: Online
Size (Total): 998973898752 B (999.0 GB)
Revertible: Yes (no decryption required)
LV Name: Macintosh HD
Volume Name: Macintosh HD
Content Hint: Apple_HFS
-bash-3.2#

damartine · 2 Juin 2018

et enfin les manip avec "ls volumes/ "Macinstosh HD" voila ce qui apparait :

Bloc de code:

-bash-3.2# ls /Volumes/"Macintosh HD"
ls: /Volumes/Macintosh HD: No such file or directory
-bash-3.2# diskutil info /Volumes/"Macintosh HD"
Could not find disk: /Volumes/Macintosh HD
-bash-3.2# diskutil repairVolume /Volumes/"Macinstosh HD"
Unable to find disk for /Volumes/Macinstosh HD
-bash-3.2#

Membre supprimé 1060554 · 2 Juin 2018

Bonjour damartine

Le volume Macintosh HD est l'hôte terminal d'un système stockage CoreStorage non chiffré (FileVault n'est pas activé).

Tu peux te représenter les choses ainsi : la partition principale du disque (disk0s2) > exporte un espace-disque virtuel appelé Logical Volume > et le volume standard Macintosh HD utilise cet espace-disque virtuel comme espace de montage -->

Bloc de code:

/dev/disk2 (internal, virtual):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           +999.0 GB   disk2
                                 Logical Volume on disk0s2
                                 7A0211C7-8BF6-4A0F-8C16-C9071D40F49C
                                 Unencrypted

manifestement : l'espace-disque virtuel du Logical Volume est bien exporté depuis la partition principale du disque > puisqu'il se trouve indexé en tant que disque virtuel disk2. Mais si le volume Macintosh HD n'est pas trouvé par les commandes que tu lui as adressées -->

Bloc de code:

Could not find disk: /Volumes/Macintosh HD

c'est parce que ledit volume Macintosh HD n'est pas monté > sur l'espace virtuel du Logical Volume.

S'il n'est pas monté automatiquement > ce doit être parce que le système de fichiers jhfs+ (= Mac OS étendu journalisé) > qui est la structure logicielle génératrice de ce volume > est corrompu. Càd. affecté d'erreurs graves qui bloquent le déploiement du volume.

Afin de vérifier cette conjecture > passe la commande :

Bloc de code:

diskutil verifyVolume disk2

la commande vérifie le système de fichiers jhfs+ ancré sur l'en-tête du Logical Volume

Poste l'affichage retourné par la commande.

damartine · 2 Juin 2018

Bonjour j'ai passé la commande diskutil verifyVolume disk2
voila ce qui apparaît
-bash-3.2# diskutil verifyVolume disk2

Started file system verification on disk2 Macintosh HD

Verifying storage system

Performing fsck_cs -n -x --lv --uuid 72B02EFC-2C40-462C-BD78-152FE2F07CCC

Checking volume

disk0s2: Scan for Volume Headers

disk0s2: Scan for Disk Labels

Logical Volume Group 72B02EFC-2C40-462C-BD78-152FE2F07CCC on 1 device

disk0s2: 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

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 1 Logical Volume

Load and verify E40BD771-60C3-4763-A1F6-A47315D6C664

Load and verify 7A0211C7-8BF6-4A0F-8C16-C9071D40F49C

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Live Virtual Addresses

Newest transaction commit checkpoint is valid

Load and verify Segment Cleaning

The volume 72B02EFC-2C40-462C-BD78-152FE2F07CCC appears to be OK

Storage system check exit code is 0

Verifying file system

Volume is already unmounted

Performing fsck_hfs -fn -x /dev/rdisk2

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog file

The volume Macintosh HD could not be verified completely

File system check exit code is 8

Restoring the original state found as unmounted

Error: -69845: File system verify or repair failed

Underlying error: 8: Exec format error

-bash-3.2#

damartine · 2 Juin 2018

Bloc de code:

-bash-3.2# diskutil verifyVolume disk2
Started file system verification on disk2 Macintosh HD
Verifying storage system
Performing fsck_cs -n -x --lv --uuid 72B02EFC-2C40-462C-BD78-152FE2F07CCC
Checking volume
disk0s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
Logical Volume Group 72B02EFC-2C40-462C-BD78-152FE2F07CCC on 1 device
disk0s2: 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
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 1 Logical Volume
Load and verify E40BD771-60C3-4763-A1F6-A47315D6C664
Load and verify 7A0211C7-8BF6-4A0F-8C16-C9071D40F49C
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 72B02EFC-2C40-462C-BD78-152FE2F07CCC appears to be OK
Storage system check exit code is 0
Verifying file system
Volume is already unmounted
Performing fsck_hfs -fn -x /dev/rdisk2
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
The volume Macintosh HD could not be verified completely
File system check exit code is 8
Restoring the original state found as unmounted
Error: -69845: File system verify or repair failed
Underlying error: 8: Exec format error
-bash-3.2#

MacBook Pro Bug lors de l'instal High Sierra

damartine

Membre confirmé

damartine

Membre confirmé

damartine

Membre confirmé

damartine

Membre confirmé

Membre supprimé 1060554

Invité

damartine

Membre confirmé

damartine

Membre confirmé

Sujets similaires