Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Issue with repairing SSD with Disk Utility

C

Clown

macrumors member
Original poster
Feb 8, 2011
31
3
Hello guys!

I have MacBook Pro Mid 2009, "15, 2.8 Duo Core with Kingston SSDNow v300 240GB SSD.
I ran a verify task with Apple built-in Disk Utility and got a message tell me that my SSD needs to get repaired using Recovery HD (command + R after restart).
So, I did so - I entered to the Disk Utility menu after restarting my MacBook Pro, run a verify task, and guess what? It said that everything looks cool and I don't need to run a repair.
So I restarted back to my SSD Macintosh HD, ran again a task with Disk Utility and is still says that I need to repair my SSD again.

This is the error I get:
Verifying file system.
Using live mode.
Performing live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking volume bitmap.
Volume bitmap needs minor repair for orphaned blocks
Checking volume information.
Invalid volume free block count
(It should be 43976949 instead of 43971524)
The volume Macintosh HD was found corrupt and needs to be repaired.
File system check exit code is 8.
Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
Click to expand...
I use Trim Enabler app. I thought this may be the reason for this error.
So I deleted it, enabled back kext singing.
It didn't help...

What can I do? :confused:
 
Clown said:
Hello guys!

I have MacBook Pro Mid 2009, "15, 2.8 Duo Core with Kingston SSDNow v300 240GB SSD.
I ran a verify task with Apple built-in Disk Utility and got a message tell me that my SSD needs to get repaired using Recovery HD (command + R after restart).
So, I did so - I entered to the Disk Utility menu after restarting my MacBook Pro, run a verify task, and guess what? It said that everything looks cool and I don't need to run a repair.
So I restarted back to my SSD Macintosh HD, ran again a task with Disk Utility and is still says that I need to repair my SSD again.

This is the error I get:

I use Trim Enabler app. I thought this may be the reason for this error.
So I deleted it, enabled back kext singing.
It didn't help...

What can I do? :confused:
Click to expand...
Look up the Kingston v300 bait-and-switch to using slower and cheaper NAND: http://www.anandtech.com/show/7763/an-update-to-kingston-ssdnow-v300-a-switch-to-slower-micron-nand and http://www.extremetech.com/extreme/...itching-cheaper-components-after-good-reviews

Trash it and get a decent SSD from a more reputable brand like Crucial.
 
Clown said:
My bad. OS X Yosemite 10.10.4.
Click to expand...

10.10.4 has newly enabled Trim support for third party SSDs. Try ...

sudo trimforce enable

in Terminal and see if the errors persist. It probably won't fix the issue but it's worth a try.
 
Dark Void said:
10.10.4 has newly enabled Trim support for third party SSDs. Try ...

sudo trimforce enable

in Terminal and see if the errors persist. It probably won't fix the issue but it's worth a try.
Click to expand...
Okay, I did so and now my MBP won't load my SSD.
When it did a restart after applying this command, I see Grey not sign-in symbol.
How can I disable this command?
 
Clown said:
Okay, I did so and now my MBP won't load my SSD.
When it did a restart after applying this command, I see Grey not sign-in symbol.
How can I disable this command?
Click to expand...

Same command, just type disable instead of enable.
 
Likely your only choice now is to reinstall OS X. That will reset the kext settings that you probably forgot before you removed the trim enabler app.
This is one of those times when you will be glad that you created a bootable USB stick with your current OS X installer...
If your MBPro was newer (2010 or later), you would be able to boot to Apple's servers, and use Internet Recovery to reinstall. Your's is too old for that.
 
Dark Void said:
I'm not sure what you're referring to. What happens when you let the computer boot up? In any case, this thread on TrimForce may help.
Click to expand...
Thank you so much! It actually worked for me.

Can you please tell me what should I check before doing again trimforce, without make
any damage?

DeltaMac said:
Likely your only choice now is to reinstall OS X. That will reset the kext settings that you probably forgot before you removed the trim enabler app.
This is one of those times when you will be glad that you created a bootable USB stick with your current OS X installer...
If your MBPro was newer (2010 or later), you would be able to boot to Apple's servers, and use Internet Recovery to reinstall. Your's is too old for that.
Click to expand...
I guess I don't have to. :cool:
 
