Disk utility detecting error in single user mode, but not when disk utility is opened via recovery mode

Question

I verified the integrity of my Macintosh HD (MacBook Pro 13" 2012, OS X Yosemite) with Disk Utility when I was logged in as a user and it reported this problem:

Invalid volume free block count
...
Error: This disk needs to be repaired

Then a window popped open and said that I had to repair the disk with the Disk Utility in Recovery Mode (cmd+R immediately after restarting the Mac). But when I do this, it doesn't find an error, so when you press the 'repair disk' and you check the disk in single mode once again, the error isn't changed.

Update: What I see, when I open User Single Mode:

Update 2: The solution worked, disk utility also doesn't generate an error anymore:

Answer 1

Here's a beginner's guide to the command line. The single user mode is also like looking in as root - the first user that owns all of the computer historically from a unix perspective.

the $ indicates a prompt where you, the human user can type commands. The system is telling you how to prepare the drive for running the repair command.

Type the following text - the same as the first line you are told to from the screen:

/usr/sbin/fsck -fy

Note, that every space, every punctuation is exact and changing any one item may run an entirely different command. If the fsck command has any errors, you can and should run it again with the same command up to three times in a row or more in some rare cases.

To get out of that screen, you could halt the Mac or type exit to resume the normal start up process.

Apple documents the root user and fsck in these two articles if you are curious or wish to learn more:

• https://support.apple.com/en-us/HT204012 - About the root user
• https://support.apple.com/en-us/HT201639 - Using Disk Utility and fsck
• https://support.apple.com/kb/PH21893 - Single user mode in El Capitan

Answer 2

It looks like your OS is not the same version as the Recovery partition, so you have to repair the disk manually.

Try this:

• Power on your Mac and boot into Single User Mode by pressing and holding cmdS until you see a black screen with status messages.
• When in Single User Mode, check your disk:

This should show you the errors you saw before.
# /sbin/fsck -fy
Remount your harddisk in read-write mode:
# /sbin/mount -uw /
Repair the filesystem.
# /sbin/fsck -fy

The error should now be gone.