7 Replies Latest reply: Jan 23, 2013 11:10 PM by ziaulhasan
ziaulhasan Level 1 Level 1 (10 points)

I have started seeing this strange problem that sometimes my Macbook Pro can't write anything/delete anything on the hard drive. Even browser can't open new tabs because it probably needs to write some cache on disk. I get the error below. It seems as if hard drive has been blocked for making changes but I could still read stuff on it. The system gets back to normal when restarted. It has been very annoying lately because it happens very randomly. I am running Mountain Lion latest version.

2013-01-23 11.24.48.jpg


MacBook Pro, OS X Mountain Lion (10.8.2)
  • William Lloyd Level 7 Level 7 (20,980 points)

    What kind of drive is it?  A spinning (mechanical) hard drive?  You may want to run disk utility to check it.

     

    Also, do you have a current backup?  If you don't, you may want to make sure your backups are up to date.

  • ziaulhasan Level 1 Level 1 (10 points)

    Yeah, it is mechanical hard drive. I did run disk utility and it says it fixed it and hard drive appears normal. The problem still persists. It is completely backed up so I am not afraid of loosing data.

  • Linc Davis Level 10 Level 10 (173,555 points)

    The next time you have the problem, note the exact time: hour, minute, second.

     

    If you have more than one user account, these instructions must be carried out as an administrator.

     

    Launch the Console application in any of the following ways:

     

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

     

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

     

    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

     

    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.

     

    Scroll back in the log to the time you noted above. Select any messages timestamped then. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.

    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

    Please do not indiscriminately dump thousands of lines from the log into this discussion.

     

    Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

     

    Also, launch the Terminal application in the same way you launched Console. In the Terminal window, type the word "mount" (without the quotes) and press return. Post any lines of output that appear below what you entered.

  • ziaulhasan Level 1 Level 1 (10 points)

    Thanks...I will wait for it then..

  • Chocolame Level 1 Level 1 (10 points)

    Do you have the hardware test built in to your computer? That would be my next spot along with what Linc has requested above. The disk utility's hard drive test is pretty crappy, its really just checking the OS, the scan it does on the actual drive is really brief.

     

    If you do have the hardware test, I would try that. It would give you a good idea on the hard drive. Start computer up and immediately hold the D key.

     

    http://support.apple.com/kb/HT1509

     

    Also, how long does it take for this to occur? If fairly quick, you could try a safeboot and see if theres some sort of application thats hanging the OS up. Its a stretch but will give us a good idea of where to go from here.

  • Topher Kessler Level 6 Level 6 (9,790 points)

    When the problem happens, are you able to write to any external hard drives attached to the system? If the problem happens regularly, does its prevalence reduce if you boot the system into Safe Mode (hold the Shift key at startup)?

  • ziaulhasan Level 1 Level 1 (10 points)

    Good Idea. I will try that next time it happens. Actually it doesn't happen that frequently so I am not usually prepared. Maybe twice a week. But next time it happens, I will try all these tricks.

    @Chocolame no hardware test built it. but I will try diskwarrior maybe.