This is the output upon running First Aid on the disk in Disk Utility:
First Aid found corruption that needs to be repaired. To repair the startup volume, run First Aid from Recovery
Running it in Recovery shows the exact same text :/
diskutil repairVolume yields:
First Aid found corruption that needs to be repaired. To repair the startup volume, run First Aid from Recovery
Checking prerequisites
Checking the partition list
Checking the partition map size
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 disk3s3
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.
Checking Core Storage Physical Volume partitions
Verifying storage system
Checking volume
disk3s2: Scan for Volume Headers
disk3s2: Scan for Disk Labels
Invalid Disk Label @ 4096: invalid field value
Invalid Disk Label @ 4198400: invalid field value
Logical Volume Group 9498CF5F-B356-4C31-91D8-7B4A06AB02C8 on 1 device
disk3s2: 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 9498CF5F-B356-4C31-91D8-7B4A06AB02C8 was found corrupt and needs to be repaired
Storage system check exit code is 1.
Problems were found with the partition map which might prevent booting
Operation successful.
Checking the partition list
Checking the partition map size
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 disk3s3
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.
Checking Core Storage Physical Volume partitions
Verifying storage system
Checking volume
disk3s2: Scan for Volume Headers
disk3s2: Scan for Disk Labels
Invalid Disk Label @ 4096: invalid field value
Invalid Disk Label @ 4198400: invalid field value
Logical Volume Group 9498CF5F-B356-4C31-91D8-7B4A06AB02C8 on 1 device
disk3s2: 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 9498CF5F-B356-4C31-91D8-7B4A06AB02C8 was found corrupt and needs to be repaired
Storage system check exit code is 1.
Problems were found with the partition map which might prevent booting
Operation successful.
Running it in Recovery shows the exact same text :/
diskutil repairVolume yields:
Error starting file system repair for disk3: Invalid request (-69886)
Last edited: