Ok, I did step 2 and 3.
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 disk0s3
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 Recovery HD appears to be OK.
File system check exit code is 0.
Checking Core Storage Physical Volume partitions
Verifying storage system
Checking volume
disk0s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
Logical Volume Group
BDA0E341-8F8A-450D-972E-171A448869DA on 1 device
disk0s2: Scan for Metadata Volume
Logical Volume Group has 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 97BCA211-EAF3-49C8-BA01-223C60584337
Load and verify 8FF06E55-0BD9-4A36-878F-FF40186D737A
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 BDA0E341-8F8A-450D-972E-171A448869DA appears to be OK
Storage system check exit code us 0.
The partition map appears to be OK
Operation successful
