Last login: Tue Jan 23 21:25:11 on ttys000
MacBook-Pro-de-Jamil:~ sos$ 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         129.9 GB   disk0s2
   3:                  Apple_HFS Crucial_SSD_HD          369.8 GB   disk0s3
/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +129.9 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Crucial_SSD_OS          60.9 GB    disk1s1
   2:                APFS Volume Preboot                 19.9 MB    disk1s2
   3:                APFS Volume Recovery                503.9 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk2
   1:                        EFI EFI                     314.6 MB   disk2s1
   2:                  Apple_HFS WD_HD_OSX               55.0 GB    disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3
   4:                  Apple_HFS SOS                     73.8 GB    disk2s4
   5:                 Apple_Boot Recovery HD             650.0 MB   disk2s5
   6:                  Apple_HFS WD_HD_DATA              369.5 GB   disk2s6
MacBook-Pro-de-Jamil:~ sos$ diskutil mountDisk disk1
One or more volume(s) failed to mount
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil verifyDisk disk1
Nonexistent, unknown, or damaged partition map scheme
If you are sure this disk contains a (damaged) APM, MBR, or GPT partition
scheme, you might be able to repair it with "diskutil repairDisk disk1"
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil mount disk1s2
Volume Preboot on disk1s2 mounted
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil mount disk1s3
Volume Recovery on disk1s3 mounted
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil mount disk1s4
Volume VM on disk1s4 mounted
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil mount disk1s1
Volume on disk1s1 failed to mount; it appears to be an APFS Volume which might be locked
Try "diskutil apfs unlockVolume"
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil apfs unlockVolume disk1s1
Passphrase:
Unlocking any cryptographic user on APFS Volume disk1s1
Error unlocking APFS Volume: The given APFS Volume is not encrypted (-69593)
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil mountDisk disk1
One or more volume(s) failed to mount
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil verifyVolume disk1s1
Started file system verification on disk1s1 Crucial_SSD_OS
Verifying file system
Volume is already unmounted
Live mode required because other APFS Volumes in its Container are mounted
Using live mode
Performing fsck_apfs -n -l -x /dev/rdisk1s1
Checking volume
Checking the container superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the object map
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
error: apfs_root: btn: invalid o_oid (0x79503)
fsroot tree is invalid
The volume /dev/rdisk1s1 could not be verified completely
File system check exit code is 0
Restoring the original state found as unmounted
Finished file system verification on disk1s1 Crucial_SSD_OS
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil verifyVolume disk1s2
Started file system verification on disk1s2 Preboot
Verifying file system
Volume was successfully unmounted
Live mode required because other APFS Volumes in its Container are mounted
Using live mode
Performing fsck_apfs -n -l -x /dev/rdisk1s2
Checking volume
Checking the container superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the object map
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
Checking the snapshot metadata tree
Checking the extent ref tree
Checking the snapshots
Verifying allocated space
error: Underallocation Detected on Main device: (1018944+64) bitmap address (440656)
error: Underallocation Detected on Main device: (1019008+64) bitmap address (440656)
error: Underallocation Detected on Main device: (1019072+12) bitmap address (440656)
warning: error (6) getting cib 5 bitmap 2 @ -1 on device 0
warning: error (6) getting cib 5 bitmap 2 @ -1 on device 0
warning: error (6) getting cib 5 bitmap 2 @ -1 on device 0
warning: error (6) getting cib 5 bitmap 2 @ -1 on device 0
warning: error (6) getting cib 5 bitmap 2 @ -1 on device 0
warning: error (6) getting cib 5 bitmap 4 @ 4294967295 on device 0
warning: error (6) getting cib 5 bitmap 4 @ 4294967295 on device 0
warning: error (6) getting cib 5 bitmap 4 @ 4294967295 on device 0
warning: error (6) getting cib 5 bitmap 4 @ 4294967295 on device 0
Space Verification failed
The volume /dev/rdisk1s2 could not be verified completely
File system check exit code is 0
Restoring the original state found as mounted
Finished file system verification on disk1s2 Preboot
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil repairDisk disk1
Nonexistent, unknown, or damaged partition map scheme
If you are sure this disk contains a (damaged) APM, MBR, or GPT partition map,
you can hereby try to repair it enough to be recognized as a map; another
"diskutil repairDisk disk1" might then be necessary for further repairs
Proceed? (y/N) y
Error repairing map: MediaKit reports bad partition or no map found (-5324)
MacBook-Pro-de-Jamil:~ sos$