Do you happen to have FileVault encryption turned on? I have seen this error before and to fix it you need to turn off FileVault and wait for it to unencrypt, then use DU from recovery to make the repair.
 
Dark Void said:
You're welcome, glad you got it sorted. Cheers.
Click to expand...
Can you please tell me what should I check before doing again trimforce, without make
any damage?

Weaselboy said:
Do you happen to have FileVault encryption turned on? I have seen this error before and to fix it you need to turn off FileVault and wait for it to unencrypt, then use DU from recovery to make the repair.
Click to expand...
I do have FileVault encryption enabled on my OS X.
I will try it later and will let you know if it worked.
 
  • Like
Reactions: Weaselboy
Clown said:
Can you please tell me what should I check before doing again trimforce, without make any damage?
Click to expand...

I've only tried it and had no issues myself, so I wouldn't really be able to. That thread that I linked seems to be a really good information source for this new feature - so beyond reiterating anything stated in there, I wouldn't have anything different to say. It's all new and still in sort of a "testing" phase.
 
Weaselboy said:
Do you happen to have FileVault encryption turned on? I have seen this error before and to fix it you need to turn off FileVault and wait for it to unencrypt, then use DU from recovery to make the repair.
Click to expand...

Actually, you don't need to goto all that trouble! You just need to provide the decryption password to the recovery utilities. They don't have access to the decryption password.

When you get into the recovery tools Disk Utility select the drive on your Mac, choose mount and it will ask for the password to decrypt it. Once you do that you can run the normal repair disk. Thus no need to wait hours to disable and then reenable FileVault.
 
TheIguana said:
Actually, you don't need to goto all that trouble! You just need to provide the decryption password to the recovery utilities. They don't have access to the decryption password.

When you get into the recovery tools Disk Utility select the drive on your Mac, choose mount and it will ask for the password to decrypt it. Once you do that you can run the normal repair disk. Thus no need to wait hours to disable and then reenable FileVault.
Click to expand...
When this happened to me, just mounting and unlocking did not do the trick. I ended having to unencrypt. Sure worth a try though.
 
TheIguana said:
Actually, you don't need to goto all that trouble! You just need to provide the decryption password to the recovery utilities. They don't have access to the decryption password.

When you get into the recovery tools Disk Utility select the drive on your Mac, choose mount and it will ask for the password to decrypt it. Once you do that you can run the normal repair disk. Thus no need to wait hours to disable and then reenable FileVault.
Click to expand...

Weaselboy said:
When this happened to me, just mounting and unlocking did not do the trick. I ended having to unencrypt. Sure worth a try though.
Click to expand...
I have started already the decryption proccess, and it seems like it going to take hours.
Any ways to disable the proccess? I want to give a try to TheIguana method.
 
Clown said:
I have started already the decryption proccess, and it seems like it going to take hours.
Any ways to disable the proccess? I want to give a try to TheIguana method.
Click to expand...

Once it has begun, you are committed. Stopping it could lead to data loss. Sorry bud.
 
  • Like
Reactions: Weaselboy
TheIguana said:
Actually, you don't need to goto all that trouble! You just need to provide the decryption password to the recovery utilities. They don't have access to the decryption password.

When you get into the recovery tools Disk Utility select the drive on your Mac, choose mount and it will ask for the password to decrypt it. Once you do that you can run the normal repair disk. Thus no need to wait hours to disable and then reenable FileVault.
Click to expand...

Weaselboy said:
When this happened to me, just mounting and unlocking did not do the trick. I ended having to unencrypt. Sure worth a try though.
Click to expand...
TheIguana method actually worked!
The decryption process took too long so I shot down the machine.
Got into recovery mode, unlocked the encrypted SSD, ran a verify
check and it did find the errors and ask me to fix them.

I want to thank all of you for commend and help!
Have a nice week.
 
  • Like
Reactions: Weaselboy
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back