Keep having to repair disk. Second time today.

[vbman213]

Verifying volume “Macintosh HD”
Performing live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Missing thread record (id = 1399529)
Incorrect number of thread records
Invalid volume directory count
(It should be 130143 instead of 130144)
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Macintosh HD was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.

So today I was going to run Onyx. I run it every Sunday morning.

And the volume test failed. So I check the exact cause in disk utility (posted above).

I run TechTools Pro 5 and check my hard drive. Everything passed. My computer is functioning just like it did before this started. Just as fast. No weird HDD noises. etc.

So Now I'm getting ready to repair for a second time! It is advising me again... I checked it again just to make sure nothing was wrong, and to my shock, something is wrong again. And it is the same warnings again.

 

[Bill Gates]

It happened to me once before on my old MacBook Pro that I had to run Disk Utility twice before my hard drive was error-free. Run Disk Utility continuously until it shows no errors, then see if this problem continues.

 

[vbman213]

It happened to me once before on my old MacBook Pro that I had to run Disk Utility twice before my hard drive was error-free. Run Disk Utility continuously until it shows no errors, then see if this problem continues.

Well so far so good...

The only thing I remember doing between the two repairs is I ran CleanMyMac. Not sure if this was the cause, but the timing fits.

 

[vbman213]

When I woke up this morning I checked it. It appears to be "OK".

I've been checking it every hour today.

If this was a single incident, what could cause something like this?

Also, FWIW. Here is my SMART status.

 

[Bill Gates]

I'd be surprised if you saw this problem happen again. Typically something like this is caused by the computer/drive being powered off before the drive has had a chance to finish making queued modifications to the file system. The SMART results look fine although I don't find them to be particularly useful to begin with unless a parameter is way out of spec. I don't think you need to do any further checks of the file system.