Currently Being ModeratedJun 28, 2013 5:38 AM (in response to Rhys.Perrin)
When you say 'work fine for a period' does that mean you have Disk Utility open and are using it for various tasks? Or do you open it once in a while to see how long it takes for it to stop responding?
Currently Being ModeratedJun 28, 2013 4:09 PM (in response to mmollo22)
This certainly helped me, thank you, but I get this impression this merely sidesteps the issue and is not actually a fix.. I'm about to respond to jayv (below) with a more thorough description of what's been happening. Perhaps you could cast your eye over this and let me know any thoughts you may have as to why it's happening as I doubt I'll be able to go into the R-partition every time.
Many thanks in advance!
Currently Being ModeratedJun 28, 2013 4:22 PM (in response to jayv.)
Essentially, if I access the Disk Utility after the MBP has been running for some time, the Disk Utility will stop responding (ie the "neverending pinwheel of death") during the process of trying to gather the HDD information. If, however, I reboot the MBP and immediately open Disk Utility, Disk Utility will find all HDD information without any fuss and I can do whatever I need to do... to a point. I found last night, for example, that I could verify the disk permissions, but I only got half-way through the repair process before it stopped responding again. Better luck the second time around and I actually succeeded in repairing the permissions, but it stopped responding again part-way through a secure erase (I actually succeeded in executing the secure erase thanks to mmollo22's suggestion above). Each time it stops it appears to be for no apparent reason, and given I work a lot with DVD format via Disk Utility, I'm concerned mmollo2's suggestion is not really a fix, but just a sidestep to do some maintenance. Perhaps there's a fix you're aware of, jayv or mmollo22 (or anyone else!!)? Any help greatly appreciated!
Currently Being ModeratedJun 29, 2013 7:54 AM (in response to Linc Davis)
Please find log information pertaining to the most recent instance below. Not many lines, I'm afraid, but perhaps it means something to you? Very keen to hear your thoughts! Many thanks in advance for your assistance.
30/06/13 12:47:59.000 AM kernel: TMCCFS 2229 MSG execveHook skip scan the file(/usr/lib/dyld)
30/06/13 12:47:59.000 AM kernel: TMCCFS 2230 MSG execveHook skip scan the file(/usr/lib/dyld)
30/06/13 12:48:00.000 AM kernel: TMCCFS 2231 MSG fileOpScopeListener exec file:/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Me tadata.framework/Versions/A/Support/mdworker:1
30/06/13 12:48:00.000 AM kernel: TMCCFS 656 MSG handlePutExceptionPids in with 10 apps & 11 pids
Currently Being ModeratedJun 29, 2013 6:37 PM (in response to Linc Davis)
I haven't done what you suggest yet, but I will. Before I do, however, I just wanted to ask a question... Are you suggesting Trend Micro (in my case Trend Micro Titanium Internet Security) is the culprit, or are you thinking that its presence is simply preventing a proper diagnosis of the problem? I'm intrigued!
Currently Being ModeratedJun 29, 2013 6:59 PM (in response to Rhys.Perrin)
Are you suggesting Trend Micro (in my case Trend Micro Titanium Internet Security) is the culprit
I'm suggest two things: that it might be the culprit, and that even if it isn't, you're still a lot better off without it, since it's completely useless for any purpose other than slowing down and destabilizing your computer. It does nothing to protect you from any real security threat. As long as it's installed, your system is unmaintainable. If you're determined to keep it despite all that, you can easily reinstall it.
Currently Being ModeratedJun 29, 2013 11:35 PM (in response to Linc Davis)
I've removed Trend Micro Titanium Internet Security now, but alas, this has not rectified the issue. Please see the log below (there may be a line or two in the below that doesn't relate, but I couldn't be sure so I selected all the lines for roughly the time in question [4:16:00 - 4:16:40).
30/06/13 4:16:00.739 PM AddressBookManager: Validate metadata timed out, cancelling
30/06/13 4:16:01.216 PM mdwrite: [ERROR] [0.000s] com.apple. UBItemStatusNotification.c:805 _do_UBItemStatusNotificationRegisterURLs() can't find realpath for "/Users/rhys1/Library/Mobile Documents/com~apple~system~spotlight/mdlabels", was blocked at "/Users/rhys1/Library/Mobile Documents": 2 (No such file or directory)
30/06/13 4:16:01.216 PM mdwrite: [ERROR] [0.001s] com.apple. UBItemStatusNotification.c:805 _do_UBItemStatusNotificationRegisterURLs() can't find realpath for "/Users/rhys1/Library/Mobile Documents/com~apple~system~spotlight/mdlabels", was blocked at "/Users/rhys1/Library/Mobile Documents": 2 (No such file or directory)
30/06/13 4:16:35.000 PM kernel: Sandbox: sandboxd(932) deny mach-lookup com.apple.coresymbolicationd
30/06/13 4:16:37.899 PM sandboxd: () mdworker(931) deny file-write-owner /Users/rhys1/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.stor edata-wal (import fstype:hfs fsflag:480D000 flags:240000005F diag:0 uti:com.apple.notes.externalrecord plugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t 33796554)
30/06/13 4:16:38.561 PM sandboxd: () mdworker(931) deny file-write-owner /Users/rhys1/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.stor edata-shm (import fstype:hfs fsflag:480D000 flags:240000005F diag:0 uti:com.apple.notes.externalrecord plugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t 33796554)
Any thoughts greatly appreciated.
Perhaps you also have some thoughts on appropriate anti-virus measures too? I suspect your advice may be to be vigilant rather than become complacent by relying on third party apps, which I also suspect to be largely useless?
Currently Being ModeratedJul 1, 2013 6:12 AM (in response to Linc Davis)
I carried out the safe boot procedure as you suggested and appeared to have no issues in the 45-odd minutes I was in this mode. I also carried out a process of resetting PRAM. I then rebooted into normal mode. For the bulk of the past 24-hours there has been no issue... Until now. I have just tried to launch Disk Utilities again, and the issue has returned. This time, the Console log reads as follows:
1/07/13 10:38:05.172 PM WindowServer: CGXDisableUpdate: UI updates were forcibly disabled by application "Disk Utility" for over 1.00 seconds. Server has re-enabled them.
1/07/13 10:38:05.313 PM WindowServer: reenable_update_for_connection: UI updates were finally reenabled by application "Disk Utility" after 1.14 seconds (server forcibly re-enabled them after 1.00 seconds)
Given the reference to Windows Server in the above, I should also highlight out a couple of other points at this stage:
- The Windows Server has been on the network since before the MBP was purchased and has never given any grief other than (maybe) a slow initial connection to the Server via Finder.
- As part of the reboot into normal mode, I elected not to launch the Windows Server Launchpad, so this was NOT running at the time of the latest hang.
- Time Machine has been conducting an excruciatingly long backup since rebooting back into normal mode (looks like it's doing a full backup). Time Machine DOES NOT, however, back up to the Windows Server, but rather to its own dedicated backup drive, which, again, has never presented any issues.
- Since the latest Disk Utility hang, I have noticed a slowing of overall performance (eg opening Safari takes a little longer). This is not to the point of "crazy slow", but rather slower than it has been running all day. I should also say that this slowing of performance is more akin to what I have been used to for some time, and I have to admit I had put the faster performance I've enjoyed for most of the day down to the removal of Trend Micro Titanium Internet Security. Sadly, however, it seems I may have been mistaken on this point.
Linc, once again, any thoughts are greatly appreciated.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points