Al momento sto soffrendo con il mio HDD da 6 TB appena comprato.
L'ho espulso in modo sicuro ieri e quando l'ho collegato di nuovo, non è successo niente. Ho quindi controllato DiskUtility ma mi è stata presentata una cosa strana: 
Poiché quasi tutto ciò che è importante per me risiede su questa unità ora, non so davvero se potrei riprendermi da questa perdita.
Sono su 10.12.5, in esecuzione su un MacBook Pro in ritardo '13, se questo è anche importante. Ok, ho cercato alcune cose dopo:
Output di 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_CoreStorage Macintosh HD 222.1 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Microsoft Basic Data BOOTCAMP 28.0 GB disk0s4
/dev/disk1 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Macintosh HD +221.8 GB disk1
Logical Volume on disk0s2
D1E19399-BC6F-4E9F-ADA5-D082A16EC2A3
Unlocked Encrypted
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *6.0 TB disk2
1: EFI EFI 314.6 MB disk2s1
2: Apple_CoreStorage MC-7 6.0 TB disk2s2
3: Apple_Boot Boot OS X 134.2 MB disk2s3
Output di diskutil cs list :
CoreStorage logical volume groups (2 found)
|
+-- Logical Volume Group E7AF9022-948A-415E-9B5E-F288DD70F8E5
| =========================================================
| Name: Macintosh HD
| Status: Online
| Size: 222140432384 B (222.1 GB)
| Free Space: 0 B (0 B)
| |
| +-< Physical Volume 02D8A677-06DE-41ED-B936-DB70E2FE3656
| | ----------------------------------------------------
| | Index: 0
| | Disk: disk0s2
| | Status: Online
| | Size: 222140432384 B (222.1 GB)
| |
| +-> Logical Volume Family 5FFE6896-66C8-4E27-9B47-75900D365736
| ----------------------------------------------------------
| Encryption Type: AES-XTS
| Encryption Status: Unlocked
| Conversion Status: Complete
| High Level Queries: Fully Secure
| | Passphrase Required
| | Accepts New Users
| | Has Visible Users
| | Has Volume Key
| |
| +-> Logical Volume D1E19399-BC6F-4E9F-ADA5-D082A16EC2A3
| ---------------------------------------------------
| Disk: disk1
| Status: Online
| Size (Total): 221803835392 B (221.8 GB)
| Revertible: No
| LV Name: Macintosh HD
| Volume Name: Macintosh HD
| Content Hint: Apple_HFS
|
+-- Logical Volume Group 20344557-B1E9-4CEE-8472-28FA39379F4C
=========================================================
Name: MC-7
Status: Offline
Size: 0 B (0 B)
Free Space: -none-
|
+-< Physical Volume 4F2A854E-9B63-49EC-A47D-14FBD768C226
----------------------------------------------------
Index: 0
Disk: disk2s2
Status: Checking
Size: 6000726290432 B (6.0 TB)
Output di diskutil repairdisk disk2 :
Started partition map repair on disk2
Checking prerequisites
Checking the partition list
Adjusting partition map to fit whole disk as required
Checking for an EFI system partition
Checking the EFI system partition's size
Checking the EFI system partition's file system
Checking the EFI system partition's folder content
Checking all HFS data partition loader spaces
Checking booter partitions
Checking booter partition disk2s3
Verifying 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 Boot OS X appears to be OK
File system check exit code is 0
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
Verifying storage system
Checking volume
disk2s2: Scan for Volume Headers
disk2s2: Scan for Disk Labels
Invalid Disk Label @ 4096: invalid field value
Invalid Disk Label @ 4198400: invalid field value
Logical Volume Group 20344557-B1E9-4CEE-8472-28FA39379F4C on 1 device
disk2s2: 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
Unable to bootstrap transaction group 5: cksum mismatch
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Unable to bootstrap transaction group 4: cksum mismatch
No valid commit checkpoint found
The volume 20344557-B1E9-4CEE-8472-28FA39379F4C was found corrupt and needs to be repaired
Storage system check exit code is 1
Repairing storage system
Checking volume
disk2s2: Scan for Volume Headers
disk2s2: Scan for Disk Labels
Invalid Disk Label @ 4096: invalid field value
Invalid Disk Label @ 4198400: invalid field value
Logical Volume Group 20344557-B1E9-4CEE-8472-28FA39379F4C on 1 device
disk2s2: 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
Unable to bootstrap transaction group 5: cksum mismatch
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Unable to bootstrap transaction group 4: cksum mismatch
No valid commit checkpoint found
The volume 20344557-B1E9-4CEE-8472-28FA39379F4C was found corrupt and can not be repaired
Storage system check exit code is 1
Repairing storage system
The volume disk2s2+disk0s2 cannot be repaired when it is in use
Checking volume
disk2s2: Scan for Volume Headers
disk0s2: Scan for Volume Headers
disk2s2: Scan for Disk Labels
Invalid Disk Label @ 4096: invalid field value
Invalid Disk Label @ 4198400: invalid field value
disk0s2: Scan for Disk Labels
Logical Volume Group E7AF9022-948A-415E-9B5E-F288DD70F8E5 on 1 device
Incomplete or inconsistent CoreStorage Physical Volume set
Storage system check exit code is 1
Problems were encountered during repair of the partition map
Error: -69716: Storage system verify or repair failed
Underlying error: 1: Operation not permitted
Output di sudo gpt -r show disk2 :
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 76800 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
76806 1465021067 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
1465097873 32768 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
1465130641 4 Sec GPT table
1465130645 1 Sec GPT header
Dice Invalid Disk Label @ #: invalid field value , questo è il primo errore che posso individuare. Ho provato anche fsck_hfs , ma ho ottenuto più o meno gli stessi risultati.
Sono piuttosto depresso, non so più cosa fare ...
Modifica : l'unità in questione è effettivamente crittografata.
Modifica 2 : sono stato in grado di recuperare parti di alcuni file importanti (~ 1 GB di ~ 250 GB) utilizzando uno strumento di ripristino (in particolare "Data Rescue 4") su un'unità che aveva i file prima che li spostassi. Immagino che valga la pena provare questo problema, anche se non otterrai molti risultati (ma almeno alcuni). Grazie per l'aiuto però. Sto lasciando l'unità così com'è nel caso qualcuno dovesse trovare una soluzione.