Verify and Repair Disk Permissions via Terminal (Mac OS X)
Verify Permissions
diskutil verifyPermissions /
Repair Permissions
diskutil repairPermissions /
If unable to unmount drive on Mac
You can try booting from OS X recovery by holding CMD + R at the time of startup. Once booted from OS X recovery, select Terminal from the utilities and then at the unix prompt enter:
diskutil list
then press return and look for the disk identifier and enter the following command with the disk identifier:
sudo diskutil unmountDisk /dev/(enter here disk identifier name)
Press return and enter your admin password if prompted. This should unmount all volumes of the physical drive.
If still the above method didn't work, then the last option is to force the entire disk to unmount.
For that using the terminal application again, enter the following command: sudo diskutil unmount force /dev/(enter here disk identifier name)
Then press return and enter the admin password if prompted. This will definetely unmount the entire disk and all its related volume.
diskutil repairVolume disk3
-bash-3.2# diskutil mount readonly disk3
disk3 is a CoreStorage Logical Volume which failed to mount
-bash-3.2# diskutil repairVolume disk3
Started file system repair on disk3 Macintosh HD
Verifying storage system
Checking volume
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 9E0AD0CC-5135-4792-8F30-C1CA890F044E spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 378 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
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 18 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 735A0A00-BB97-4ED1-B479-3E2F62DABD1D
Load and verify 8DFCD068-1865-43E3-8856-CBC599318973
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 9E0AD0CC-5135-4792-8F30-C1CA890F044E appears to be OK
Storage system check exit code is 0
Repairing file system
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
The volume Macintosh HD appears to be OK
File system check exit code is 0
Checking for overcommitted space in Logical Volume Group
Finished file system repair on disk3 Macintosh HD
mount -t hfs -r /dev/disk3 /tmp
-bash-3.2#
ls /tmp
mount hfs: error on mount(): error = -1
mount hfs: Invalid argument
diskutil umount disk4
mount -t hfs -r /dev/disk4 /tmp
ls /tmp
On a créé un disque de boot externe afin de voir si on pouvait récupérer les données internes
le disque dur mécanique est bien là présent mais aucun 'cable' ne le relie avec mon disque SSD. On n'arrive pas à 'cabler' par une commande 'mount' les deux disques.
iMac-de-Olivier:~ olivierfabre$ diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 9E0AD0CC-5135-4792-8F30-C1CA890F044E
=========================================================
Name: Macintosh HD
Status: Online
Size: 3120722075648 B (3.1 TB)
Free Space: 4136345600 B (4.1 GB)
|
+-< Physical Volume C7F6CB04-EE67-451F-9BDE-64ABBA692C97
| ----------------------------------------------------
| Index: 0
| Disk: disk1s2
| Status: Online
| Size: 120988852224 B (121.0 GB)
|
+-< Physical Volume 47E9BD0F-211C-4CE2-B9C0-DA10CF992D0C
| ----------------------------------------------------
| Index: 1
| Disk: disk0s2
| Status: Online
| Size: 2999733223424 B (3.0 TB)
|
+-> Logical Volume Family 735A0A00-BB97-4ED1-B479-3E2F62DABD1D
----------------------------------------------------------
Encryption Type: None
|
+-> Logical Volume 8DFCD068-1865-43E3-8856-CBC599318973
---------------------------------------------------
Disk: disk2
Status: Online
Size (Total): 3115223613440 B (3.1 TB)
Revertible: No
LV Name: Macintosh HD
Volume Name: Macintosh HD
Content Hint: Apple_HFS
LVG Type: Sparse
3: Apple_Boot Boot OS X 134.2 MB disk0s3
3: Apple_Boot Recovery HD 650.0 MB disk1s3
Data Rescue voit après analyse rapide, toute mes fichiers et dossiers dans Machintosh HD comme si j'y accédais directement.
Apparement je peux récupérer tous mes fichiers...
j ai 3To de données à récupérer, ça va prendre des lustres surtout que je n'ai qu'un disque dur de 250 Go
même Apple ne peut rien faire alors qu'un programme Rescue arrive à accéder à mon disque