PDA

View Full Version : 10.8.2: Randomly Unable to Save to Hard Drive




ObeseSquirrel
Feb 10, 2013, 11:59 AM
I have had this bug intermittently since October, or roughly around the release of the current version of 10.8.2. Sometimes, especially when I have moved my laptop from one location to another, my Mac will lose the ability to save to the hard drive, and I may also lose access to the keychain and the ability to open new apps.

I posted more about this error here, but I have not been able to find an answer, or even other complaints about this:
https://discussions.apple.com/message/20446905#20446905

I've attached a photograph from my Console as well. I had to take a picture because I lose the ability to save to my hard drive, and when I restart my computer, the Console messages are gone. I restarted my computer so that I would know which messages had appeared after I had lost connection to the hard drive.

When I rebooted my computer, everything in the Console starting at 7:04 had disappeared. (So the error began between 7:01 and 7:04.)

Any ideas?



Intell
Feb 10, 2013, 12:01 PM
That looks like a failing hard drive. But it could also be a very odd permissions problem. I suggest backing up your data and reinstalling Mac OS X making sure to wipe the drive before installation.

ObeseSquirrel
Feb 10, 2013, 12:10 PM
That looks like a failing hard drive. But it could also be a very odd permissions problem. I suggest backing up your data and reinstalling Mac OS X making sure to wipe the drive before installation.

I have a Corsair Performance Pro SSD. Disk Utility finds nothing, and I have even tried Terminal "resetpassword" command that can supposedly fix permissions for all files, not just the system files. Earlier, I had reinstalled OSX as well, though it was not a clean install.

Yesterday, I had been watching videos in my apartment unplugged, and the laptop became disconnected when I plugged the laptop back in, and reconnected my Time Machine Drive. (I knew because I had lost my keychain password access to my Time Machine drive.)

It also seems to happen when I bring my laptop to class and there is a wifi problem. (sometimes, because I have lost keychain access, but other times the wifi is just down, and the other Macs in the room are disconnected as well.) Other times, it just happens randomly, but the majority of the time, it seems correlated with connecting to a new wifi network or else to a new external drive.)

The Console seems like one of the few apps that I actually can open after this happens. Sometimes, a particular app will crash, but not always.

Intell
Feb 10, 2013, 12:13 PM
SSD's can still fail in similar ways to a hard drive with bad sectors. The resetpassword command does not reset permissions, it only changes the permissions for the user's folder whose password you're resetting.

ObeseSquirrel
Feb 10, 2013, 12:16 PM
Is there a good way to test my SSD for bad sectors without resorting to a clean install?

50548
Feb 10, 2013, 02:42 PM
Is there a good way to test my SSD for bad sectors without resorting to a clean install?

Try Safe Booting your Mac (with shift pressed) and then rebooting normally again - let us know if this helps.

ObeseSquirrel
Feb 10, 2013, 03:28 PM
Try Safe Booting your Mac (with shift pressed) and then rebooting normally again - let us know if this helps.

I've done that multiple times already. No change, though it may stop it for a little while. :(

EDIT: If it happens again, I'll try to post another Console message, though from what I can see, the Console isn't saying much, besides that logs and mail items are failing to save to disk (I think).

50548
Feb 10, 2013, 04:02 PM
I've done that multiple times already. No change, though it may stop it for a little while. :(

EDIT: If it happens again, I'll try to post another Console message, though from what I can see, the Console isn't saying much, besides that logs and mail items are failing to save to disk (I think).

Then I would also recommend you back up everything and perhaps try reformatting the whole enchilada.

I/O errors are normally the sign of something more serious.

Have you tried checking their SMART status?

ObeseSquirrel
Feb 10, 2013, 07:36 PM
Then I would also recommend you back up everything and perhaps try reformatting the whole enchilada.

I/O errors are normally the sign of something more serious.

Have you tried checking their SMART status?

It says "Verified" in Disk Utility. I do have Trim Enabler working, though I'm not sure if that would cause a problem.

By "something more serious" do you mean hardware-related? Would erasing the disk and then reinstalling from my Time Machine be a good idea, or do you mean a completely fresh install? (Reformat the disk, and move files back individually)

EDIT: I see the Disk I/O error seems to always refer to a temporary items folder for mail. Is it safe to delete that?

50548
Feb 11, 2013, 03:07 PM
It says "Verified" in Disk Utility. I do have Trim Enabler working, though I'm not sure if that would cause a problem.

By "something more serious" do you mean hardware-related? Would erasing the disk and then reinstalling from my Time Machine be a good idea, or do you mean a completely fresh install? (Reformat the disk, and move files back individually)

EDIT: I see the Disk I/O error seems to always refer to a temporary items folder for mail. Is it safe to delete that?

Disable TRIM Enabler - it's been reported to cause instability to many people, AND OWC specifically recommends AGAINST using it in any of SandForce drives. If your SSD already has garbage collection, you don't need it.

In any case and at the very least, try disabling it for now and see if the problem disappears.

ObeseSquirrel
Feb 11, 2013, 06:54 PM
Disable TRIM Enabler - it's been reported to cause instability to many people, AND OWC specifically recommends AGAINST using it in any of SandForce drives. If your SSD already has garbage collection, you don't need it.

In any case and at the very least, try disabling it for now and see if the problem disappears.

My understanding is that TRIM and garbage collection are different though. Garbage collection moves data around so it is more efficiently clustered in your SSD, while TRIM cleans out the deleted parts.

It happened again today, and I may have an idea of what's causing it. (Just an idea, though. I could be wrong.) When I eject my Time Machine Drive, the icons are supposed to disappear from my Desktop and my Finder to show that it has been ejected. Before 10.8.2, this happened normally, but since that update, the disks have taken longer to actually eject than it would appear. So my computer would show that my disks had ejected, but if I unplugged them, I would get an alert that my disks were ejected improperly. To eject properly, I would have to wait much longer than normal for it to happen.

The other day, I was running on battery power at my apartment, and I had unplugged my Time Machine drive too soon (but after it should have been ejected). When I plugged my Time Machine and my power back in, the problem occurred. This morning, on my way to school, I had unplugged my Time Machine relatively quickly, but not so fast enough to give me an improper eject message. When I opened my laptop at school, the computer had forgotten my wifi password, and sure enough, I could not save to disk. Restart, and I was fine. I believe that I had recently had some improper eject messages soon before the I/O had gone out, even though I had not unplugged my drive.

Also, my Time Machine Drive is password encrypted, and signs in automatically with my Keychain, so that could explain the Keychain connection. (I guess?)

This can't explain all of the times this has happened, but it may explain most of them. I'm just not sure. I'm thinking I will be extra careful with my external drives until hopefully 10.8.3 fixes this. Otherwise, I'll keep updates on my situation right here. :cool:

TheBSDGuy
Feb 11, 2013, 06:59 PM
I/O errors don't necessarily mean that the drive is bad, it means that the I/O operation failed. Most of the time on an HD, it's caused by a bad sector, but a bad or poorly connected cable can cause the exact same problem - it looks like a drive problem when it isn't one.

Find the web site for Scannerz, go to their downloads section, and get the document that describes path isolation and troubleshooting with Scannerz. That could tell you how this problem could occur and how to isolate it, but I have no idea if their product works on SSDs. I would have thought that the controller on an SSD would be mapping out bad blocks anyway.

SandboxGeneral
Feb 12, 2013, 05:41 AM
Is there a good way to test my SSD for bad sectors without resorting to a clean install?

You can get a mild check of it's status with SMART. Get the SMART Utility here (http://www.macupdate.com/app/mac/24875/smart-utility). It works on SSD's just like HDD's.

Next, or first, you should double check all the physical connections to the SSD. Be sure they're properly connected and not damaged.

If you're still having the problem after the physical check, and you have access to an IBM PC, you can run Spinrite on it. "SpinRite's Level 1 is a read-only scan, and doing that on an SSD makes a lot of sense. Do a read-only scan of an SSD, it'll show the SSD's controller that it's got a problem reading a sector, and then it'll map that out or rewrite it in order to strengthen that sector, if possible. So that ends up being a value for SpinRite on solid-state drives." - Steve Gibson (http://en.wikipedia.org/wiki/SpinRite), Spinrite creator and from the Security Now podcast.

If you can get the SSD into that IBM PC, run it only on level 1 or 2. You don't want levels 3 or 4 because those read and write which are great for HDD's, but not SSD's.

I use Spinrite (http://www.grc.com/spinrite.htm) as a maintenance and data recovery utility on all my HDD's. Below is my old MBP HDD in a Dell PC with Spinrite (http://www.grc.com/spinrite.htm) working on it.

Independent review of Spinrite (http://www.troyandjessica.com/geekspeak/reviews/spinrite) (not me)

https://dl.dropbox.com/u/49002863/MacRumors/SpinriteImages/IMG_2003.JPG

https://dl.dropbox.com/u/49002863/MacRumors/SpinriteImages/IMG_2004.JPG

4x_KlRlcqNI

ObeseSquirrel
Feb 12, 2013, 02:24 PM
Find the web site for Scannerz, go to their downloads section, and get the document that describes path isolation and troubleshooting with Scannerz. That could tell you how this problem could occur and how to isolate it, but I have no idea if their product works on SSDs. I would have thought that the controller on an SSD would be mapping out bad blocks anyway.

It seems like Scannerz does not support SSD's yet.

You can get a mild check of it's status with SMART. Get the SMART Utility here (http://www.macupdate.com/app/mac/24875/smart-utility). It works on SSD's just like HDD's.

Next, or first, you should double check all the physical connections to the SSD. Be sure they're properly connected and not damaged.

If you're still having the problem after the physical check, and you have access to an IBM PC, you can run Spinrite on it. "SpinRite's Level 1 is a read-only scan, and doing that on an SSD makes a lot of sense. Do a read-only scan of an SSD, it'll show the SSD's controller that it's got a problem reading a sector, and then it'll map that out or rewrite it in order to strengthen that sector, if possible. So that ends up being a value for SpinRite on solid-state drives." - Steve Gibson (http://en.wikipedia.org/wiki/SpinRite), Spinrite creator and from the Security Now podcast.

If you can get the SSD into that IBM PC, run it only on level 1 or 2. You don't want levels 3 or 4 because those read and write which are great for HDD's, but not SSD's.

Smart Utility shows my disk as "verified" but the short and long tests seem to hang my computer. (Like stuck on "2 minutes" for a couple of hours.) Connection seemed fine. I have an old HP laptop from c. 2005, but sadly, it's pre-SATA, so that is not an option (I think).

And… it happened again. This time there was a storm and my school has having wifi problems. After closing my laptop and opening it again somewhere else, I got the error. This time, I recognized it because the "connect to wifi" window kept popping up, as I had no access to the KeyChain.

This seems to usually happen with the same type of promptings, either after connecting or disconnecting an external drive, after waking from sleep, or after problems in the wifi problems. This makes me think it is something other than a normal hard drive dying, but beyond that, I am at a loss.

Here are some pictures from today. Upon restart, everything starting at 12:56:08 was gone (meaning that the SSD had stopped writing to disk).

50548
Feb 12, 2013, 04:06 PM
Have you tried disabling TRIM Enabler at all?

SandboxGeneral
Feb 12, 2013, 04:29 PM
Smart Utility shows my disk as "verified" but the short and long tests seem to hang my computer. (Like stuck on "2 minutes" for a couple of hours.) Connection seemed fine. I have an old HP laptop from c. 2005, but sadly, it's pre-SATA, so that is not an option (I think).


Here are some pictures from today. Upon restart, everything starting at 12:56:08 was gone (meaning that the SSD had stopped writing to disk).

You can get an IDE to SATA adapter for cheap if you're serious about trying Spinrite. Here is one from Amazon.com (http://www.amazon.com/IDE-SATA-Adapter/dp/B000RK89M4) for about $7.

Do you have those pictures to post still?

ObeseSquirrel
Feb 12, 2013, 07:50 PM
Have you tried disabling TRIM Enabler at all?

Not yet. I'll do that if 10.8.3 doesn't fix this.

You can get an IDE to SATA adapter for cheap if you're serious about trying Spinrite. Here is one from Amazon.com (http://www.amazon.com/IDE-SATA-Adapter/dp/B000RK89M4) for about $7.

Do you have those pictures to post still?

If 10.8.3 doesn't end this, I might just try that. Looks easy enough.

Got the pictures. Had trouble uploading them. Again, the I/O problem happened between 12:56:06 and 12:56:08.

SandboxGeneral
Feb 12, 2013, 07:55 PM
Not yet. I'll do that if 10.8.3 doesn't fix this.



If 10.8.3 doesn't end this, I might just try that. Looks easy enough.

Got the pictures. Had trouble uploading them. Again, the I/O problem happened between 12:56:06 and 12:56:08.

Why wait for 10.8.3? Disable TRIM now and see what happens. Are you using Groths (http://www.groths.org/trim-enabler/)? It's just a matter of flipping the switch to on or off.

Have you done anything with your screensaver and/or do you have Aperture? I came across this thread (https://discussions.apple.com/thread/4148836?start=15&tstart=0) based on one of the Console messages.

50548
Feb 13, 2013, 03:36 AM
Why wait for 10.8.3? Disable TRIM now and see what happens. Are you using Groths (http://www.groths.org/trim-enabler/)? It's just a matter of flipping the switch to on or off.

Have you done anything with your screensaver and/or do you have Aperture? I came across this thread (https://discussions.apple.com/thread/4148836?start=15&tstart=0) based on one of the Console messages.

I have already suggested that he disable TRIM Enabler and can't understand why he wouldn't do that just as an initial test - it's a matter of flicking the switch from ON to OFF...

ObeseSquirrel
Feb 13, 2013, 05:40 PM
Why wait for 10.8.3? Disable TRIM now and see what happens. Are you using Groths (http://www.groths.org/trim-enabler/)? It's just a matter of flipping the switch to on or off.

Have you done anything with your screensaver and/or do you have Aperture? I came across this thread (https://discussions.apple.com/thread/4148836?start=15&tstart=0) based on one of the Console messages.

Yes, it's Groths. The problem is that when 10.8.3 is released (I was assuming today or tomorrow) I would have TRIM disabled -and- 10.8.3, so I would not know that whether I fixed the problem. Not a big deal though. I'll disable it now, and if it happens again before 10.8.3, I'll know it isn't TRIM.

Don't have Aperture. Computer is set never to sleep, and "put disk to sleep whenever possible" is deactivated because I've read this is bad for SSD's. I *do* have "wake for network access" activated though. I do not use a screen saver. My display just goes black.

TheBSDGuy
Feb 14, 2013, 05:13 AM
1. Scannerz supports SSDs, otherwise it couldn't support Core Storage technology. To the best of my knowledge it treats even mounted disk images as valid drives. I don't know if it would be of any value to you, as the rest of this post will indicate.

2. I've read some of your other posts on Apple as well as responders to it, and all the posts in this thread, and one thing begs the question: Is this an OS problem, and will an update fix it?

IMHO you need to approach the problem in a logical manner, one step at a time. I would take the advice of BRLawyer and others BEFORE updating the OS, and disable TRIM enabler before proceeding.

The problems you're having appear to be similar to those of faulty connections somewhere in the system. Unfortunately, the more I use Mountain Lion, the more I'm inclined to move back to Snow Leopard.

Here are some of the problems I ran into when using an older version of iWeb and iPhoto that I imported to ML to try and update a simple and quite honestly pathetic little site I have for business purposes:

1. iPhoto seems to have a mind of its own as to whether or not a camera is attached. Sometimes it sees it sometimes it doesn't. If it does see it and there are images to download, whether or not their recognized is a crap shoot. Sometimes iPhoto simply crashes or locks up.

2. iWeb never exits cleanly. It exits with a crash, EVERY time. I can't really publish anything with it.

3. There are reports of external hard drive driver problems existing with ML and Lion that simply didn't exist before, and they're serious too.

The more I use ML the more buggy it appears. I remember that someone referred to Lion as Apple's "Vista Moment," but I'm beginning to believe it might be better to call it Apple's "Windows 95" moment.

If the problems you were having were on a STABLE operating system, I'd be inclined to tell you the problems were likely related to a bad cable or connection in the system, but if my digital camera is exhibiting the exact same types of problems, it implies to me this is a kernel problem and this isn't really a stable operating system. This has gotten ridiculous.

... I also understand that the development team at Apple was given a whopping 2 weeks to test and debug an OS. Note that comment - an OS, not an application.

In any case, good luck, and please let us know how things turn out.

ObeseSquirrel
Feb 14, 2013, 09:06 AM
1. Scannerz supports SSDs, otherwise it couldn't support Core Storage technology. To the best of my knowledge it treats even mounted disk images as valid drives. I don't know if it would be of any value to you, as the rest of this post will indicate.

http://www.scsc-online.com/Downloads_files/FAQ-2.pdf
"24. Can Scannerz be used with SSDs or flash drives? Scannerz will treat these as if they're regular hard drives, but the results might be erratic. SSDs are a “moving target.” The technology and how the OS deals with SSDs is still emerging. Future releases of Scannerz will have better SSD support. Scannerz can still be used with either of these if the user suspects the problem is related to the hardware connectivity circuitry or certain sections of the devices are unreadable.

2. I've read some of your other posts on Apple as well as responders to it, and all the posts in this thread, and one thing begs the question: Is this an OS problem, and will an update fix it?

IMHO you need to approach the problem in a logical manner, one step at a time. I would take the advice of BRLawyer and others BEFORE updating the OS, and disable TRIM enabler before proceeding.

The problems you're having appear to be similar to those of faulty connections somewhere in the system. Unfortunately, the more I use Mountain Lion, the more I'm inclined to move back to Snow Leopard.

Here are some of the problems I ran into when using an older version of iWeb and iPhoto that I imported to ML to try and update a simple and quite honestly pathetic little site I have for business purposes:

1. iPhoto seems to have a mind of its own as to whether or not a camera is attached. Sometimes it sees it sometimes it doesn't. If it does see it and there are images to download, whether or not their recognized is a crap shoot. Sometimes iPhoto simply crashes or locks up.

2. iWeb never exits cleanly. It exits with a crash, EVERY time. I can't really publish anything with it.

3. There are reports of external hard drive driver problems existing with ML and Lion that simply didn't exist before, and they're serious too.

The more I use ML the more buggy it appears. I remember that someone referred to Lion as Apple's "Vista Moment," but I'm beginning to believe it might be better to call it Apple's "Windows 95" moment.

If the problems you were having were on a STABLE operating system, I'd be inclined to tell you the problems were likely related to a bad cable or connection in the system, but if my digital camera is exhibiting the exact same types of problems, it implies to me this is a kernel problem and this isn't really a stable operating system. This has gotten ridiculous.

... I also understand that the development team at Apple was given a whopping 2 weeks to test and debug an OS. Note that comment - an OS, not an application.

In any case, good luck, and please let us know how things turn out.

I agree completely about the bugginess of Mountain Lion, but am glad that this may likely be an OS issue and not a hardware issue. It also seems like it is a problem with external connections somehow.

Another problem I have been having (randomly started about 3 weeks ago) is that my Safari will go out of control with RAM usage after a few hours. This will happen all at once, and my RAM will fill up with Active Memory, before paging out. My swap file will reach 14-18GB before my computer becomes almost completely unusable and I have to restart Safari. I had had this problem in 10.8.1 (I think) and determined that the only way to stop it was to disable JavaScript (unworkable) but the problem eventually ended. Now it's back and I use the Webkit Nightlies without a problem. The only difference in functionality between Safari and Webkit: Webkit has no access to the iCloud tabs…. Weird.

I have disabled TRIM Enabler, so if it happens again, I will know that this was not problem.

xgman
Feb 14, 2013, 11:51 AM
Trim enabler is trouble.

SandboxGeneral
Feb 14, 2013, 02:44 PM
Trim enabler is trouble.

Would you elaborate please on your statement and back it up with examples and sources?

50548
Feb 14, 2013, 03:43 PM
Would you elaborate please on your statement and back it up with examples and sources?

The Internet is full of them - reports of crashes, slowdowns and overall instability when using TRIM Enabler. Not to mention OWC's own explicit recommendation to AVOID it whenever using SandForce-enabled SSDs.

SandboxGeneral
Feb 14, 2013, 04:06 PM
The Internet is full of them - reports of crashes, slowdowns and overall instability when using TRIM Enabler. Not to mention OWC's own explicit recommendation to AVOID it whenever using SandForce-enabled SSDs.

Likewise, the Internet is probably also full of success stories in using a TRIM enabler. My point in asking xgman to elaborate and provide links was in the spirit of our rules for appropriate debate (http://guides.macrumors.com/Help:Rules_for_Appropriate_Debate) whereby we try to back up claims with sources and links so others can make more informed decisions or opinons on the subject at hand.

A blanket statement like that without further commentary, personal experience testimony or sources, is like a drive-by trolling post in some cases.

Since I recently purchased a MBP with a third-party SSD, I am personally reading up on everything there is to know about them. If TRIM is as bad as his one-liner suggests, I'd like to know more about why he said that.

I also just did a search (https://www.google.com/webhp?sourceid=chrome-instant&ion=1&ie=UTF-8#q=trim+support+site:www.macsales.com&hl=en&safe=off&tbo=d&filter=0&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=d5bbde17dd6cca0a&biw=957&bih=755&ion=1) of OWC's site looking for that explicit recommendation to not use TRIM enablers on SandForce SSD's and could not find anything. Would you post the link so I could read it too please?

TheBSDGuy
Feb 14, 2013, 09:22 PM
TheObeseSquirrel wrote:

http://www.scsc-online.com/Downloads_files/FAQ-2.pdf
"24. Can Scannerz be used with SSDs or flash drives? Scannerz will treat these as if they're regular hard drives, but the results might be erratic. SSDs are a “moving target.” The technology and how the OS deals with SSDs is still emerging. Future releases of Scannerz will have better SSD support. Scannerz can still be used with either of these if the user suspects the problem is related to the hardware connectivity circuitry or certain sections of the devices are unreadable.

Well, I never said I was an expert on Scannerz. :eek::D

Maybe I'll send the guys at SCSC an e-mail with a link to this post and possibly get a response from them that I can post here. We've been using it on SSDs without any problems.

As an FYI last night I thought I would watch a video online and for kicks thought I'd use FireFox for a change, since I hadn't used it on Mountain Lion. About 2 minutes into the video, I start seeing horizontal lines and blocks start running through the thing. I thought to myself, "Oh great, the display's going." When I hit escape which brought the video back into a window, it was apparent that it wasn't the display, it was FireFox...or at least FireFox running under Mountain Lion.

When I installed Mountain Lion, I basically split the original Snow Leopard volume, cloned it onto the new volume and installed ML over that. Glad I did, because now if I move back to SL it's still there, but migrating the e-mail back might be a PIA since I made a fairly hard commitment to ML when I moved to it. The video ran fine in SL on FireFox, although the two versions of FireFox are different.

50548
Feb 15, 2013, 05:13 PM
Likewise, the Internet is probably also full of success stories in using a TRIM enabler. My point in asking xgman to elaborate and provide links was in the spirit of our rules for appropriate debate (http://guides.macrumors.com/Help:Rules_for_Appropriate_Debate) whereby we try to back up claims with sources and links so others can make more informed decisions or opinons on the subject at hand.

A blanket statement like that without further commentary, personal experience testimony or sources, is like a drive-by trolling post in some cases.

Since I recently purchased a MBP with a third-party SSD, I am personally reading up on everything there is to know about them. If TRIM is as bad as his one-liner suggests, I'd like to know more about why he said that.

I also just did a search (https://www.google.com/webhp?sourceid=chrome-instant&ion=1&ie=UTF-8#q=trim+support+site:www.macsales.com&hl=en&safe=off&tbo=d&filter=0&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=d5bbde17dd6cca0a&biw=957&bih=755&ion=1) of OWC's site looking for that explicit recommendation to not use TRIM enablers on SandForce SSD's and could not find anything. Would you post the link so I could read it too please?

I would never state something like that without proper basis:

http://blog.macsales.com/11051-to-trim-or-not-to-trim-owc-has-the-answer

Other links report problems, but I am trying to ski with my wife tomorrow here in France so can't find them right now... ;)

SandboxGeneral
Feb 15, 2013, 05:31 PM
I would never state something like that without proper basis:

http://blog.macsales.com/11051-to-trim-or-not-to-trim-owc-has-the-answer

Thank you for providing the URL.

ObeseSquirrel
Feb 15, 2013, 10:21 PM
It happened again, after I had disabled TRIM Enabler, repaired permissions, and restarted the computer. So either TRIM was never the problem, or it has already damaged my system already. I am inclined to believe the former.

This happened while I had the laptop unplugged, and playing a video on my bed. It always happens after I have moved the computer around…

I have the sudden motion sensor disabled (because it's an SSD). Could that have anything to do with it?

I might just have to wait for 10.8.3 for this one to get fixed...

SandboxGeneral
Feb 15, 2013, 10:25 PM
It happened again, after I had disabled TRIM Enabler, repaired permissions, and restarted the computer. So either TRIM was never the problem, or it has already damaged my system already. I am inclined to believe the former.

This happened while I had the laptop unplugged, and playing a video on my bed. It always happens after I have moved the computer around…

I have the sudden motion sensor disabled (because it's an SSD). Could that have anything to do with it?

I might just have to wait for 10.8.3 for this one to get fixed...

Strange for sure. What is it that you think is in 10.8.3 that is going to fix the problem?

blueroom
Feb 15, 2013, 10:26 PM
Do not run Spinrite on an SSD, it'll wear it out prematurely. Plus SSDs have smart sector remapping.

Check for firmware updates for your SSD.

SandboxGeneral
Feb 15, 2013, 10:27 PM
Do not run Spinrite on an SSD, it'll wear it out prematurely. Plus SSDs have smart sector remapping.

Which model SSD is it?

Spinrite will only wear on an SSD if run on level's 3 or 4 which performs write actions. Levels 1 and 2 are read only which do not wear out SSD's.

blueroom
Feb 15, 2013, 10:36 PM
The current version of Sprinrite 6 is from 2004, long before SSDs. I would suspect the problem being in the firmware, OSX (reinstall & restore) or the sata cable (I had this go duff on a friends 2010 MBP). Of course it could also be a failing or worn out SSD (an early OCZ wore out on me).

SandboxGeneral
Feb 15, 2013, 10:39 PM
The current version of Sprinrite 6 is from 2004, long before SSDs.

That's irrelevant. Levels 1 and 2 are read only, you can read an SSD all day long everyday and it's not going to bother it a bit. The problem with wearing out an SSD comes in when it's being written to.

50548
Feb 16, 2013, 08:43 AM
It happened again, after I had disabled TRIM Enabler, repaired permissions, and restarted the computer. So either TRIM was never the problem, or it has already damaged my system already. I am inclined to believe the former.

This happened while I had the laptop unplugged, and playing a video on my bed. It always happens after I have moved the computer around…

I have the sudden motion sensor disabled (because it's an SSD). Could that have anything to do with it?

I might just have to wait for 10.8.3 for this one to get fixed...

And why did you disable the motion sensor again?

ObeseSquirrel
Feb 16, 2013, 09:06 AM
Strange for sure. What is it that you think is in 10.8.3 that is going to fix the problem?

This problem first appeared on October 10, 2012. The current version of Mountain Lion (12C60) was released on October 4. This makes me think this might be an issue with the latest OSX release. I will probably use the combo update to install 10.8.3 for good measure.


Check for firmware updates for your SSD.

Apparently the Corsair Performance Pro still uses the original firmware, though the website isn't very helpful, since it relies on a forum for this kind of information.
http://forum.corsair.com/forums/showthread.php?t=107588
(Last updated Nov. 18, 2012, so since this issue has started for me, at least.)

I would suspect the problem being in the firmware, OSX (reinstall & restore) or the sata cable (I had this go duff on a friends 2010 MBP). Of course it could also be a failing or worn out SSD (an early OCZ wore out on me).

Firmware: I believe I purchased my solid state drive around springtime last year, and this problem only started in October. It seems strange that a firmware problem would show up all at once, and then consistently afterward, no?

OSX (reinstall and restore): I reinstalled OSX over my current drive (not a clean install) after this problem started and it didn't solve the problem. I'm won't be ready to commit to a clean install unless 10.8.3 fails to address this issue.

SATA Cable: Spring of last year was a very traumatic time for me computer wise. Around this time (can't remember whether it was before or after the SSD arrived) my computer started having random kernel panics, followed by failure to restart, followed by normal behavior, and repeat. (This on Lion 10.7.3) The problem was only resolved when my entire motherboard was replaced. My point is that though my Macbook is a little old (MBP mid-2010, 13") most of the Internals have been in use for less than a year.

Failing or Worn SSD: Based on what others have said, I could erase the entire SSD and then restore from Time Machine, right? But then there's the risk that my Time Machine volume (dating back to June 2011, I believe) has been corrupted in that time. And if this isn't the real problem, I would have added a bunch of unnecessary writes to my disk.

One piece of information that might be helpful: While my laptop was being repaired last spring, I had all of my data stored on my brand new SSD, which I then tried to connect to my school's iMac via Firewire, so that I could continue my work. This worked for a few minutes, until I heard a click from my drive, and the computer froze. Upon restart, it did not recognize a partition at all on my disk. When my laptop came back, I had to reformat the SSD (don't know if it erased), restore from time machine, and then reinstall Lion over that to make it all work again. My point is that my current installation is written over a previous installation that had somehow mysteriously disappeared from my SSD. Don't know if that would affect the SSD's performance. But then again, it lasted for 6 months without any issue, until very shortly after the release of 12C60.

And why did you disable the motion sensor again?

Because it's unnecessary for an SSD, and I wasn't sure if it could be detrimental for the Mac to unnecessarily cause hangs in the system. Lots of SSD users seem to disable it. Apple says computers with SSD don't use SMS, because there are no moving parts, but for Apple, this language often means "computers that weren't shipped with SSD already."
http://support.apple.com/kb/HT1935?viewlocale=en_US

Here are my "pmset -g" settings, incase that's interesting:

Battery Power -1
AC Power -1*
Currently in use:
womp 1
halfdim 1
sms 0
hibernatefile /var/vm/sleepimage
networkoversleep 0
disksleep 0
sleep 0
hibernatemode 0
ttyskeepawake 1
displaysleep 15
acwake 0
lidwake 1

SandboxGeneral
Feb 16, 2013, 09:11 AM
And why did you disable the motion sensor again?

There is no need to leave it on with an SSD in place and it was a troubleshooting step for him as well no doubt.

Right from Apple's support site:

Mac notebooks: About the Sudden Motion Sensor (http://support.apple.com/kb/HT1935)
Note: Computers with Solid State Drives (SSD) or Flash Storage do not use SMS as the drives have no moving parts.

ObeseSquirrel
Feb 16, 2013, 09:14 AM
There is no need to leave it on with an SSD in place and it was a troubleshooting step for him as well no doubt.

Not a troubleshooting step. I did this almost as soon as I started using the SSD. Again, no problems until October.

SandboxGeneral
Feb 16, 2013, 09:18 AM
This problem first appeared on October 10, 2012. The current version of Mountain Lion (12C60) was released on October 4. This makes me think this might be an issue with the latest OSX release. I will probably use the combo update to install 10.8.3 for good measure.

I understand now where you're coming from. Doing the combo update is a good idea. Like you said already, one other possibility is doing a secure erase (http://www.anandtech.com/show/2738/11) of the SSD and restoring from Time Machine. I would wait on doing that until after you get 10.8.3 to see if it resolves itself.

Not a troubleshooting step. I did this almost as soon as I started using the SSD.

Good thinking. You're certainly doing your homework! :)

ObeseSquirrel
Feb 16, 2013, 09:33 AM
A note about my computer history:

In Snow Leopard and Early Lion, I seemed to have a lot of problems with wake from sleep, usually after I had moved between my apartment and school. The computer would simply wake up to a black screen, and I would have to shut down my computer and restart. This has happened a few times more recently, but it isn't nearly as much of a problem as it used to be.

Then in Spring 2012, I had the kernel panics mentioned above. Again, this was often shortly after I had awakened my computer, and usually after I had moved between locations (from what I can remember). Replacing the logic board seems to have resolved this issue.

And then there is this, disk i/o failure evidenced by either loss of access to keychain or a random program quitting and failing to restart, again correlated with (triggered by?) either waking from sleep, moving the computer, connecting/disconnecting external drives/power cords, or wifi network outages.

Could there be a longstanding problem with OSX generally after changes are made with the computers external connections?

smithrh
Feb 16, 2013, 08:02 PM
OP, there is a lot of info in this thread, but there are some key parts missing for me.

* Did you upgrade your MBP to SSD? It sounds like you did, but confirming would be helpful

* What model MBP (e.g., year) is this?

* How often does this problem occur?

While I know SSD is awesome (my 2008 unibody MacBook is running great on a Samsung 830 I installed in it recently), I really have to lean towards some issue with your SSD - but that's based on really thin information.

What I'm getting at is that I suggest going back to your HDD that you took out of the MBP when you upgraded [assuming a) you upgraded and b) you still have that drive around]. Or, you could buy a new SSD or HDD and start totally fresh.

If the problem you're describing doesn't re-occur within a reasonable timeframe, I'd say the SSD is the culprit. That is, if you get this problem once a month, then after 2 months I'd lean that direction and look at a new SSD.

I'll also say that hardware troubleshooting can be a PITA remotely. If you haven't already, you might want to consult a genius in the store. I'm also recommending this action because you mentioned the logic board was replaced, which gives me pause.

In the end, there are some issues that don't resolve well. Not being able to look at console logs is problematic. If this is a transient issue, then that's another complicating variable.

ObeseSquirrel
Feb 17, 2013, 03:12 PM
OP, there is a lot of info in this thread, but there are some key parts missing for me.

* Did you upgrade your MBP to SSD? It sounds like you did, but confirming would be helpful

Upgraded to SDD from original HDD.


* What model MBP (e.g., year) is this?

13" mid-2010

* How often does this problem occur?

There's no consistent timeframe. Lately, it's been every few days. Since starting this thread, it has happened on Feb. 10, Feb. 12, and Feb. 15. It seems to happen in spurts though, and may be about once a week on average. It's correlated with certain aspects of my behavior, especially when I move my computer around (as explained in the earlier posts).

While I know SSD is awesome (my 2008 unibody MacBook is running great on a Samsung 830 I installed in it recently), I really have to lean towards some issue with your SSD - but that's based on really thin information.

What I'm getting at is that I suggest going back to your HDD that you took out of the MBP when you upgraded [assuming a) you upgraded and b) you still have that drive around]. Or, you could buy a new SSD or HDD and start totally fresh.

If the problem you're describing doesn't re-occur within a reasonable timeframe, I'd say the SSD is the culprit. That is, if you get this problem once a month, then after 2 months I'd lean that direction and look at a new SSD.

I am using my original HDD as an external drive, but I do have an extra one laying around. Thanks for the suggestion! To save myself the trouble, I think I should troubleshoot in the following order:

1. See if 10.8.3 fixes this.
2. If not, secure erase my SDD and reinstall from Time Machine.
(may want to make sure my Time Machine isn't corrupted and restore to HDD just to be sure)
3. If not, move to HDD.
4. If not, clean install to SSD.
5. If not, clean install to HDD.

I'll also say that hardware troubleshooting can be a PITA remotely. If you haven't already, you might want to consult a genius in the store. I'm also recommending this action because you mentioned the logic board was replaced, which gives me pause.

In the end, there are some issues that don't resolve well. Not being able to look at console logs is problematic. If this is a transient issue, then that's another complicating variable.

Thanks a lot! :) I'm not sure why the logic board previously being replaced gives you pause, but consulting a genius may be a must if this continues. The timing of when this started makes me think it was a problem with the most recent iteration of 10.8.2, which will be fixed with 10.8.3, but I can't be sure. This is one reason why this update can't come soon enough.

smithrh
Feb 17, 2013, 03:33 PM
If I were in your shoes, I'd forget about 10.8.3. This sounds a lot more like a hardware issue than anything else. Sure, it *could* be OS-related, but with your input I'm leaning towards a hardware issue of some sort, specifically a flaked-out SSD. I'd hate to see you prolonging your issue by waiting, and loading 10.8.3 onto a bum SSD won't fix anything.

If it were OS-related then I'd expect more people to be complaining about this issue.

Given the frequency of occurrence, replacing the SSD with an HDD should tell you where you stand fairly quickly (a week or so).

Again, if I were in your shoes I'd be biting the bullet and starting fresh with an internal HDD. You want to remover as many variables as possible, and too many fingers point towards the existing SSD.

TheBSDGuy
Feb 18, 2013, 03:48 AM
I contacted SCSC about Scannerz and support for SSDs. You CAN test an SSD with Scannerz, but the "historical report" may not be of much value to you. The "historical report" is intended to typically indicate a performance slow down on a real (mechanical) hard drive where a loss of performance due to slow degradation over time would show up as changes in their relative performance indices. Because SSDs use varying and changing types of wear leveling and TRIM, and its operation and timing can't be predicted by them, it might tend to report inaccurate results in the "historical report."

That said, they took a look at this thread and suggested that the fact that you seem to be correlating movement with the appearance of the problem to them suggests a connection fault, such as a faulty cable, faulty connector, or cracked traces in the logic board. Traces in the SATA cable on those units can develop micro cracks and provide intermittent contact, which can yield I/O errors or irregularities during a Scannerz test, and of course during actual use as well.

They suggested you download their demo (limited to 0-10G sweeps) at:

http://www.scsc-online.com/Scannerz_files/Scannerz Demo.dmg

and do the following:

1. Start a scan on the unit in cursory mode. Keep in mind that with an SSD I assume you won't have a whole lot of time because I assume it will scan quickly and the demo is limited to 10G.

2. Click on the "Test Status" tab.

3. Monitoring the "Test Status" tab, start lightly tapping on the bottom of the unit near the vicinity of the SSD and cable.

4. If irregularities or errors are showing up that can be correlated to the tapping, then you've got an electrical fault in the system somewhere. This will be a cracked logic board trace, intermittent contact in the SATA cable, or connector problems.

5. If irregularities or errors are showing up at the exact same places in the scan, then you've got bad or marginal memory blocks in the SSD, but the demo only scans to 10G so the likelihood of this being the problem and being caught isn't that high.

Scannerz monitors for I/O errors and timing retries. If there are temporary disconnects due to something like a cable fault, cracked logic board trace, or intermittent contact in a connector, the system will try and re-try until electrical contact is re-established (sort of like a loose light bulb flickering on and off) at which point an irregularity is acknowledge by Scannerz, or if contact isn't re-established an I/O error will occur and will show up as an error in Scannerz. I would think in the latter your system would lock up, but that's me guessing (again). :)

The difference between a drive problem and a system problem is that drive problems, like bad sectors, will always occur at the exact same place during a drive scan, but if they're caused by bad cables, logic board traces, or connectors they won't be tied to a specific region of the drive, they'll happen randomly.

They also suggested that if you have the free space on your drive you might want to split the volume and try something like a basic installation of Snow Leopard or Lion on the smaller, new volume to see if the problems disappear.

One caveat about Scannerz: It disables Spotlight indexing during a scan. When it ends, Spotlight will start re-indexing the entire system on Mountain Lion (it didn't seem to do this on Snow Leopard or Lion, just incremental updates.) SCSC makes a product called "SpotOff" which allows users to enable/disable Spotlight indexing. It was intended to be used on PPC units with Leopard because Spotlight was so obnoxious on those systems and it seemed to be cleaned up in Snow Leopard and Lion because they appeared to do incremental indexing. Guess what? Now it's apparently a "hot selling product" since ML has been introduced. Can you guess why?

As an FYI about ML bugs, today all I was doing was some e-Mail and basic web browsing. The system came to a crawl. I checked Activity Monitor and the system was using all 4GB or RAM, most of it in the kernel_task, mds, and Safari Web Content. In fact, as I write this, Activity Monitor is reporting that I'm using 429M for the kernel_task, 234M for the mds process, and 152M for Safari Web Content. I've got about 100M of "inactive" memory, and the total sum of memory used is slightly over 2GB. That's a lot of memory to be used when the only applications I'm running are Safari and Activity Monitor. I swear to God this thing worked better when I had 2G installed in the system.

I've never had problems with an Apple OS like this before. I'm seriously considering moving back down to Lion or Snow Leopard. I wouldn't rule out the OS being the cause of the problems at all!

ObeseSquirrel
Feb 18, 2013, 01:17 PM
Now we might be getting somewhere! I'll explain below, so please offer your opinion if you have any. Referring this post to SCSC would be extremely helpful as well.

I contacted SCSC about Scannerz and support for SSDs. You CAN test an SSD with Scannerz, but the "historical report" may not be of much value to you. The "historical report" is intended to typically indicate a performance slow down on a real (mechanical) hard drive where a loss of performance due to slow degradation over time would show up as changes in their relative performance indices. Because SSDs use varying and changing types of wear leveling and TRIM, and its operation and timing can't be predicted by them, it might tend to report inaccurate results in the "historical report."

That said, they took a look at this thread and suggested that the fact that you seem to be correlating movement with the appearance of the problem to them suggests a connection fault, such as a faulty cable, faulty connector, or cracked traces in the logic board. Traces in the SATA cable on those units can develop micro cracks and provide intermittent contact, which can yield I/O errors or irregularities during a Scannerz test, and of course during actual use as well.

That would certainly be bad news. I don't want to have to replace Mac internals again! :( What would be the causes if this were the problem? I don't think I've ever been overtly rough with my Mac; I put it in my backpack and carry it around, but I haven't done anything unusual or actively destructive to it.

A note about the correlation with movement: This disconnect never happens while I am moving the computer around, but usually a few minutes afterward. I was never sure if it was the movement that triggered it, or the power/externals/wifi being (dis)connected.

They suggested you download their demo (limited to 0-10G sweeps) at:

http://www.scsc-online.com/Scannerz_files/Scannerz Demo.dmg

and do the following:

1. Start a scan on the unit in cursory mode. Keep in mind that with an SSD I assume you won't have a whole lot of time because I assume it will scan quickly and the demo is limited to 10G.

2. Click on the "Test Status" tab.

3. Monitoring the "Test Status" tab, start lightly tapping on the bottom of the unit near the vicinity of the SSD and cable.

4. If irregularities or errors are showing up that can be correlated to the tapping, then you've got an electrical fault in the system somewhere. This will be a cracked logic board trace, intermittent contact in the SATA cable, or connector problems.

5. If irregularities or errors are showing up at the exact same places in the scan, then you've got bad or marginal memory blocks in the SSD, but the demo only scans to 10G so the likelihood of this being the problem and being caught isn't that high.

Here's what Happened:

1. Scannerz told me to close all of my applications, so I closed them, except for the Finder.

2. Cursory Mode was unavailable, but I was able to use the Normal Scan for a Surface Scan (limited to 10 GB) and a Seek Scan (I think for the entire drive). No error reported.

3. I performed a second scan, since I was unsure whether this would scan the same same 10 GB or a different portion of the disk. Again, no errors.

4. I then performed a "Test Status" and lightly tapped the bottom of my laptop around where the SSD was located. There were no errors, so I lightly tapped the entire bottom of my laptop. Still no errors.

5. Spotlight was now reindexing.

6. I opened Safari to reply to your post.

7. Before Safari had loaded, I got a bunch of pop-up messages saying that all of my extensions were invalid and unable to load. I remembered that this had been one of the (many) symptoms of my i/o error once, so I opened a document and tried to save a change, and yep, IT HAPPENED AGAIN!

8. I restarted my computer, and all of my startup programs, PLUS SAFARI, opened up. This means that the disk i/o had failed *after* I had reopened Safari, but *before* the extensions were loaded.

My Time Machine external drive was connected the entire time.

Scannerz monitors for I/O errors and timing retries. If there are temporary disconnects due to something like a cable fault, cracked logic board trace, or intermittent contact in a connector, the system will try and re-try until electrical contact is re-established (sort of like a loose light bulb flickering on and off) at which point an irregularity is acknowledge by Scannerz, or if contact isn't re-established an I/O error will occur and will show up as an error in Scannerz. I would think in the latter your system would lock up, but that's me guessing (again). :)

The difference between a drive problem and a system problem is that drive problems, like bad sectors, will always occur at the exact same place during a drive scan, but if they're caused by bad cables, logic board traces, or connectors they won't be tied to a specific region of the drive, they'll happen randomly.

They also suggested that if you have the free space on your drive you might want to split the volume and try something like a basic installation of Snow Leopard or Lion on the smaller, new volume to see if the problems disappear.

One caveat about Scannerz: It disables Spotlight indexing during a scan. When it ends, Spotlight will start re-indexing the entire system on Mountain Lion (it didn't seem to do this on Snow Leopard or Lion, just incremental updates.) SCSC makes a product called "SpotOff" which allows users to enable/disable Spotlight indexing. It was intended to be used on PPC units with Leopard because Spotlight was so obnoxious on those systems and it seemed to be cleaned up in Snow Leopard and Lion because they appeared to do incremental indexing. Guess what? Now it's apparently a "hot selling product" since ML has been introduced. Can you guess why?

As an FYI about ML bugs, today all I was doing was some e-Mail and basic web browsing. The system came to a crawl. I checked Activity Monitor and the system was using all 4GB or RAM, most of it in the kernel_task, mds, and Safari Web Content. In fact, as I write this, Activity Monitor is reporting that I'm using 429M for the kernel_task, 234M for the mds process, and 152M for Safari Web Content. I've got about 100M of "inactive" memory, and the total sum of memory used is slightly over 2GB. That's a lot of memory to be used when the only applications I'm running are Safari and Activity Monitor. I swear to God this thing worked better when I had 2G installed in the system.

I've never had problems with an Apple OS like this before. I'm seriously considering moving back down to Lion or Snow Leopard. I wouldn't rule out the OS being the cause of the problems at all!

So there I am. I might try running Scannerz again, with just the "Normal Scan," and just the "Test Status" plus finger-tapping to see if one of those individually causes the problem. Or this may have been a coincidence (I had also just returned to my apartment from school, another trigger, apparently). Scannerz never reported an error, but it may have triggered the problem somehow. I don't know, but it's not looking good...

ObeseSquirrel
Feb 18, 2013, 01:36 PM
Note: This happened a couple of hours after I had had a wake-from-sleep issue while moving between classes. This may be irrelevant, but here's the Console log for that:

Here, I had opened the computer to a black screen. Pressing the power button brought me to my login screen, but the keyboard and trackpad would not respond. If this isn't related to the disk i/o error, I would rather focus on that, but if this is relevant, it might be worth looking at.

2/18/13 9:48:59.448 AM WindowServer[91]: CGXRegisterWindowWithSystemStatusBar: window 11 already registered
2/18/13 9:49:11.673 AM WindowServer[91]: CGXRegisterWindowWithSystemStatusBar: window 11 already registered
2/18/13 9:49:35.500 AM WindowServer[91]: CGXRegisterWindowWithSystemStatusBar: window 11 already registered
2/18/13 9:49:54.530 AM WindowServer[91]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
2/18/13 9:49:54.534 AM loginwindow[60]: find_shared_window: WID -1
2/18/13 9:49:54.534 AM loginwindow[60]: CGSGetWindowTags: Invalid window 0xffffffff
2/18/13 9:49:54.534 AM loginwindow[60]: find_shared_window: WID -1
2/18/13 9:49:54.534 AM loginwindow[60]: CGSSetWindowTags: Invalid window 0xffffffff
2/18/13 9:49:54.604 AM loginwindow[60]: ERROR | -[LWBuiltInScreenLockAuthLion preLoad] | guestEnabled is true, but guest mode is not set to a usable value
2/18/13 9:49:55.416 AM com.apple.time[13]: Next maintenance wake [Backup Interval]: <date: 0x7ffd22c32830> Mon Feb 18 10:13:30 2013 CST (approx)
2/18/13 9:49:55.416 AM com.apple.time[13]: Requesting maintenance wake [Backup Interval]: <date: 0x7ffd22c32830> Mon Feb 18 10:13:30 2013 CST (approx)
2/18/13 9:49:56.253 AM WindowServer[91]: Created shield window 0x1350 for display 0x042730c0
2/18/13 9:49:56.253 AM WindowServer[91]: device_generate_desktop_screenshot: authw 0x7fe8a4cbff20(2000), shield 0x7fe8a4cbfbb0(2001)
2/18/13 9:49:56.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
2/18/13 9:49:56.297 AM WindowServer[91]: device_generate_lock_screen_screenshot: authw 0x7fe8a4cbff20(2000), shield 0x7fe8a4cbfbb0(2001)
2/18/13 9:49:56.000 AM kernel[0]: en1: BSSID changed to d8:c7:c8:69:71:78
2/18/13 9:49:56.000 AM kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
2/18/13 9:49:56.000 AM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
2/18/13 9:49:56.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
2/18/13 9:49:57.316 AM WindowServer[91]: CGXDisableUpdate: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
2/18/13 9:52:15.394 AM WindowServer[91]: handle_will_sleep_auth_and_shield_windows: no lock state data
2/18/13 9:52:15.431 AM WindowServer[91]: reenable_update_for_connection: UI updates were finally reenabled by application "Finder" after 2.22 seconds (server forcibly re-enabled them after 1.00 seconds)
2/18/13 9:52:15.000 AM kernel[0]: Wake reason: EC LID0
2/18/13 9:52:15.000 AM kernel[0]: HID tickle 0 ms
2/18/13 9:52:15.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
2/18/13 9:52:15.000 AM kernel[0]: Previous Sleep Cause: 5
2/18/13 9:52:17.217 AM loginwindow[60]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
2/18/13 9:52:18.335 AM configd[19]: setting hostname to "USERNAME.local"
2/18/13 9:52:18.346 AM configd[19]: network changed: v4(en1-:129.118.9.166) DNS- Proxy- SMB-
2/18/13 9:52:18.422 AM usbmuxd[411]: AMDeviceConnect (thread 0x100681000): Could not connect to lockdown port (62078) on device 131 - 98cbd9c7dcfc83468aa7cf7d551e72872a602dc7: 0xe8000084.
2/18/13 9:52:18.423 AM usbmuxd[411]: _AMDevicePreflightWorker (thread 0x100681000): Pair worker could not connect to lockdownd on device 131: 0xe8000084.
2/18/13 9:52:18.456 AM eapolclient[7986]: en1 STOP
2/18/13 9:52:19.000 AM kernel[0]: MacAuthEvent en1 Auth result for: d8:c7:c8:69:74:98 MAC AUTH succeeded
2/18/13 9:52:19.000 AM kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
2/18/13 9:52:19.000 AM kernel[0]: AirPort: Link Up on en1
2/18/13 9:52:19.000 AM kernel[0]: en1: BSSID changed to d8:c7:c8:69:74:98
2/18/13 9:52:19.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
2/18/13 9:52:19.133 AM eapolclient[8174]: en1 START
2/18/13 9:52:19.170 AM eapolclient[8174]: en1 LEAP: successfully authenticated
2/18/13 9:52:19.732 AM airportd[8171]: _doAutoJoin: Already associated to “TTUnet”. Bailing on auto-join.
2/18/13 9:52:19.807 AM airportd[8171]: _doAutoJoin: Already associated to “TTUnet”. Bailing on auto-join.
2/18/13 9:52:20.000 AM kernel[0]: AirPort: RSN handshake complete on en1
2/18/13 9:52:20.547 AM configd[19]: network changed: v4(en1+:129.118.9.166) DNS+ Proxy+ SMB+
2/18/13 9:52:20.606 AM configd[19]: setting hostname to "soc-2.ttu.edu"
2/18/13 9:52:20.615 AM UserEventAgent[13]: Captive: en1: Not probing 'TTUnet' (protected network)
2/18/13 9:52:20.631 AM configd[19]: network changed: v4(en1!:129.118.9.166) DNS Proxy SMB
2/18/13 9:52:25.000 AM kernel[0]: AppleUSBHub::setPowerState(0xffffff802d759800, 2 -> 4) timed out after 10228 ms
2/18/13 9:52:25.000 AM kernel[0]: en1: BSSID changed to d8:c7:c8:69:74:98
2/18/13 9:52:26.286 AM airportd[8171]: _doAutoJoin: Already associated to “TTUnet”. Bailing on auto-join.
2/18/13 9:52:30.381 AM timezoned[8190]: bootstrap_look_up failed (44e)
2/18/13 9:52:30.412 AM timezoned[8190]: bootstrap_look_up failed (44e)
2/18/13 9:52:30.433 AM BetterTouchTool[8183]: kCGErrorIllegalArgument: CGSUnregisterWindowWithSystemStatusBar: Invalid window
2/18/13 9:52:35.509 AM com.apple.time[13]: Next maintenance wake [Backup Interval]: <date: 0x7ffd22e18c60> Mon Feb 18 10:13:29 2013 CST (approx)
2/18/13 9:52:35.509 AM com.apple.time[13]: Requesting maintenance wake [Backup Interval]: <date: 0x7ffd22e18c60> Mon Feb 18 10:13:29 2013 CST (approx)
2/18/13 9:52:35.000 AM kernel[0]: USBF: 114270.109 AppleUSBOHCI[0xffffff802d686000]::Found a transaction which hasn't moved in 5 seconds on bus 0x6, timing out! (Addr: 2, EP: 0)
2/18/13 9:52:35.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004051 - retrying
2/18/13 9:52:35.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe00002eb - retrying
2/18/13 9:52:35.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe00002ed (interface 0, reportID 0x0)
2/18/13 9:52:35.000 AM kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configurePower
2/18/13 9:52:35.000 AM kernel[0]: USBF: 114270.547 AppleUSBHub[0xffffff802d75aa00]::Suspend - expected port to be suspended for conversion, but it is not!!
2/18/13 9:52:35.635 AM WindowServer[91]: post_notification : Time out waiting for reply from "BetterTouchTool" for notification type 102 (CID 0x2bce3, PID 8183)
2/18/13 9:52:35.640 AM WindowServer[91]: Created shield window 0x1351 for display 0x042730c0
2/18/13 9:52:35.640 AM WindowServer[91]: device_generate_desktop_screenshot: authw 0x7fe8a4cbff20(2004), shield 0x7fe8a4cbfbb0(2001)
2/18/13 9:52:35.653 AM WindowServer[91]: device_generate_lock_screen_screenshot: authw 0x7fe8a4cbff20(2004), shield 0x7fe8a4cbfbb0(2001)
2/18/13 9:52:35.719 AM netbiosd[84]: name servers down?
2/18/13 9:52:35.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
2/18/13 9:52:35.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe0004061 (interface 0, reportID 0x0)
2/18/13 9:52:35.000 AM kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configureDataMode
2/18/13 9:52:35.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:52:35.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:52:35.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:52:35.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe0004061 (interface 0, reportID 0x0)
2/18/13 9:52:35.000 AM kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configurePower
2/18/13 9:52:35.000 AM kernel[0]: en1: BSSID changed to d8:c7:c8:69:74:98
2/18/13 9:52:35.000 AM kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
2/18/13 9:52:35.000 AM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
2/18/13 9:52:35.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
2/18/13 9:52:36.918 AM configd[19]: setting hostname to "USERNAME.local"
2/18/13 9:52:36.923 AM configd[19]: network changed: v4(en1-:129.118.9.166) DNS- Proxy- SMB-
2/18/13 9:52:36.951 AM usbmuxd[411]: AMDeviceConnect (thread 0x100681000): Could not connect to lockdown port (62078) on device 132 - 98cbd9c7dcfc83468aa7cf7d551e72872a602dc7: 0xe8000084.
2/18/13 9:52:36.951 AM usbmuxd[411]: _AMDevicePreflightWorker (thread 0x100681000): Pair worker could not connect to lockdownd on device 132: 0xe8000084.
2/18/13 9:52:46.000 AM kernel[0]: AppleUSBHub::setPowerState(0xffffff802d759800, 4 -> 2) timed out after 10288 ms
2/18/13 9:53:22.409 AM WindowServer[91]: handle_will_sleep_auth_and_shield_windows: no lock state data
2/18/13 9:52:46.000 AM kernel[0]: Wake reason: PWRB (User)
2/18/13 9:53:22.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
2/18/13 9:53:22.000 AM kernel[0]: Previous Sleep Cause: 5
2/18/13 9:53:24.238 AM AddressBookSourceSync[8177]: [CardDAVPlugin-ERROR] Exception caught while running sync with server: Error Domain=CoreDAVErrorDomain Code=1 "The operation couldn’t be completed. (CoreDAVErrorDomain error 1.)"
2/18/13 9:53:24.381 AM digest-service[8202]: label: default
2/18/13 9:53:24.381 AM digest-service[8202]: dbname: od:/Local/Default
2/18/13 9:53:24.381 AM digest-service[8202]: mkey_file: /var/db/krb5kdc/m-key
2/18/13 9:53:24.382 AM digest-service[8202]: acl_file: /var/db/krb5kdc/kadmind.acl
2/18/13 9:53:24.387 AM digest-service[8202]: digest-request: uid=0
2/18/13 9:53:24.496 AM rpcsvchost[8203]: sandbox_init: com.apple.msrpc.netlogon.sb succeeded
2/18/13 9:53:24.539 AM digest-service[8202]: digest-request: init request
2/18/13 9:53:24.545 AM digest-service[8202]: digest-request: init return domain: SOC-2 server: USERNAME
2/18/13 9:53:25.443 AM eapolclient[8174]: en1 STOP
2/18/13 9:53:25.936 AM eapolclient[8208]: en1 START
2/18/13 9:53:25.000 AM kernel[0]: MacAuthEvent en1 Auth result for: d8:c7:c8:69:74:98 MAC AUTH succeeded
2/18/13 9:53:25.000 AM kernel[0]: MacAuthEvent en1 Auth result for: d8:c7:c8:69:76:88 MAC AUTH succeeded
2/18/13 9:53:25.000 AM kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
2/18/13 9:53:25.000 AM kernel[0]: AirPort: Link Up on en1
2/18/13 9:53:25.000 AM kernel[0]: en1: BSSID changed to d8:c7:c8:69:76:88
2/18/13 9:53:25.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
2/18/13 9:53:26.039 AM eapolclient[8208]: en1 LEAP: successfully authenticated
2/18/13 9:53:26.000 AM kernel[0]: AirPort: RSN handshake complete on en1
2/18/13 9:53:26.098 AM configd[19]: network changed: v4(en1+:129.118.9.166) DNS+ Proxy+ SMB+
2/18/13 9:53:26.140 AM UserEventAgent[13]: Captive: en1: Not probing 'TTUnet' (protected network)
2/18/13 9:53:26.153 AM configd[19]: network changed: v4(en1!:129.118.9.166) DNS Proxy SMB
2/18/13 9:53:26.177 AM configd[19]: setting hostname to "soc-2.ttu.edu"
2/18/13 9:53:26.633 AM airportd[8201]: _doAutoJoin: Already associated to “TTUnet”. Bailing on auto-join.
2/18/13 9:53:26.708 AM airportd[8201]: _doAutoJoin: Already associated to “TTUnet”. Bailing on auto-join.
2/18/13 9:53:31.221 AM com.apple.launchd[1]: (com.apple.smb.preferences) Throttling respawn: Will start in 4 seconds
2/18/13 9:53:31.222 AM com.apple.launchd[1]: (com.apple.smb.preferences) Throttling respawn: Will start in 4 seconds
2/18/13 9:53:31.222 AM com.apple.launchd[1]: (com.apple.smb.preferences) Throttling respawn: Will start in 4 seconds
2/18/13 9:53:31.243 AM com.apple.launchd[1]: (com.apple.smb.preferences) Throttling respawn: Will start in 4 seconds
2/18/13 9:53:32.437 AM airportd[8201]: _doAutoJoin: Already associated to “TTUnet”. Bailing on auto-join.
2/18/13 9:53:32.000 AM kernel[0]: AppleUSBHub::setPowerState(0xffffff802d759800, 2 -> 4) timed out after 10154 ms
2/18/13 9:53:32.000 AM kernel[0]: en1: BSSID changed to d8:c7:c8:69:76:88
2/18/13 9:53:32.949 AM Finder[193]: -[ABAddressBook save] failed. (<ABAddressBook: 0x7f850d800d00>)
2/18/13 9:53:33.771 AM netbiosd[84]: name servers down?
2/18/13 9:53:35.326 AM digest-service[8202]: digest-request: uid=0
2/18/13 9:53:35.326 AM digest-service[8202]: digest-request: init request
2/18/13 9:53:35.336 AM digest-service[8202]: digest-request: init return domain: USERNAME server: SOC-2
2/18/13 9:53:36.415 AM BetterTouchTool[8216]: kCGErrorIllegalArgument: CGSUnregisterWindowWithSystemStatusBar: Invalid window
2/18/13 9:53:36.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:53:36.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:53:36.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:53:36.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe0004061 (interface 0, reportID 0x0)
2/18/13 9:53:36.000 AM kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configureDataMode
2/18/13 9:53:40.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:53:40.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:53:40.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:53:40.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe0004061 (interface 0, reportID 0x0)
2/18/13 9:53:40.000 AM kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configurePower
2/18/13 9:53:45.291 AM LKDCHelper[8223]: Starting (uid=501)
2/18/13 9:53:47.591 AM netbiosd[84]: name servers down?
2/18/13 9:53:56.703 AM usbmuxd[411]: AMDeviceConnect (thread 0x100719000): Could not connect to lockdown port (62078) on device 133 - 98cbd9c7dcfc83468aa7cf7d551e72872a602dc7: 0xe8000084.
2/18/13 9:53:56.704 AM usbmuxd[411]: _AMDevicePreflightWorker (thread 0x100719000): Pair worker could not connect to lockdownd on device 133: 0xe8000084.
2/18/13 9:53:56.704 AM com.apple.usbmuxd[411]: HandleDeviceAttachHelperCallback preflighting failed for WiFi device 0x85-129.118.9.29:0: 0xe8000084. Ignoring device.
2/18/13 9:54:10.000 AM kernel[0]: AppleUSBMultitouchDriver::handleSuspend - SuspendPort returned error 0xe00002e2.
2/18/13 9:54:16.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:54:16.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:54:16.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:54:16.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe0004061 (interface 0, reportID 0x0)
2/18/13 9:54:16.000 AM kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configurePower
2/18/13 9:54:18.470 AM WindowServer[91]: Created shield window 0x1352 for display 0x042730c0
2/18/13 9:54:18.513 AM WindowServer[91]: device_generate_desktop_screenshot: authw 0x7fe8a4cbff20(2004), shield 0x7fe8a4cbfbb0(2001)
2/18/13 9:54:18.526 AM WindowServer[91]: device_generate_lock_screen_screenshot: authw 0x7fe8a4cbff20(2004), shield 0x7fe8a4cbfbb0(2001)
2/18/13 9:54:25.864 AM netbiosd[84]: name servers down?
2/18/13 9:54:46.253 AM com.apple.time[13]: Next maintenance wake [Backup Interval]: <date: 0x7ffd22e23260> Mon Feb 18 10:13:29 2013 CST (approx)
2/18/13 9:54:46.253 AM com.apple.time[13]: Requesting maintenance wake [Backup Interval]: <date: 0x7ffd22e23260> Mon Feb 18 10:13:29 2013 CST (approx)
2/18/13 9:54:46.000 AM kernel[0]: AppleUSBMultitouchDriver::handleSuspend - SuspendPort returned error 0xe00002e2.
2/18/13 9:54:46.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
2/18/13 9:54:46.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:54:46.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:54:46.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest for reportID 0x0 returned with result 0xe0004061 - retrying
2/18/13 9:54:46.000 AM kernel[0]: AppleUSBMultitouchDriver::_deviceGetReport - DeviceRequest returned error 0xe0004061 (interface 0, reportID 0x0)
2/18/13 9:54:46.000 AM kernel[0]: AppleUSBMultitouchDebug: _deviceGetReport returned an error in configurePower
2/18/13 9:54:46.000 AM kernel[0]: en1: BSSID changed to d8:c7:c8:69:76:88
2/18/13 9:54:46.000 AM kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
2/18/13 9:54:46.000 AM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
2/18/13 9:54:46.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
2/18/13 9:54:47.579 AM configd[19]: setting hostname to "USERNAME.local"
2/18/13 9:54:47.584 AM configd[19]: network changed: v4(en1-:129.118.9.166) DNS- Proxy- SMB-
2/18/13 9:54:56.000 AM kernel[0]: AppleUSBHub::setPowerState(0xffffff802d759800, 4 -> 2) timed out after 10303 ms
2/18/13 9:55:03.012 AM loginwindow[60]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
2/18/13 9:55:03.416 AM WindowServer[91]: handle_will_sleep_auth_and_shield_windows: no lock state data
2/18/13 9:55:03.496 AM loginwindow[60]: resume called when there was already a timer
2/18/13 9:54:56.000 AM kernel[0]: Wake reason: PWRB (User)
2/18/13 9:55:03.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
2/18/13 9:55:03.000 AM kernel[0]: Previous Sleep Cause: 5
2/18/13 9:55:05.286 AM digest-service[8234]: label: default
2/18/13 9:55:05.286 AM digest-service[8234]: dbname: od:/Local/Default
2/18/13 9:55:05.286 AM digest-service[8234]: mkey_file: /var/db/krb5kdc/m-key
2/18/13 9:55:05.286 AM digest-service[8234]: acl_file: /var/db/krb5kdc/kadmind.acl
2/18/13 9:55:05.289 AM digest-service[8234]: digest-request: uid=0
2/18/13 9:55:05.307 AM digest-service[8234]: digest-request: init request
2/18/13 9:55:05.309 AM digest-service[8234]: digest-request: init return domain: SOC-2 server: USERNAME
2/18/13 9:55:06.272 AM eapolclient[8208]: en1 STOP

[And then I restarted the computer]

ZVH
Feb 18, 2013, 02:18 PM
Hi:

New to the discussion. Scannerz only does reads on drives and monitors timing, so it can't hurt anything. I'd ignore the errors in the log files because Mountain Lion is reporting so many errors on so many things even when its working right you almost can't tell what's right and what's wrong.

In another site somewhere (not this one and I don't remember where) Scannerz was picking up timing errors caused by an intermittent short in a FireWire connector even though the problem was detected during an internal HD test. Eventually the port blew. Moral of the story: Scannerz doesn't miss ANYTHING. It will pick up bad sectors, marginal sectors, and erratic timing errors. If it hasn't picked anything up on a few tests then you're out of the "intermittent contact/bad cable/logic board trace bad/connector" being the problem ball park - which is good, because those are the most difficult types of problems to troubleshoot. Unless you actually have bad blocks in the SSD beyond the 10G demo limit, it's something else. The only way you could clarify it would be to run a scan on the entire drive.

...and now for the bad news...

I did, however, find another post that may be of use to you:

http://forums.macrumors.com/showthread.php?t=1415481

I would go through that thread (maybe you did already) and see if the problems they're having are like yours.

To me it looks like SSDs are a lot like Chiropractors - some people swear by them, some people swear at them.

ObeseSquirrel
Feb 18, 2013, 02:29 PM
Hi:

New to the discussion. Scannerz only does reads on drives and monitors timing, so it can't hurt anything. I'd ignore the errors in the log files because Mountain Lion is reporting so many errors on so many things even when its working right you almost can't tell what's right and what's wrong.

In another site somewhere (not this one and I don't remember where) Scannerz was picking up timing errors caused by an intermittent short in a FireWire connector even though the problem was detected during an internal HD test. Eventually the port blew. Moral of the story: Scannerz doesn't miss ANYTHING. It will pick up bad sectors, marginal sectors, and erratic timing errors. If it hasn't picked anything up on a few tests then you're out of the "intermittent contact/bad cable/logic board trace bad/connector" being the problem ball park - which is good, because those are the most difficult types of problems to troubleshoot. Unless you actually have bad blocks in the SSD beyond the 10G demo limit, it's something else. The only way you could clarify it would be to run a scan on the entire drive.

...and now for the bad news...

I did, however, find another post that may be of use to you:

http://forums.macrumors.com/showthread.php?t=1415481

I would go through that thread (maybe you did already) and see if the problems they're having are like yours.

To me it looks like SSDs are a lot like Chiropractors - some people swear by them, some people swear at them.

I have had freezes, but very rarely. Usually it's the wake from sleep issue as stated above, or it's Dashboard related.

My particular SSD has a Marvell-based controller, if that's relevant. SATA on my Mac is NVIDIA.

I'll look at that thread in more detail this evening, and will probably try to see if I can trigger the i/o crash again with Scannerz as well.

I tried to do an Apple Hardware test with the Snow Leopard disk that came with my computer, but the computer just ejected it and booted normally. (I had been able to use AHT previously, and may or may have used it when this issue started back in October. I can't remember.)

smithrh
Feb 18, 2013, 02:35 PM
I don't think that has any relevance to your other (main) problem HOWEVER I do see some interesting things* in there.

If you can, I'd take your MBP to the TTUnet support folks in person and describe the issues you've been having waking from sleep. They may want to see those console logs.

* looks like something is programmatically taking screenshots of your desktop and login screens. If this isn't you doing this, perhaps it's some sort of security measure your school's put in place.

ObeseSquirrel
Feb 18, 2013, 04:27 PM
I don't think that has any relevance to your other (main) problem HOWEVER I do see some interesting things* in there.

If you can, I'd take your MBP to the TTUnet support folks in person and describe the issues you've been having waking from sleep. They may want to see those console logs.

* looks like something is programmatically taking screenshots of your desktop and login screens. If this isn't you doing this, perhaps it's some sort of security measure your school's put in place.

That isn't me. :eek: When I do a Google search, the "screenshot" messages appear common for people with sleep problems.

benthewraith
Feb 18, 2013, 06:30 PM
That isn't me. :eek: When I do a Google search, the "screenshot" messages appear common for people with sleep problems.

OP, from reading through this thread, I would recommend you just get an Ubuntu live cd and secure erase the drive. Don't copy from your Time Machine yet and see if the problem is resolved.

You can find the instructions here (http://mackonsti.wordpress.com/2011/11/22/ssd-secure-erase-ata-command/).

smithrh
Feb 18, 2013, 08:58 PM
OP, from reading through this thread, I would recommend you just get an Ubuntu live cd and secure erase the drive. Don't copy from your Time Machine yet and see if the problem is resolved.

You can find the instructions here (http://mackonsti.wordpress.com/2011/11/22/ssd-secure-erase-ata-command/).

The device is the OPs boot device. Not sure he can see if he can see if the problem is resolved that way - since he won't be able to, you know, boot.

:)

I also wouldn't totally trust the TM backup, which is why I continue to say that the OP should swap out the SDD for a known-good HDD and start from scratch.

benthewraith
Feb 19, 2013, 08:39 AM
The device is the OPs boot device. Not sure he can see if he can see if the problem is resolved that way - since he won't be able to, you know, boot.

:)

I also wouldn't totally trust the TM backup, which is why I continue to say that the OP should swap out the SDD for a known-good HDD and start from scratch.

Well naturally after secure-erasing the drive he'd reinstall the OS on his boot drive. Recommend that before having to go out and spend money on a conventional HDD or another SSD.

ZVH
Mar 5, 2013, 10:59 PM
So, what happened?

Mountain Lion seems to have a lot of bugs in it. I think before Apple spends time working on their next major OS release they really ought to get some of the bugs fixed in Mountain Lion. There are a lot of people having hardware problems, programs crashing, and memory being all hogged up for no reason.

This OS is NOT impressive!

ObeseSquirrel
Mar 7, 2013, 04:49 PM
So, what happened?

Mountain Lion seems to have a lot of bugs in it. I think before Apple spends time working on their next major OS release they really ought to get some of the bugs fixed in Mountain Lion. There are a lot of people having hardware problems, programs crashing, and memory being all hogged up for no reason.

This OS is NOT impressive!

I managed to last about 8 days without this crash. Then, my computer froze. Reboot, and I had this bug again within a few hours. Last terminal message before i/o was something about core storage and my Time Machine volume. :/

(I have Time Machine password protection, but not using File Vault.)

Still waiting for 10.8.3 before I do anything.

TheBSDGuy
Mar 9, 2013, 10:15 PM
I have a sneaky suspicion you may be waiting a looooooooooong time.

I found the following link which is focusing on some of the Lion/ML problems:

http://macperformanceguide.com/AppleCoreRot-intro.html

Pages and pages and pages of bugs.

ObeseSquirrel
Mar 10, 2013, 12:08 PM
I am currently at a resort on vacation for spring break. The wifi is extremely spotty, and I have to walk outside in order to get Internet to work. So I have 3 of the things that have been associated with this problem. 1) Computer unplugged; 2) Wifi problems; 3) Computer being moved around between locations.

Here is as much of the log as I can fit into this post. (censored information replaced w @@@). I am now seeing "kernel[0]: disk0s2: I/O error," which I hadn't seen before. (I placed a break where the Disk I/O stopped recording, as seen after I restarted my computer.)

3/10/13 10:39:00.000 AM kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
3/10/13 10:39:00.000 AM kernel[0]: AirPort: Link Up on en1
3/10/13 10:39:00.000 AM kernel[0]: en1: BSSID changed to 06:27:22:f9:7e:2e
3/10/13 10:39:00.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
3/10/13 10:39:00.707 AM airportd[828]: _doAutoJoin: Already associated to “Dreams_lobby”. Bailing on auto-join.
3/10/13 10:39:00.933 AM airportd[828]: _doAutoJoin: Already associated to “Dreams_lobby”. Bailing on auto-join.
3/10/13 10:39:01.043 AM airportd[828]: _doAutoJoin: Already associated to “Dreams_lobby”. Bailing on auto-join.
3/10/13 10:39:01.307 AM configd[19]: network changed: v4(en1+:10.0.1.41) DNS+ Proxy+ SMB
3/10/13 10:39:01.338 AM UserEventAgent[13]: Captive: en1: Probing 'Dreams_lobby'
3/10/13 10:39:01.500 AM UserEventAgent[13]: Captive: [async_http_read_stream:386] kCFStreamEventErrorOccurred kCFErrorDomainCFNetwork/306: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error 306.)
3/10/13 10:39:01.500 AM UserEventAgent[13]: Captive: [CaptiveHandleRedirect:2156] Unknown result value: 1, assuming online
3/10/13 10:39:01.505 AM configd[19]: network changed: v4(en1!:10.0.1.41) DNS Proxy SMB
3/10/13 10:39:03.249 AM BetterTouchTool[889]: kCGErrorIllegalArgument: CGSUnregisterWindowWithSystemStatusBar: Invalid window
3/10/13 10:39:06.383 AM timezoned[898]: bootstrap_look_up failed (44e)
3/10/13 10:39:06.402 AM timezoned[898]: bootstrap_look_up failed (44e)
3/10/13 10:39:29.993 AM com.apple.backupd-helper[887]: Not starting Time Machine backup after wake - failed to resolve alias to backup volume.
3/10/13 10:41:11.967 AM WindowServer[103]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
3/10/13 10:41:11.969 AM loginwindow[60]: find_shared_window: WID -1
3/10/13 10:41:11.969 AM loginwindow[60]: CGSGetWindowTags: Invalid window 0xffffffff
3/10/13 10:41:11.969 AM loginwindow[60]: find_shared_window: WID -1
3/10/13 10:41:11.969 AM loginwindow[60]: CGSSetWindowTags: Invalid window 0xffffffff
3/10/13 10:41:11.970 AM loginwindow[60]: find_shared_window: WID 67
3/10/13 10:41:11.998 AM loginwindow[60]: ERROR | -[LWBuiltInScreenLockAuthLion preLoad] | guestEnabled is true, but guest mode is not set to a usable value
3/10/13 10:41:12.108 AM WindowServer[103]: Created shield window 0x6f1 for display 0x042730c0
3/10/13 10:41:12.108 AM WindowServer[103]: device_generate_desktop_screenshot: authw 0x7f940cc16d00(2000), shield 0x7f940cc164c0(2001)
3/10/13 10:41:12.193 AM WindowServer[103]: device_generate_lock_screen_screenshot: authw 0x7f940cc16d00(2000), shield 0x7f940cc164c0(2001)
3/10/13 10:49:34.138 AM com.apple.launchd.peruser.501[170]: (com.apple.KerberosHelper.LKDCHelper[864]) Exited with code: 1
3/10/13 10:49:45.357 AM mdworker32[917]: CGSGetDisplayBounds: Invalid display 0x00000000
3/10/13 10:49:45.377 AM mdworker32[917]: bootstrap_look_up2 failed with 0x44c
3/10/13 10:49:45.000 AM kernel[0]: Sandbox: sandboxd(918) deny mach-lookup com.apple.coresymbolicationd
3/10/13 10:49:45.784 AM sandboxd[918]: ([917]) mdworker32(917) deny mach-lookup com.apple.PowerManagement.control (import fstype:hfs fsflag:480D000 flags:240000005E diag:0 uti:org.openxmlformats.wordprocessingml.template plugin:/Library/Spotlight/Microsoft Office.mdimporter - find suspect file using: sudo mdutil -t 41373764)
3/10/13 10:50:23.459 AM com.apple.backupd-helper[919]: Not starting scheduled Time Machine backup - time machine destination not resolvable.
3/10/13 10:51:44.857 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f940cc16d00(2000), shield 0x7f940cc164c0(2001), lock state 3
3/10/13 10:51:44.858 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: err 0x0
3/10/13 10:51:44.890 AM coreservicesd[33]: Application App:"Mail" [ 0x0/0xb00b] @ 0x0x7fde9a41fb20 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x1001:) ), so denying.
3/10/13 10:51:44.890 AM WindowServer[103]: [cps/setfront] Failed setting the front application to Mail, psn 0x0-0xb00b, securitySessionID=0x186a6, err=-13066
3/10/13 10:52:12.448 AM WindowServer[103]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
3/10/13 10:52:12.449 AM loginwindow[60]: find_shared_window: WID -1
3/10/13 10:52:12.449 AM loginwindow[60]: CGSGetWindowTags: Invalid window 0xffffffff
3/10/13 10:52:12.449 AM loginwindow[60]: find_shared_window: WID -1
3/10/13 10:52:12.450 AM loginwindow[60]: CGSSetWindowTags: Invalid window 0xffffffff
3/10/13 10:52:12.478 AM loginwindow[60]: ERROR | -[LWBuiltInScreenLockAuthLion preLoad] | guestEnabled is true, but guest mode is not set to a usable value
3/10/13 10:52:12.658 AM com.apple.time[13]: Next maintenance wake [Backup Interval]: <date: 0x7fd3d9e255c0> Sun Mar 10 11:50:23 2013 CDT (approx)
3/10/13 10:52:12.658 AM com.apple.time[13]: Requesting maintenance wake [Backup Interval]: <date: 0x7fd3d9e255c0> Sun Mar 10 11:50:23 2013 CDT (approx)
3/10/13 10:52:13.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
3/10/13 10:52:13.758 AM WindowServer[103]: Created shield window 0x6f5 for display 0x042730c0
3/10/13 10:52:13.759 AM WindowServer[103]: device_generate_desktop_screenshot: authw 0x7f940bc90190(2000), shield 0x7f940cb1bc80(2001)
3/10/13 10:52:13.900 AM WindowServer[103]: device_generate_lock_screen_screenshot: authw 0x7f940bc90190(2000), shield 0x7f940cb1bc80(2001)
3/10/13 10:52:14.000 AM kernel[0]: en1: BSSID changed to 06:27:22:f9:7e:2e
3/10/13 10:52:14.000 AM kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
3/10/13 10:52:14.000 AM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
3/10/13 10:52:14.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
3/10/13 10:52:15.301 AM configd[19]: network changed: v4(en1-:10.0.1.41) DNS- Proxy- SMB
3/10/13 10:53:42.000 AM kernel[0]: Wake reason: EC LID0
3/10/13 10:53:42.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
3/10/13 10:53:42.000 AM kernel[0]: Previous Sleep Cause: 5
3/10/13 10:53:42.000 AM kernel[0]: en1: 802.11d country code set to 'X0'.
3/10/13 10:53:42.000 AM kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
3/10/13 10:53:43.000 AM kernel[0]: en1: 802.11d country code set to 'US'.
3/10/13 10:53:43.000 AM kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
3/10/13 10:53:43.000 AM kernel[0]: Graphics suppressed 1629 ms
3/10/13 10:53:44.000 AM kernel[0]: MacAuthEvent en1 Auth result for: 06:27:22:f9:7e:2e MAC AUTH succeeded
3/10/13 10:53:44.000 AM kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
3/10/13 10:53:44.000 AM kernel[0]: AirPort: Link Up on en1
3/10/13 10:53:44.000 AM kernel[0]: en1: BSSID changed to 06:27:22:f9:7e:2e
3/10/13 10:53:44.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
3/10/13 10:53:45.259 AM airportd[828]: _doAutoJoin: Already associated to “Dreams_lobby”. Bailing on auto-join.
3/10/13 10:53:46.127 AM configd[19]: network changed: v4(en1+:10.0.1.41) DNS+ Proxy+ SMB
3/10/13 10:53:46.169 AM UserEventAgent[13]: Captive: en1: Probing 'Dreams_lobby'
3/10/13 10:53:46.295 AM UserEventAgent[13]: Captive: [async_http_read_stream:386] kCFStreamEventErrorOccurred kCFErrorDomainCFNetwork/306: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error 306.)
3/10/13 10:53:46.295 AM UserEventAgent[13]: Captive: [CaptiveHandleRedirect:2156] Unknown result value: 1, assuming online
3/10/13 10:53:46.300 AM configd[19]: network changed: v4(en1!:10.0.1.41) DNS Proxy SMB
3/10/13 10:53:49.905 AM com.apple.time[13]: Next maintenance wake [Backup Interval]: <date: 0x7fd3d9e32390> Sun Mar 10 11:50:23 2013 CDT (approx)
3/10/13 10:53:49.905 AM com.apple.time[13]: Requesting maintenance wake [Backup Interval]: <date: 0x7fd3d9e32390> Sun Mar 10 11:50:23 2013 CDT (approx)
3/10/13 10:53:49.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
3/10/13 10:53:50.000 AM kernel[0]: en1: BSSID changed to 06:27:22:f9:7e:2e
3/10/13 10:53:50.000 AM kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
3/10/13 10:53:50.000 AM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
3/10/13 10:53:50.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
3/10/13 10:53:51.197 AM configd[19]: network changed: v4(en1-:10.0.1.41) DNS- Proxy- SMB
3/10/13 10:53:51.241 AM AddressBookSourceSync[927]: Got error The Internet connection appears to be offline. (-1009) on subscription request (connection = <NSURLConnection: 0x7fbaa40c84c0>)
3/10/13 10:56:25.037 AM loginwindow[60]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
3/10/13 10:56:25.000 AM kernel[0]: Wake reason: EC LID0
3/10/13 10:56:25.000 AM kernel[0]: HID tickle 0 ms
3/10/13 10:56:25.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
3/10/13 10:56:25.000 AM kernel[0]: Previous Sleep Cause: 5
3/10/13 10:56:25.400 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
3/10/13 10:56:27.000 AM kernel[0]: MacAuthEvent en1 Auth result for: 06:27:22:f9:7e:2e MAC AUTH succeeded
3/10/13 10:56:27.000 AM kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
3/10/13 10:56:27.000 AM kernel[0]: AirPort: Link Up on en1
3/10/13 10:56:27.000 AM kernel[0]: en1: BSSID changed to 06:27:22:f9:7e:2e
3/10/13 10:56:27.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
3/10/13 10:56:28.200 AM airportd[828]: _doAutoJoin: Already associated to “Dreams_lobby”. Bailing on auto-join.
3/10/13 10:56:28.266 AM airportd[828]: _doAutoJoin: Already associated to “Dreams_lobby”. Bailing on auto-join.
3/10/13 10:56:29.094 AM configd[19]: network changed: v4(en1+:10.0.1.41) DNS+ Proxy+ SMB
3/10/13 10:56:29.158 AM UserEventAgent[13]: Captive: en1: Probing 'Dreams_lobby'
3/10/13 10:56:29.289 AM UserEventAgent[13]: Captive: [async_http_read_stream:386] kCFStreamEventErrorOccurred kCFErrorDomainCFNetwork/306: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error 306.)
3/10/13 10:56:29.289 AM UserEventAgent[13]: Captive: [CaptiveHandleRedirect:2156] Unknown result value: 1, assuming online
3/10/13 10:56:29.294 AM configd[19]: network changed: v4(en1!:10.0.1.41) DNS Proxy SMB
3/10/13 10:56:30.587 AM BetterTouchTool[937]: kCGErrorIllegalArgument: CGSUnregisterWindowWithSystemStatusBar: Invalid window
3/10/13 10:56:34.165 AM timezoned[941]: bootstrap_look_up failed (44e)
3/10/13 10:56:34.179 AM timezoned[941]: bootstrap_look_up failed (44e)
3/10/13 10:56:36.841 AM LKDCHelper[942]: Starting (uid=501)
3/10/13 10:56:39.725 AM WindowServer[103]: Created shield window 0x6f6 for display 0x042730c0
3/10/13 10:56:39.725 AM WindowServer[103]: device_generate_desktop_screenshot: authw 0x7f940bc90190(2004), shield 0x7f940cb1bc80(2001)
3/10/13 10:56:39.789 AM WindowServer[103]: device_generate_lock_screen_screenshot: authw 0x7f940bc90190(2004), shield 0x7f940cb1bc80(2001)
3/10/13 10:56:39.887 AM com.apple.time[13]: Next maintenance wake [Backup Interval]: <date: 0x7fd3d9e250e0> Sun Mar 10 11:50:22 2013 CDT (approx)
3/10/13 10:56:39.887 AM com.apple.time[13]: Requesting maintenance wake [Backup Interval]: <date: 0x7fd3d9e250e0> Sun Mar 10 11:50:22 2013 CDT (approx)
3/10/13 10:56:41.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
3/10/13 10:56:41.000 AM kernel[0]: en1: BSSID changed to 06:27:22:f9:7e:2e
3/10/13 10:56:41.000 AM kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
3/10/13 10:56:41.000 AM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
3/10/13 10:56:41.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
3/10/13 10:56:41.692 AM AddressBookSourceSync[927]: [CardDAVPlugin-ERROR] -getPrincipalInfo:[_controller supportsRequestCompressionAtURL:https://@@@gmail.com@p07-contacts.icloud.com/190980871/principal/] Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found." UserInfo=0x7fbaa421e330 {NSUnderlyingError=0x7fbaa43023d0 "A server with the specified hostname could not be found.", NSErrorFailingURLStringKey=https://@@@gmail.com@p07-contacts.icloud.com/190980871/principal/, NSErrorFailingURLKey=https://@@@gmail.com@p07-contacts.icloud.com/190980871/principal/, NSLocalizedDescription=A server with the specified hostname could not be found.}
3/10/13 10:56:41.697 AM AddressBookSourceSync[927]: Got error A server with the specified hostname could not be found. (-1003) on subscription request (connection = <NSURLConnection: 0x7fbaa433ffa0>)
3/10/13 10:56:42.032 AM configd[19]: network changed: v4(en1-:10.0.1.41) DNS- Proxy- SMB
3/10/13 10:56:42.142 AM AddressBookSourceSync[927]: -[ABAddressBook save] failed. (<ABAddressBook: 0x7fbaa43834f0>)
3/10/13 10:56:42.226 AM AddressBookSourceSync[927]: -[ABAddressBook save] failed. (<ABAddressBook: 0x7fbaa422fcb0>)
3/10/13 10:58:27.414 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
3/10/13 10:58:27.000 AM kernel[0]: Wake reason: EC LID0 OHC2
3/10/13 10:58:27.000 AM kernel[0]: HID tickle 0 ms
3/10/13 10:58:27.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
3/10/13 10:58:27.000 AM kernel[0]: Previous Sleep Cause: 5
3/10/13 10:58:27.000 AM kernel[0]: en1: 802.11d country code set to 'X0'.
3/10/13 10:58:27.000 AM kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
3/10/13 10:58:27.000 AM kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 3 of Hub at 0x6000000) may have caused a wake by issuing a remote wakeup (2)
3/10/13 10:58:28.000 AM kernel[0]: en1: 802.11d country code set to 'MX'.
3/10/13 10:58:28.000 AM kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 149 153 157 161 165
3/10/13 10:58:29.000 AM kernel[0]: MacAuthEvent en1 Auth result for: 06:27:22:f9:7e:2e MAC AUTH succeeded
3/10/13 10:58:29.000 AM kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
3/10/13 10:58:29.000 AM kernel[0]: AirPort: Link Up on en1
3/10/13 10:58:29.000 AM kernel[0]: en1: BSSID changed to 06:27:22:f9:7e:2e
3/10/13 10:58:29.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
3/10/13 10:58:30.440 AM airportd[828]: _doAutoJoin: Already associated to “Dreams_lobby”. Bailing on auto-join.
3/10/13 10:58:30.499 AM airportd[828]: _doAutoJoin: Already associated to “Dreams_lobby”. Bailing on auto-join.
3/10/13 10:58:31.213 AM configd[19]: network changed: v4(en1+:10.0.1.41) DNS+ Proxy+ SMB
3/10/13 10:58:31.341 AM UserEventAgent[13]: Captive: en1: Probing 'Dreams_lobby'
3/10/13 10:58:31.410 AM UserEventAgent[13]: Captive: [async_http_read_stream:386] kCFStreamEventErrorOccurred kCFErrorDomainCFNetwork/306: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error 306.)
3/10/13 10:58:31.411 AM UserEventAgent[13]: Captive: [CaptiveHandleRedirect:2156] Unknown result value: 1, assuming online
3/10/13 10:58:31.432 AM configd[19]: network changed: v4(en1!:10.0.1.41) DNS Proxy SMB
3/10/13 10:58:31.755 AM WindowServer[103]: CGXRegisterWindowWithSystemStatusBar: window 11 already registered
3/10/13 10:58:32.709 AM BetterTouchTool[950]: kCGErrorIllegalArgument: CGSUnregisterWindowWithSystemStatusBar: Invalid window

-(Disk I/O stops recording)-

3/10/13 10:58:57.801 AM Mail[186]: unrecognized decoding of mime part (null)
3/10/13 10:58:59.876 AM com.apple.PassXPCService[962]: PAPassValidator: _signatureIsValid failed to load signature file
3/10/13 10:59:00.000 AM kernel[0]: disk0s2: I/O error.
3/10/13 10:59:00.000 AM kernel[0]: jnl: unknown-dev: do_jnl_io: strategy err 0x5
3/10/13 10:59:00.000 AM kernel[0]: jnl: unknown-dev: end_transaction: only wrote 0 of 823808 bytes to the journal!
3/10/13 10:59:00.183 AM com.apple.backupd-helper[948]: Not starting Time Machine backup after wake - failed to resolve alias to backup volume.
3/10/13 10:59:00.628 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 10 seconds
3/10/13 10:59:01.070 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 10 seconds
3/10/13 10:59:01.166 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 10 seconds
3/10/13 10:59:01.279 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 9 seconds
3/10/13 10:59:01.380 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 9 seconds
3/10/13 10:59:01.481 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 9 seconds
3/10/13 10:59:02.178 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 9 seconds
3/10/13 10:59:03.198 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 8 seconds
3/10/13 10:59:04.215 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 7 seconds
3/10/13 10:59:04.393 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 6 seconds
3/10/13 10:59:04.494 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 6 seconds
3/10/13 10:59:04.596 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 6 seconds
3/10/13 10:59:05.210 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 6 seconds
3/10/13 10:59:06.226 AM com.apple.launchd[1]: (com.apple.aslmanager) Throttling respawn: Will start in 4 seconds
3/10/13 10:59:55.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
3/10/13 10:59:55.000 AM kernel[0]: en1: BSSID changed to 06:27:22:f9:7e:2e
3/10/13 10:59:55.000 AM kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
3/10/13 10:59:55.000 AM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
3/10/13 10:59:55.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
3/10/13 11:00:19.000 AM kernel[0]: Wake reason: EC LID0
3/10/13 11:00:19.000 AM kernel[0]: HID tickle 0 ms
3/10/13 11:00:19.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
3/10/13 11:00:19.000 AM kernel[0]: Previous Sleep Cause: 5
3/10/13 11:00:19.000 AM kernel[0]: en1: 802.11d country code set to 'X0'.
3/10/13 11:00:19.000 AM kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
3/10/13 11:00:20.000 AM kernel[0]: en1: 802.11d country code set to 'US'.

ObeseSquirrel
Mar 10, 2013, 12:57 PM
From this morning: another "kernel[0]: disk0s2: I/O error," but my computer was able to keep writing to disk afterwards. ("@@@" means I censored it.)

3/10/13 8:57:46.000 AM kernel[0]: MacAuthEvent en1 Auth result for: 06:27:22:f9:7e:2e MAC AUTH succeeded
3/10/13 8:57:46.000 AM kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
3/10/13 8:57:46.000 AM kernel[0]: AirPort: Link Up on en1
3/10/13 8:57:46.000 AM kernel[0]: en1: BSSID changed to 06:27:22:f9:7e:2e
3/10/13 8:57:46.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
3/10/13 8:57:47.335 AM airportd[425]: _doAutoJoin: Already associated to “Dreams_lobby”. Bailing on auto-join.
3/10/13 8:57:47.382 AM airportd[425]: _doAutoJoin: Already associated to “Dreams_lobby”. Bailing on auto-join.
3/10/13 8:57:47.439 AM airportd[425]: _doAutoJoin: Already associated to “Dreams_lobby”. Bailing on auto-join.
3/10/13 8:57:47.697 AM configd[19]: network changed: v4(en1+:10.0.1.41) DNS+ Proxy+ SMB
3/10/13 8:57:47.763 AM UserEventAgent[13]: Captive: en1: Probing 'Dreams_lobby'
3/10/13 8:57:47.890 AM UserEventAgent[13]: Captive: [async_http_read_stream:386] kCFStreamEventErrorOccurred kCFErrorDomainCFNetwork/306: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error 306.)
3/10/13 8:57:47.890 AM UserEventAgent[13]: Captive: [CaptiveHandleRedirect:2156] Unknown result value: 1, assuming online
3/10/13 8:57:47.896 AM configd[19]: network changed: v4(en1!:10.0.1.41) DNS Proxy SMB
3/10/13 8:57:48.620 AM BetterTouchTool[607]: kCGErrorIllegalArgument: CGSUnregisterWindowWithSystemStatusBar: Invalid window
3/10/13 8:57:52.747 AM timezoned[616]: bootstrap_look_up failed (44e)
3/10/13 8:57:52.762 AM timezoned[616]: bootstrap_look_up failed (44e)
3/10/13 8:58:17.250 AM com.apple.backupd-helper[605]: Not starting Time Machine backup after wake - failed to resolve alias to backup volume.
3/10/13 8:58:36.000 AM kernel[0]: disk0s2: I/O error.
3/10/13 8:58:50.819 AM WindowServer[103]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
3/10/13 8:58:50.820 AM loginwindow[60]: find_shared_window: WID -1
3/10/13 8:58:50.820 AM loginwindow[60]: CGSGetWindowTags: Invalid window 0xffffffff
3/10/13 8:58:50.820 AM loginwindow[60]: find_shared_window: WID -1
3/10/13 8:58:50.820 AM loginwindow[60]: CGSSetWindowTags: Invalid window 0xffffffff
3/10/13 8:58:50.840 AM loginwindow[60]: ERROR | -[LWBuiltInScreenLockAuthLion preLoad] | guestEnabled is true, but guest mode is not set to a usable value
3/10/13 8:58:51.064 AM com.apple.time[13]: Next maintenance wake [Backup Interval]: <date: 0x7fd3d9e24e10> Sun Mar 10 09:49:26 2013 CDT (approx)
3/10/13 8:58:51.064 AM com.apple.time[13]: Requesting maintenance wake [Backup Interval]: <date: 0x7fd3d9e24e10> Sun Mar 10 09:49:26 2013 CDT (approx)
3/10/13 8:58:52.123 AM WindowServer[103]: Created shield window 0x3fa for display 0x042730c0
3/10/13 8:58:52.124 AM WindowServer[103]: device_generate_desktop_screenshot: authw 0x7f940cb16550(2000), shield 0x7f940becaed0(2001)
3/10/13 8:58:52.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
3/10/13 8:58:52.219 AM WindowServer[103]: device_generate_lock_screen_screenshot: authw 0x7f940cb16550(2000), shield 0x7f940becaed0(2001)
3/10/13 8:58:52.000 AM kernel[0]: en1: BSSID changed to 06:27:22:f9:7e:2e
3/10/13 8:58:52.000 AM kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
3/10/13 8:58:52.000 AM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
3/10/13 8:58:52.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed
3/10/13 8:58:53.457 AM configd[19]: network changed: v4(en1-:10.0.1.41) DNS- Proxy- SMB
3/10/13 9:01:06.010 AM loginwindow[60]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
3/10/13 9:01:06.393 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
3/10/13 9:01:06.000 AM kernel[0]: Wake reason: EC LID0
3/10/13 9:01:06.000 AM kernel[0]: HID tickle 0 ms
3/10/13 9:01:06.000 AM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
3/10/13 9:01:06.000 AM kernel[0]: Previous Sleep Cause: 5
3/10/13 9:01:06.000 AM kernel[0]: en1: 802.11d country code set to 'X0'.
3/10/13 9:01:06.000 AM kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
3/10/13 9:01:07.000 AM kernel[0]: en1: 802.11d country code set to 'MX'.
3/10/13 9:01:07.000 AM kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 149 153 157 161 165
3/10/13 9:01:08.397 AM CalendarAgent[219]: [com.apple.calendar.store.log.caldav.queue] [Account refresh failed with error: Error Domain=NSURLErrorDomain Code=-1009 "The Internet connection appears to be offline." UserInfo=0x7fd7a3b7bf90 {NSUnderlyingError=0x7fd7a3b82f80 "The Internet connection appears to be offline.", NSErrorFailingURLStringKey=https://@@@gmail.com@p07-caldav.icloud.com/190980871/principal/, NSErrorFailingURLKey=https://@@@gmail.com@p07-caldav.icloud.com/190980871/principal/, AccountName=iCloud, CalDAVErrFromRefresh=YES, NSLocalizedDescription=The Internet connection appears to be offline.}]
3/10/13 9:01:11.640 AM BetterTouchTool[626]: kCGErrorIllegalArgument: CGSUnregisterWindowWithSystemStatusBar: Invalid window

TheBSDGuy
Mar 10, 2013, 07:20 PM
The demo you had for Scannerz was only a demo and it's limited to the 0-10G range. The message:

kernel[0]: disk0s2: I/O error

means one of the following:
1. That the SSD has bad sectors (blocks)on it
2. There's a cable problem with the drive
3. There's a cracked trace in the logic board.

In the latter two, intermittent contact would be causing data flow from the drive to the system to be erratically interrupted. Most of the time it succeeds, but once it a while it doesn't, and it's never repeatable.

Scannerz is the only tool that we use for drive testing because it's the only one that can identify all of these problems. If the error correction on the SSD is working properly, a Scannerz scan on the drive is SUPPOSED to cause the SSD controller to re-map the bad sector, assuming the SSD is doing what it's supposed to. In reality it shouldn't take a Scannerz scan to trigger this, because the SSD really ought to be auto correcting and relocating bad blocks to good blocks anyway, but that isn't what's happening. Why? If the error is being caused OUTSIDE the SSD, the SSD won't see an error. In other words, if your cable is bad and it has intermittent periods of connect and disconnect, your system will have delays, and once in a while an I/O error, but the SSD will never see them - it likely never got the data. This problem is usually more pronounced the hotter the unit gets.

This type of problem is not rare at all. Years ago Apple produced a 1GHz iBook that had the IDE cable, which was flexible mylar with copper traces etched on it, looping from the top side of the logic board through a slot, to the underside of the logic board with the connector held on with Kapton tape (YES, YOU DID READ THAT CORRECTLY!) Over a period of time, as the units went through heating and cooling cycles the tape would work it's way loose, the mylar IDE cable would act like a spring lever, and all of a sudden you'd get erratic drive failures...either long delays or flat out, unrepeatable I/O errors that could never be correlated to a drive during a surface scan. The fact is, the connector on the underside of the logic board was making inconsistent and erratic contact. There was another, rarer problem involving a break in one of the connections to the video chip on this model, but this was rare, and a lot of people had the drive problem and assumed it was the video problem. The fix was to reconnect and re-seat the cable and put on new Kapton tape. Apple had enough sense to fix this the next year.

The erratic nature of the problems you're having sound almost exactly like those I described above. The results users had were always the same: works well one minute, then for some reason it goes on the fritz, then it's OK, then it isn't. If the problem is related to a cable or a logic board or supply fault, then SMART status will not show any errors either since the errors are originating outside the SSD. Disk Utility and Scannerz only report SMART threshold levels (i.e. when disaster has occurred). If you're up to it, you could try smartmontools, but it's strictly command line and I don't know if your familiar with using terminal apps. At least you could find out if the SSD is going whacko on you.

My personal guess, and that's all this is, a guess, is that the drive cable to the SSD is bad, damaged, or not properly connected, or there's a logic board fault.

ObeseSquirrel
Mar 11, 2013, 12:18 PM
The demo you had for Scannerz was only a demo and it's limited to the 0-10G range. The message:

kernel[0]: disk0s2: I/O error

means one of the following:
1. That the SSD has bad sectors (blocks)on it
2. There's a cable problem with the drive
3. There's a cracked trace in the logic board.

In the latter two, intermittent contact would be causing data flow from the drive to the system to be erratically interrupted. Most of the time it succeeds, but once it a while it doesn't, and it's never repeatable.

Scannerz is the only tool that we use for drive testing because it's the only one that can identify all of these problems. If the error correction on the SSD is working properly, a Scannerz scan on the drive is SUPPOSED to cause the SSD controller to re-map the bad sector, assuming the SSD is doing what it's supposed to. In reality it shouldn't take a Scannerz scan to trigger this, because the SSD really ought to be auto correcting and relocating bad blocks to good blocks anyway, but that isn't what's happening. Why? If the error is being caused OUTSIDE the SSD, the SSD won't see an error. In other words, if your cable is bad and it has intermittent periods of connect and disconnect, your system will have delays, and once in a while an I/O error, but the SSD will never see them - it likely never got the data. This problem is usually more pronounced the hotter the unit gets.

This type of problem is not rare at all. Years ago Apple produced a 1GHz iBook that had the IDE cable, which was flexible mylar with copper traces etched on it, looping from the top side of the logic board through a slot, to the underside of the logic board with the connector held on with Kapton tape (YES, YOU DID READ THAT CORRECTLY!) Over a period of time, as the units went through heating and cooling cycles the tape would work it's way loose, the mylar IDE cable would act like a spring lever, and all of a sudden you'd get erratic drive failures...either long delays or flat out, unrepeatable I/O errors that could never be correlated to a drive during a surface scan. The fact is, the connector on the underside of the logic board was making inconsistent and erratic contact. There was another, rarer problem involving a break in one of the connections to the video chip on this model, but this was rare, and a lot of people had the drive problem and assumed it was the video problem. The fix was to reconnect and re-seat the cable and put on new Kapton tape. Apple had enough sense to fix this the next year.

The erratic nature of the problems you're having sound almost exactly like those I described above. The results users had were always the same: works well one minute, then for some reason it goes on the fritz, then it's OK, then it isn't. If the problem is related to a cable or a logic board or supply fault, then SMART status will not show any errors either since the errors are originating outside the SSD. Disk Utility and Scannerz only report SMART threshold levels (i.e. when disaster has occurred). If you're up to it, you could try smartmontools, but it's strictly command line and I don't know if your familiar with using terminal apps. At least you could find out if the SSD is going whacko on you.

My personal guess, and that's all this is, a guess, is that the drive cable to the SSD is bad, damaged, or not properly connected, or there's a logic board fault.

Thanks!

When you say it gets worse with heat, that would be the opposite of my experience, which usually happens shortly after waking from sleep. The intermittent problems fit, but my machine usually doesn't recover until I restart. So rather than an intermittent connection blip, the solve-by-restart like a software or a SSD problem. But I really don't know.

Since I am not at home, I have just disabled my Time Machine. Perhaps it has something to do with failed internal backup drives (which I might be able to disable via Terminal later.) Since disabling Time Machine yesterday, there has not been a problem, though that isn't saying much. If disabling TM doesn't work, I'm thinking I should reenable the Sudden Motion Sensor, just to see what happens.

MacRobert10
Mar 13, 2013, 03:43 AM
Dude, you've got a billion things going on with your system and you're not isolating any of them. You need to start with a basic, bare bones system with little running, then start adding things on sequentially. I don't even know HOW you get an I/O error from an SSD unless, like the other guy said, it's a crack in a logic board trace or a bad cable.

The only ways I know to diagnose that would be one of the following:

1. Use AHT into a long term test mode to test your unit.
2. Put Scannerz in cursory mode and keep running scan tests on it.

You would need to do these long term until a failure occurs, if it occurs. If you've got a cracked trace in a logic board or cable, the problem will only get worse until all of a sudden it breaks.

I'd tend to think it's more like the logic board because you seem to have errors with everything.

If you're already talking about re-attaching the sudden motion sensor, you might want to inspect or replace the SSD cable too. I know some of them come with their own dedicated cables and they're fragile and easy to screw up.

I'm not an expert on SSDs but I thought they had to relocate bad sectors because it's their nature to lose sectors when the memory cells deplete, which to me more or less rules out an I/O error from the SSD. BRLawyer told you to disable TRIM enabler and you said you did. Did you leave it disabled? The only way I could think of an SSD generating an I/O error because of a bad sector (memory cell) might be if the SSD's own TRIM routines were doing an operation and then TRIM enabler kicked and decided to work on that cell and it ended up being moved mid process. That MIGHT generate an I/O error, but I would also think your drive would be in a state of chaos right about now.

Last but not least, you're probably using the buggiest OS Apple has produced in the entire OS X line.

Good Luck.

ObeseSquirrel
Mar 13, 2013, 01:37 PM
Dude, you've got a billion things going on with your system and you're not isolating any of them. You need to start with a basic, bare bones system with little running, then start adding things on sequentially. I don't even know HOW you get an I/O error from an SSD unless, like the other guy said, it's a crack in a logic board trace or a bad cable.

I've been doing just the opposite: turning features off to see if the problem goes away. So far, I haven't had much luck, except that a couple of days ago, it was happening 3+ times a day from my current location, and with Time Machine disables, it hasn't happened again. Fingers crossed.

The only ways I know to diagnose that would be one of the following:

1. Use AHT into a long term test mode to test your unit.

I tried AHT, but I couldn't get my computer to accept the disk. A lot of people online say their CD drives stopped working after upgrading to Mountain Lion. And my computer model doesn't support the online version of AHT. WTF, Apple!

2. Put Scannerz in cursory mode and keep running scan tests on it.

Cursory Mode isn't available on my trial version. (I can't click "Start Scan" at least.) Do you mean keep it on "Test Status"?

You would need to do these long term until a failure occurs, if it occurs. If you've got a cracked trace in a logic board or cable, the problem will only get worse until all of a sudden it breaks.

It's not getting worse, though. It's happening in spurts. Last week, I had it going for about 8 days without any errors. Before that, it was every 3 days or so, and before that..., etc., etc.

I'd tend to think it's more like the logic board because you seem to have errors with everything.

If you're already talking about re-attaching the sudden motion sensor, you might want to inspect or replace the SSD cable too. I know some of them come with their own dedicated cables and they're fragile and easy to screw up.

This SSD did not come with its own SATA cable. You might have read that I had a GeekSquad repair on my computer about a year ago, and a screw up is certainly a possibility. I'm only talking about reenabling the SMS, because I don't know what else to do.

I'm not an expert on SSDs but I thought they had to relocate bad sectors because it's their nature to lose sectors when the memory cells deplete, which to me more or less rules out an I/O error from the SSD. BRLawyer told you to disable TRIM enabler and you said you did. Did you leave it disabled? The only way I could think of an SSD generating an I/O error because of a bad sector (memory cell) might be if the SSD's own TRIM routines were doing an operation and then TRIM enabler kicked and decided to work on that cell and it ended up being moved mid process. That MIGHT generate an I/O error, but I would also think your drive would be in a state of chaos right about now.

My understanding is that they have a limited amount of "writes" on them, but that the sectors don't go "bad" because of this. (They're still readable, just nor writeable.) TRIM-Enabler is disabled, but my SSD is said to support TRIM. I believe Garbage Collection and TRIM are separate things.

Last but not least, you're probably using the buggiest OS Apple has produced in the entire OS X line.

Good Luck.

Probably not the buggiest ever, but certainly in my limited (since 10.6.3) experience. Thanks!

MacRobert10
Mar 13, 2013, 06:46 PM
I've been doing just the opposite: turning features off to see if the problem goes away. So far, I haven't had much luck, except that a couple of days ago, it was happening 3+ times a day from my current location, and with Time Machine disables, it hasn't happened again. Fingers crossed.

I would do the exact opposite, with adding the backup drive and doing backups as the last thing to check at all. You don't have any anti-virus software installed do you? It's notorious for screwing things up.

Cursory Mode isn't available on my trial version. (I can't click "Start Scan" at least.) Do you mean keep it on "Test Status"?

Unless you're using Scannerz Lite, then Cursory Mode is available. Cursory mode tests have to be configured before running. You have to click on the drive to test first, then you click on the Cursory Scan button in the mid section, then click on Options. Put a check mark beside surface scan, and select the limit scanning range option. Adjust the scanning range to go from 0 to 10GB that way the demo limits exceeded dialog won't come up. After the options have been set the Start button is active. if there's intermittent contact in the system it will show up as an unrepeatable irregularity with a long length (like 2 or more seconds) or an unrepeatable I/O error. If you start moving the system around and these start showing up then that's almost certainly the problem. Repeatable I/O errors or irregularities mean the drive has problems, unrepeatable errors or irregularities mean the errors being caused by intermittent disconnects. Unfortunately you would have to keep running and re-running the test to catch an error, or you could try the test when the thing starts flaking out on you.

The only thing that can cause I/O errors are either breaks in the data lines or bad media in the SSD. Like I said before, I don't think the latter is possible with an SSD because they're supposed to automatically mark that as bad (unless, of course, SSDs are less than perfect....imagine that!) If you had intermittent breaks in the supply lines your drive and other components would drop out completely.

It's not getting worse, though. It's happening in spurts. Last week, I had it going for about 8 days without any errors. Before that, it was every 3 days or so, and before that..., etc., etc.


Intermittent problems are intermittent problems.

You might want to do a web search and see what other problems people are having. I know Time Machine is a problem with some systems.

ObeseSquirrel
Mar 14, 2013, 08:46 AM
I would do the exact opposite, with adding the backup drive and doing backups as the last thing to check at all.

It seemed the last couple of crashes were in close proximity to failed attempts to back up locally. Welp, that didn't work. Yesterday, I had the same kind of crash. This time, while watching a movie for a school project, laptop in my lap instead of on a table. (So I'm really thinking the "moving" thing is a big factor.) I have now reenabled SMS, to see if that has anything to do with it.


You don't have any anti-virus software installed do you? It's notorious for screwing things up.

ClamXav, though I don't believe I have it on a schedule right now.

Unless you're using Scannerz Lite, then Cursory Mode is available. Cursory mode tests have to be configured before running. You have to click on the drive to test first, then you click on the Cursory Scan button in the mid section, then click on Options. Put a check mark beside surface scan, and select the limit scanning range option. Adjust the scanning range to go from 0 to 10GB that way the demo limits exceeded dialog won't come up. After the options have been set the Start button is active. if there's intermittent contact in the system it will show up as an unrepeatable irregularity with a long length (like 2 or more seconds) or an unrepeatable I/O error. If you start moving the system around and these start showing up then that's almost certainly the problem. Repeatable I/O errors or irregularities mean the drive has problems, unrepeatable errors or irregularities mean the errors being caused by intermittent disconnects. Unfortunately you would have to keep running and re-running the test to catch an error, or you could try the test when the thing starts flaking out on you.

The only thing that can cause I/O errors are either breaks in the data lines or bad media in the SSD. Like I said before, I don't think the latter is possible with an SSD because they're supposed to automatically mark that as bad (unless, of course, SSDs are less than perfect....imagine that!) If you had intermittent breaks in the supply lines your drive and other components would drop out completely.

Ok, so SMS was reenabled, and then I tried this. Moved my computer around during the scan, and there was 1 Surface Scan Error, though I am not seeing a report start up. Saving still works, so this might have been the SMS. Where do I see the report? One popped up when I did a Normal Scan.

Intermittent problems are intermittent problems.

You might want to do a web search and see what other problems people are having. I know Time Machine is a problem with some systems.

Only mention of this I have ever found is in the link on the first post. Someone had replied to my Apple forums post saying they had had the same problem since 10.8.2, but then stopped answering my questions. Frustrating.

MacRobert10
Mar 14, 2013, 07:02 PM
There won't be a report generated for a cursory mode scan. The report is for regular hard drives and compares historical performance of the drive with its past performance. It's a wear indicator because as a mechanical drive gets older its performance starts to degrade without necessarily generating any wear errors.

What you have is a log file and it should be in your documents directory. Go to your documents directory and put it in list mode, then sort by date. They all start with "Log" or "log" followed by some kind of date format (I don't remember but it's pretty obvious). The log files will tell you where the scan failed and lists any irregularities.

If you re-scan and get the same I/O errors at the same point, then it's the SSD causing the problem If the problems can't be replicated, you can bet on it being the cable or a trace in the logic board. Here's a link to one of the manuals that I think is included in the package:

http://scsc-online.com/Downloads_files/Troubleshooting%20With%20Scannerz.pdf

You need to read some of the documentation to understand how to use the tool and what it does, even with the lame demo version. If you have an external bootable drive you can isolate the problem to the path in the logic board (is it the logic board, or is it just the path to the SSD, with the latter implying it's an SSD cable problem). It sounds like it's complicated, but it's really nothing more than common sense. The words "surface scan" in their GUI are because it's doing a surface scan test when the error was detected.

Could the SMS cause it? Maybe, but I thought that would only trigger an event when it detects a sudden change, like when the velocity of a computer goes from a few feet per second to a sudden stop, which is what happens when a laptop falls off a table. Hence the name, sudden motion sensor.

I think the most likely culprit will turn out to be your SSD cable.

ObeseSquirrel
Mar 14, 2013, 07:43 PM
There won't be a report generated for a cursory mode scan. The report is for regular hard drives and compares historical performance of the drive with its past performance. It's a wear indicator because as a mechanical drive gets older its performance starts to degrade without necessarily generating any wear errors.

What you have is a log file and it should be in your documents directory. Go to your documents directory and put it in list mode, then sort by date. They all start with "Log" or "log" followed by some kind of date format (I don't remember but it's pretty obvious). The log files will tell you where the scan failed and lists any irregularities.

If you re-scan and get the same I/O errors at the same point, then it's the SSD causing the problem If the problems can't be replicated, you can bet on it being the cable or a trace in the logic board. Here's a link to one of the manuals that I think is included in the package:

http://scsc-online.com/Downloads_files/Troubleshooting%20With%20Scannerz.pdf

You need to read some of the documentation to understand how to use the tool and what it does, even with the lame demo version. If you have an external bootable drive you can isolate the problem to the path in the logic board (is it the logic board, or is it just the path to the SSD, with the latter implying it's an SSD cable problem). It sounds like it's complicated, but it's really nothing more than common sense. The words "surface scan" in their GUI are because it's doing a surface scan test when the error was detected.

Could the SMS cause it? Maybe, but I thought that would only trigger an event when it detects a sudden change, like when the velocity of a computer goes from a few feet per second to a sudden stop, which is what happens when a laptop falls off a table. Hence the name, sudden motion sensor.

I think the most likely culprit will turn out to be your SSD cable.

Scan start - Start Byte: 7340032000 End Byte: 8388607999 Index: 7
SCAN FAILED - Start Byte: 7340032000 End Byte: 8388607999 Index: 7
BAD DATA DETECTED BETWEEN 8081637376 and 8081899520 BYTES.
Scan FAILED - Start Byte: 7340032000 End Byte: 8388607999 Index: 7
Scan start - Start Byte: 8388608000 End Byte: 9437183999 Index: 8
Scan passed - Start Byte: 8388608000 End Byte: 9437183999 Index: 8

I was thinking OSX might be confused with the SMS somehow. As in, normally with SMS enabled, the computer detects movement, stops the drive, and then starts it again. But with it disabled, somehow the drive stops with movement but fails to reconnect. That's just an idea, since I am completely guessing at this point.

Downloading 10.8.3 right now. :) Internet sucks here, so the Combo says it will take 9 more hours. If that doesn't fix it, I'll have to take more drastic action.

MacRobert10
Mar 14, 2013, 10:40 PM
That little log file clip shows you exactly why you probably have a bad cable or a cracked trace on you logic board. Another previous post you had said there was nothing there and now there is. That's exactly the type of stuff that Scannerz is supposed to pick up that nothing else does. The rule is simple:

1. If the errors are repeatable in the exact same sections of the drive, the drive is bad.
2. If the errors aren't repeatable, it's elsewhere in the system.

For the latter you have to do path isolation.

If you do path isolation I'd bet 50 bucks it will point right a the CPU to SSD path, and more than likely it's the cable. Unless your SSD is going south on you and those errors are actually bad SSD cells, which I find unlikely, the problems will likely continue and get worse.

Your 10.8.3 may help. I'm going to update it now myself and maybe some of these other dumb bugs will disappear - maybe it will turn into something that works right....like Snow Leopard!!!! :D

ObeseSquirrel
Mar 15, 2013, 12:07 PM
That little log file clip shows you exactly why you probably have a bad cable or a cracked trace on you logic board. Another previous post you had said there was nothing there and now there is. That's exactly the type of stuff that Scannerz is supposed to pick up that nothing else does. The rule is simple:

1. If the errors are repeatable in the exact same sections of the drive, the drive is bad.
2. If the errors aren't repeatable, it's elsewhere in the system.

For the latter you have to do path isolation.

If you do path isolation I'd bet 50 bucks it will point right a the CPU to SSD path, and more than likely it's the cable. Unless your SSD is going south on you and those errors are actually bad SSD cells, which I find unlikely, the problems will likely continue and get worse.

Your 10.8.3 may help. I'm going to update it now myself and maybe some of these other dumb bugs will disappear - maybe it will turn into something that works right....like Snow Leopard!!!! :D

Ugh... I just ran Cursory Scan twice more, and it found the bad data again in the exact same place! Normal Scan found it now too. This wasn't showing up before!!!

Quote from the Normal Scan report: "The surface scan test failed, and both the initial and current surface scan linear RPI values are comparable. Both the current and initial surface scan ratio RPI values are within acceptable ranges, even though this unit has failed a surface scan test. This implies the damage to the drive may not be extensive (yet)."

What does this mean? (again, keeping in mind that Scannerz may be strange with SSD's). Any ideas?

Still having trouble downloading 10.8.3 (I've given up on the Combo file until after the vacation. Using Software update, which should be ready in a couple of hours. Will run Scannerz again after the restart.

MacRobert10
Mar 15, 2013, 05:40 PM
Scannerz can do SSDs, it just can't do the historical profiling on them and there's no reason to do a seek scan because there aren't any moving parts on an SSD.

It sounds to me like your SSD has problems. I thought those things are supposed to auto-correct and map out bad sectors all on their own. I'm not an SSD expert, so maybe someone else here can chime in. I would think there would be some utility you could use to cause the SSD to map that stuff out. Repeatable bad sector mean it is the drive, not a cable. I'm also surprised. It also sounds like you're either really, really unlucky and just happened to hit some bad sectors, or they're dropping like flies.

Check out these links (some are from Windows):

http://www.tomshardware.com/forum/265868-32-ssds-sectors
http://forums.anandtech.com/showthread.php?t=2249701
http://www.ocztechnologyforum.com/forum/showthread.php?91631-Can-SSDs-Have-Bad-Sectors

The more I read about SSDs the happier I am I haven't switched to one yet.

ObeseSquirrel
Mar 17, 2013, 07:33 AM
Scannerz can do SSDs, it just can't do the historical profiling on them and there's no reason to do a seek scan because there aren't any moving parts on an SSD.

It sounds to me like your SSD has problems. I thought those things are supposed to auto-correct and map out bad sectors all on their own. I'm not an SSD expert, so maybe someone else here can chime in. I would think there would be some utility you could use to cause the SSD to map that stuff out. Repeatable bad sector mean it is the drive, not a cable. I'm also surprised. It also sounds like you're either really, really unlucky and just happened to hit some bad sectors, or they're dropping like flies.

Check out these links (some are from Windows):

http://www.tomshardware.com/forum/265868-32-ssds-sectors
http://forums.anandtech.com/showthread.php?t=2249701
http://www.ocztechnologyforum.com/forum/showthread.php?91631-Can-SSDs-Have-Bad-Sectors

The more I read about SSDs the happier I am I haven't switched to one yet.

Update:

1) I can confirm that this bug had nothing to do with reenabling the SMS. Unfortunately. :(

2) Scannerz started consistently showing 2 errors, instead of 1 from a couple of days ago.

From the "Normal Test" results:
General Results by Test Type:

Sizing Scan: PASSED
Surface Scan: FAILED
Seek Scan: PASSED
S.M.A.R.T. Status: Verified

Detailed Test Results:

Sizing Scan Errors: 0
Surface Scan Errors: 2
Surface Scan Irregularities: 0
Seek Scan Errors: 0
Seek Scan Irregularities: 0

Relative Performance Indices:

Current Surface Scan Linear RPI: 0.262437
Current Surface Scan Ratio RPI: 0.000000
Current Seek Scan Linear RPI: 1.611142
Current Seek Scan Ratio RPI: 1.601184

Initial Surface Scan Linear RPI: 0.250677
Initial Surface Scan Ratio RPI: 0.000000
Initial Seek Scan Linear RPI: 1.443496
Initial Seek Scan Ratio RPI: 1.390688

This is a comparative scan, and the values of the current test data will be compared to those in the initial scan data set.

The sizing scan completed without any errors.

The surface scan test failed, and both the initial and current surface scan linear RPI values are comparable. Both the current and initial surface scan ratio RPI values are within acceptable ranges, even though this unit has failed a surface scan test. This implies the damage to the drive may not be extensive (yet).

The seek scan passed, however a comparison of the initial and current seek scan linear RPI values shows a marked degradation. This frequently indicates that the unit is in the process of developing problems. The seek scan ratio RPIs are both within acceptable limits.

There were no irregularities detected in this test.


So Surface Scan: Failures, but still ok. Seek Scan: Passed, but marked degradation... What does this mean???

3) I was finally able to successfully install 10.8.3 after returning home from vacation by reinstalling all of OSX. (Scannerz still shows 2 errors though.) I will still watch for this error in the upcoming days. If the bug doesn't occur again within a week or so, I'm thinking about disabling SMS again and reenabling TRIM. (That is, if I don't ultimately decide to move back to the old HDD. :()

4) An interesting thing happened after the update. OSX told me that Parallels had been moved to an "Incompatible Software" folder. I checked, and saw that a "com.parallels.vm.prl_pcproxy.plist" and "Parallels Service.app" were now located there. Both files date back to August 2012, which I think means they were from Parallels 7. I currently use Parallels 8, but rarely. I was able to activate my Parallels VM within 10.8.3. Makes me wonder...

5) Superdrive works again. :) That means I can run AHT.

ObeseSquirrel
Mar 18, 2013, 12:18 AM
Welp, I purchased the full version of Scannerz, ran the test again, and there were still 2 errors.

So, I decided to bite the bullet, and completely reformat my drive. Disk Utility wouldn't allow a full "zeroing out" of my SSD, but I figured that if the SSD's firmware does its job, a full Time Machine restore shouldn't place any critical data on the bad sectors.

So, after spending all day restoring from ™, things were looking good. Everything was restored and Disk Utility was checking out fine. (I was afraid to run Scannerz again.)

I then completely reinstalled the OS again, just in case any of my Time Machine restored data had been corrupted on the bad sector. (I also wanted the Recovery Partition). This time, things were strange: My computer's time was stuck on the wrong Time Zone, and my Calendar was wrong (weeks starting on Saturday, with no way to change it.) So, I checked Disk Utility, and found that my drive was corrupted with "an incorrect number of file links". Disk Utility easily repaired this. Then, while trying to repair permissions, Disk Utility found a corrupt Automator file. (Unknown Error -22) I replaced it with a copy from last July using Time Machine, and the error went away.

So, I finally mustered the courage to try Scannerz again, and I can happily report that there are no more errors. :) I may never know whether this was ultimately a hardware problem or a software problem, but I think I can say that if I do not post back here within the next two weeks, we can consider this problem tentatively solved.

Thanks guys!

TheBSDGuy
Mar 21, 2013, 05:49 AM
I haven't visited this post in a while...sorry about that.

Now you know why people that know what they're doing are using Scannerz. I told you buddy...it doesn't lie!! And they don't even advertise their ability to do SSDs as you pointed out. If ONLY Apple would put that kind of quality into their OS (by the way, I switched from ML to Lion and now I can send Notes to my iPhone without using iCloud and I can ignore all the other archaic changes Apple made). Both Lion and Snow Leopard seem so much faster.

I just hope your SSD fares well. From reading some of the other posts, it seems you had something of a bizarre problem. I have to wonder if something like TechTool Pro of Drive Genius would have even picked it up.

ObeseSquirrel
Mar 21, 2013, 11:42 AM
I haven't visited this post in a while...sorry about that.

Now you know why people that know what they're doing are using Scannerz. I told you buddy...it doesn't lie!! And they don't even advertise their ability to do SSDs as you pointed out. If ONLY Apple would put that kind of quality into their OS (by the way, I switched from ML to Lion and now I can send Notes to my iPhone without using iCloud and I can ignore all the other archaic changes Apple made). Both Lion and Snow Leopard seem so much faster.

I just hope your SSD fares well. From reading some of the other posts, it seems you had something of a bizarre problem. I have to wonder if something like TechTool Pro of Drive Genius would have even picked it up.

Yup! :)

My computer was running a little rocky on Sunday and Monday, had a few "kernel: disk i/o" errors show up in the console, alongside a bunch of "talagent: CoreAnimation rendering error 506"s. I take it that talagent is a function of the Resume feature, and that this could be related to the growing pains following the reinstall. (Time Machine is always *really* fun for the couple of days after I do this.) This has not happened since Monday.

I have had my computer on for almost three full days (following the Monday weirdness) and still no problems saving to disk! :D Just now, I ran a full Scannerz test on my drive – while moving around from room to room, no less – with no issues reported, and no problems saving.

But I am a little worried that Scannerz wasn't showing the errors before, and then started showing 2 errors consistently a little later (as if my disk was suddenly degrading). The Console i/o logs were also different IIRC. But with the 10GB scan limit, I can't be sure it was even scanning the same 10 GB all those times. The jump from finding 1 to 2 was probably due to me scanning the whole drive instead of just the "Mac HD" partition, since it would show 1 error for the "Mac HD" and 2 for the whole SSD afterwards.

I will still be on the lookout for the next couple of weeks, but I think odds are the full erase and Time Machine reinstall did it. Thanks, guys!

----------

Also interesting, in 10.8.2, I had a bug where external drives would take a long time to properly eject, even after the icons had disappeared from my Desktop. Today, I was able to unplug my Time Machine drive as soon as the icons had disappeared, without getting the "improper eject" warning.

So if there was a software problem related to my MBP's handling of drives causing this, that's gone too.

MacRobert10
Mar 22, 2013, 03:06 AM
I think we can safely conclude that Scannerz can detect bad sectors on an SSD, which is good. Scannerz detects both weak and bad sectors on a drive. A weak sector shows up as an "irregularity" because the drive takes longer to read it than normal, but eventually succeeds. I would wonder if perhaps something similar doesn't happen with SSDs, but their speed is so much faster than a hard drive that it falls beneath Scannerz threshold level. Well, it's theory anyway. ;)

With that said, I find it interesting that the infallible SSD's we've been hearing all the raves about are ending up having the exact same problems hard drives have.

ObeseSquirrel
Mar 23, 2013, 10:16 PM
I think we can safely conclude that Scannerz can detect bad sectors on an SSD, which is good. Scannerz detects both weak and bad sectors on a drive. A weak sector shows up as an "irregularity" because the drive takes longer to read it than normal, but eventually succeeds. I would wonder if perhaps something similar doesn't happen with SSDs, but their speed is so much faster than a hard drive that it falls beneath Scannerz threshold level. Well, it's theory anyway. ;)

With that said, I find it interesting that the infallible SSD's we've been hearing all the raves about are ending up having the exact same problems hard drives have.

I'm kind of amazed that OSX doesn't have something like Scannerz built into Disk Utility. Hasn't Windows had the ability to detect bad sectors for ages?

Something interesting: I just enabled noatime (by default, OSX records last access time for every file), since it's recommended for SSD's to reduce writes to the disk. So far, it seems like disk writes have been reduced by about 20-30%. That might help speed things up a little, especially for you HDD folks. ;)

TheBSDGuy
Mar 24, 2013, 03:28 AM
I'm kind of amazed that OSX doesn't have something like Scannerz built into Disk Utility. Hasn't Windows had the ability to detect bad sectors for ages?

Actually, it has to do with the OS, I think. Windows is more or less implicitly tied to hardware, whereas OS X and other Unix variants aren't. That's why any time you add a piece of hardware to a Windows system, you typically have to fool with drivers (or at least used to...it may be different nowadays since it's been over 7 years since I worked on a Windows system).

The trouble with not being implicitly tied to the OS means that timing errors and I/O errors are more or less "generic" when presented to the kernel. It can't tell, per se whether or not the I/O error was specifically from the drive or whether or it was caused by a bad cable. That's why people like me like Scannerz. If the problem is repeatable in cursory mode, it's the media (drive, SSD, whatever) causing the problem. It it isn't repeatable from scan to scan, it's being caused by a cable or something in the circuitry and it can be traced to the major component level.

To go off topic for a moment, after moving back to Lion I wanted to test the actual performance of the GUI stuff to see if the performance difference was real or my imagination.

Below are some comparisons between the two (TSTM means to short to measure). I'd open an app on both Lion and Mountain Lion and time the amount of time it takes for each to open with a digital stop watch. TSTM really means that I can't click the start and stop buttons fast enough to measure it. These obviously aren't scientific, I just wanted to find out if the performance difference was real or my imagination. It wasn't my imagination, Lion's loading stuff a lot faster.

Command: Open Safari
Lion: 1.5 sec.
ML: 7 sec.

Command: Open TextEdit
Lion: TSTM
ML: 5 sec

Command: Open Mail
Lion: 2 sec
ML: 8 sec

I knew it wasn't my imagination. And now I can sync notes to the iPhone again without iCloud.

ObeseSquirrel
Mar 24, 2013, 10:19 AM
OH MY GOD!!!!!! SERIOUSLY???????

It happened again. One of my programs crashed (MenuTab Pro) which was usually a sign that my disk drive had disconnected. So I opened an MS Word Document, and … I couldn't save it. Neither Disk Utility, not Scannerz would start properly.

Will restart the computer and see if Scannerz finds anything.

I seriously want to destroy my computer right now.

------------------------------------------------

Edit: Ran Scannerz again, and there were no errors.

Mount Command

Running the "mount" command in terminal, I get:

Last login: Sun Mar 24 12:10:16 on ttys000
FirstName-LastName:~ FirstNameLastName$ mount
/dev/disk0s2 on / (hfs, local, journaled, noatime)
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
localhost:/RANDOMLETTERSANDNUMBERS on /Volumes/MobileBackups (mtmfs, nosuid, read-only, nobrowse)
/dev/disk2 on /Volumes/Time Machine Backups (hfs, local, nodev, nosuid, journaled)
/dev/disk3 on /Volumes/Parallels Backup (hfs, local, nodev, nosuid, journaled, noowners)
FirstName-LastName:~ FirstNameLastName$

I have no idea if any of that is interesting. ("Parallels Backup" is a partition on my Time Machine drive that keeps a copy of my Parallels VM.)

Glimmerblocker

I did not mention this before. The last time I fully reinstalled OSX, OSX randomly placed some files from Glimmerblocker into the "Incompatible Software" folder without notifying me. (It had previously notified me when I first installed 10.8.3 the day before that the random Parallels 7 files had been placed there.) Yesterday, I reinstalled Glimmerblocker, which is a very tiny program. After doing this, Time Machine made a huge backup file of 19GB, which apparently included all of my Applications, my Library, and my System/Library files. This seemed very strange to me.

If Glimmerblocker is the source of the problem (and I cannot think of a reason why it would be), I'm thinking I should disable it for two weeks and see if the problem stops. But according to Time Machine, I installed Glimmerblocker in early September, while the problem started in early/mid October.

Parallels?

Another thing I have noticed: I have a shortcut to my main Parallels VM in my Doc. By default, it's icon is a red Parallels logo, but after these crashes, or after a SafeBoot, it shows up as the default document icon (blank page with a dog ear) until I click on it again. I'm assuming this simply means that the document icons in the Dock are part of a cache that is cleared upon hard restarts, but I wanted to make sure. Time Machine says that my Dock from October 17, 2012 did not have this shortcut, fyi.

Console/ New Problem?

Since updating to 10.8.3, I have had several problems with my application windows not responding when I clicked on the icon for the active program in the Dock. Closing the program and restarting fixes it. Possibly related, my Console is repeatedly becoming clogged with *LOTS* of:
talagent[205]: CoreAnimation: rendering error 506
with the occasional
talagent[205]: CGSSetWindowShadowAndRimParametersWithStretch: Invalid window 0x34
scattered throughout. And as my computer reindexes (Scannerz causes this), I am receiving lots of:
mdworker[1637]: CoreData: error: (264) attempt to write a readonly database
mixed with lots of other mdworker and sandboxd-related errors. If this is all completely unrelated, I might have to start a new topic for it. :sigh:

------------------------

Review

Problem: Computer randomly disconnects from the hard drive so that I am unable to save to disk, though the system otherwise appears functional. There is no consistent interval between these crashes, but it probably averages about once every 2-3 days. Has lasted up to 8 days before. If I can make it 14 days, I will consider the problem solved.

Symptoms: Inconsistent, but I usually know that my drive will fail to save after -ONE- of the following occurs:

1) Certain Applications (usually BetterTouchTool or MenuTab Pro) randomly crash. Word has done it too.
2) Most Applications (excluding Console) are unable to launch, and are left paralyzed in the Dock.
3) Unable to access keychain.
4) Unable to load extensions when starting Safari. (And possibly, extensions failing when Safari opens.)
5) Unable to access wifi: sometimes this is related to keychain problems (#3), but sometimes it happens when wifi simply won't work, possibly correlated with bad wifi for other Macs in the area.

When wifi fails to connect, it is the least likely of the above to be a symptom. When any of the first four occur, it almost certainly means my drive has disconnected.

Cause: Unknown. Seems to happen more when I am moving my computer between locations, but not always. (Today, I did not move my computer before this happened.) It is most likely caused by Either:

1) SSD: At first, I had no reason to believe the SSD was the problem, but later found that Scannerz was reporting some errors, that were not present when I started this thread. I reinstalled my entire system from Time Machine to the SSD, and now Scannerz reports no errors. The i/o problem persists.

*Sidenote* My SSD has a 3-year warranty, so I have plenty of time to trade it out if the SSD is still the most likely suspect.

2) Cable/Logic Board: This is still a possibility. It would explain the inconsistency, as well as the proneness to happening after moving my computer. While I was on vacation, it would happen 2-3 times a day, especially when I had my computer in my lap. It can still happen when I am sitting at a table, but it is much less frequent. But of course, correlation is not causation. (Cable is connected properly.)

3) Bad wifi/ Bad Disk Connections: I would sometimes have this problem in class, right after all the other students with Macs had wifi drop as well. It has also happened at school, shortly after I had ejected my Time Machine disk too quickly.

4) OSX 10.8.2: The problem first showed up on October 10, 2012, only a few days after the last build of 10.8.2 (October 4), which makes sense from a timing standpoint. On the other hand, very few people have reported this problem, and it has just happened again, with 10.8.3 installed. If it is a bug introduced in the October build (which I was initially hoping for) I will be waiting for a *very* long time.

5) TRIM enabled/Sudden Motion Sensor disabled: These settings are recommended for users of SSD's on a Mac. I disabled TRIM at the behest of many users here, but the problem persisted. I left TRIM disabled, however, due to the plausibility that TRIM had somehow caused data corruption on my SSD. With a full reinstall from Time Machine, plus a full reinstall of OSX (thus restoring all system files), I'm thinking it is safe to reenable TRIM (unless someone here disagrees). After trying SMS enabled/disabled, I believe this has nothing to do with it.

6) Software: So far, I have considerred BetterTouchTool, TotalFinder, SideEffects, Time Machine, and Parallels as possible suspects. I not uninstalled all of these long term, but so far, disabling some of SideEffects does not solve the problem, nor does refraining from launching Parallels, nor does reinstalling TotalFinder, BetterTouchTool, or Parallels. Disabling Time Machine does not prevent the problem either. I might be investigating Glimmerblocker soon. (see above)

7) Permissions/Disk Utility/PRAM/SMC/Safe Mode/Resetpassword Utility (for Permissions): none of these have fixed the problem.

TheBSDGuy
Mar 24, 2013, 09:34 PM
What we know for facts are the following:

1. At one point Scannerz detected bad sectors on your SSD, which in my opinion shouldn't have happened because the SSD is supposed to auto correct and catch them.

2. Mountain Lion is an extremely buggy operating system. Some of the very types of disconnects you described were similar to what I was getting with some applications, and I'm not running anything particularly intensive. Here's a list:


TextEdit crashed on me for no apparent reason
iPhoto crashes periodically
iPhoto recognizes an attached camera via USB "when it wants to" and if it does recognize it, it may not detect that photos need to be downloaded - yet another crap shoot.
iWeb ALWAYS crashes
NotePad crashes intermittently. I can't use it anyway since I'm not using iCloud or iMap
Videos in Firefox are totally screwed up - it might be fixed in a Firefox update, I don't know.
Safari Web Content has gone wild at times consuming nearly 100% of the memory
Some applications will open "Save" dialogs in the wrong work space.


That's a lot of bugs for doing trivial stuff.

To me, you have three suspects: The SSD, possible cable problems, and the operating system itself.

I don't know if you can do this, but I would get off Mountain Lion as task 1. I've also been reading about others having fairly significant problems with driver (KEXT) compatibility problems and those are serious, crash worthy bugs. I don't know if you can do that because all your backups are likely now from ML. I would try either Lion, or probably even better yet, Snow Leopard. I have none of the problems I've listed above with either of them.

If you can do task 1 and the problems persist then you know it's either the SSD, a cable, or some other problem, but at least you'll know it wasn't the OS. If the problems go away then you know it's the OS. Another thing you could do is contact SCSC's tech support and let them try and help you - you paid for Scannerz so what harm could it do to ask? They know more about this crap than we do!

There are simply too many bugs with Mountain Lion to be ignored.

ObeseSquirrel
Mar 25, 2013, 09:15 PM
What we know for facts are the following:

1. At one point Scannerz detected bad sectors on your SSD, which in my opinion shouldn't have happened because the SSD is supposed to auto correct and catch them.

2. Mountain Lion is an extremely buggy operating system. Some of the very types of disconnects you described were similar to what I was getting with some applications, and I'm not running anything particularly intensive. Here's a list:


TextEdit crashed on me for no apparent reason
iPhoto crashes periodically
iPhoto recognizes an attached camera via USB "when it wants to" and if it does recognize it, it may not detect that photos need to be downloaded - yet another crap shoot.
iWeb ALWAYS crashes
NotePad crashes intermittently. I can't use it anyway since I'm not using iCloud or iMap
Videos in Firefox are totally screwed up - it might be fixed in a Firefox update, I don't know.
Safari Web Content has gone wild at times consuming nearly 100% of the memory
Some applications will open "Save" dialogs in the wrong work space.


That's a lot of bugs for doing trivial stuff.

To me, you have three suspects: The SSD, possible cable problems, and the operating system itself.

I don't know if you can do this, but I would get off Mountain Lion as task 1. I've also been reading about others having fairly significant problems with driver (KEXT) compatibility problems and those are serious, crash worthy bugs. I don't know if you can do that because all your backups are likely now from ML. I would try either Lion, or probably even better yet, Snow Leopard. I have none of the problems I've listed above with either of them.

If you can do task 1 and the problems persist then you know it's either the SSD, a cable, or some other problem, but at least you'll know it wasn't the OS. If the problems go away then you know it's the OS. Another thing you could do is contact SCSC's tech support and let them try and help you - you paid for Scannerz so what harm could it do to ask? They know more about this crap than we do!

There are simply too many bugs with Mountain Lion to be ignored.

All that talk about kexts got me thinking… Just downloaded a program I found called "Kext Wizard" and it repairs permissions for all kexts! Just did it, and it found a lot…

… including one called "ioatafamily.kext," which apparently has something to do with hard drives. :D

I'm going to give it another go, because out of the remaining suspects, running my system from a hard drive for awhile would be the easiest, and I'm not really in the mood for that sort of thing… (DVD drive is still too finicky to run AHT. Well, maybe not now. Hoping…)

EDIT: eh… repeat runs show roughly the same number of errors, meaning it isn't repairing much… Maybe it fixed something. But at least it doesn't seem to make anything worse.

TheBSDGuy
Mar 28, 2013, 03:32 AM
I don't know if that will do the trick for you, but who knows, it might. If it doesn't I'd SERIOUSLY contact SCSC for tech support. I'm serious. They're located about 7 miles from where I live and they give good tech support, even if the problem ends up not being something Scannerz would have detected anyway. It's almost like getting free consulting. You paid for Scannerz, why not take advantage of all their services.

ObeseSquirrel
Apr 2, 2013, 03:00 PM
I found the problem!!!!!
It was the SATA cable.

1) I used some compressed air to clean out the disk drive. Afterwards, I was finally able to boot from the AHT disk. (re: Superdrive problems)

2) I then ran AHT on long mode, and then short mode on loop all night. No problems found.

3) I wondered whether dust had gotten caught under the logic board, causing problems similar to those in my Superdrive. Research says that dust almost never caused short circuits, but I wanted to make sure. (I have not been having overheating problems.) I sprayed the compressed air under the logic board and found some dust bunnies, but nothing major.

4) I then wondered whether I had spilled a coke or something under the board, and just didn't remember it. I was about to remove the logic board to look underneath. And when I unsnapped the SATA cable from the board, I found it…

If you look closely at the attached picture, you can see four holes in the cable; one large white one, and three small copper-colored ones. And on the plastic casing to the Superdrive, you can see what appears to be four matching burn marks. My theory is that SSD would disconnect whenever the SATA cable got bumped against the Superdrive, causing a short circuit. That would explain why the problem happened more frequently whenever the computer was moved.

I am confused about the exposed cable hitting the plastic casing, which does not seem like it would be conducive to electricity. However, I am now 99% sure that I have found the problem, and this is a HUGE relief.

Will get this thing repaired shortly. :cool:

MacRobert10
Apr 3, 2013, 05:09 AM
No, you think you have the problem solved. The problems you've been having have been multiple, unrelated to one another in some cases, and erratic.

Bad sectors or blocks on an SSD should have nothing to do with a SATA cable, or at least I don't think so. That's a bonafide media failure. The Wi-Fi problems you've been having are probably due to nothing more than the erratic nature of Wi-Fi. The erratic nature of the problem was likely why the advice given to you to "tap on the bottom of the unit was given" ... it's to try to induce a fault...it just wasn't enough to do it (perhaps if you hit it with hammer???:eek:)

I think in this case you're just one of those unlucky people ... you know, the type of guy who gets a flat tire, fixes it, thinks all is well, and then the radiator in the car spring a leak. One unlucky thing after another.

I'm going to shoot SCSC a link to this post because I think they need to add a continuous mode of testing to Scannerz in cursory mode...they seem to listen to customers, so maybe they'll do it. Who knows? If a continuous mode was added, Scannerz might have caught this problem much earlier. Just my opinion. It is, after all, doing essentially the same thing that AHT is doing, it just doesn't lock out the user from the system to get it done.

You need to be patient and see if the problem is really fixed. Based on your photo, I would say the culprit may very well be identified, but only time will tell. Your saga seems to be "everything's working fine" and then a few days later "everything's screwed up."

I will, however, give you kudos for having the b*lls to open your system up and try to isolate the problem. That's a lot more than a lot of other people would consider doing...or do it properly.

Good luck and I hope this works out for you. :cool:

ObeseSquirrel
Apr 3, 2013, 08:06 AM
No, you think you have the problem solved. The problems you've been having have been multiple, unrelated to one another in some cases, and erratic.

Bad sectors or blocks on an SSD should have nothing to do with a SATA cable, or at least I don't think so. That's a bonafide media failure. The Wi-Fi problems you've been having are probably due to nothing more than the erratic nature of Wi-Fi. The erratic nature of the problem was likely why the advice given to you to "tap on the bottom of the unit was given" ... it's to try to induce a fault...it just wasn't enough to do it (perhaps if you hit it with hammer???:eek:)

I think in this case you're just one of those unlucky people ... you know, the type of guy who gets a flat tire, fixes it, thinks all is well, and then the radiator in the car spring a leak. One unlucky thing after another.

I'm going to shoot SCSC a link to this post because I think they need to add a continuous mode of testing to Scannerz in cursory mode...they seem to listen to customers, so maybe they'll do it. Who knows? If a continuous mode was added, Scannerz might have caught this problem much earlier. Just my opinion. It is, after all, doing essentially the same thing that AHT is doing, it just doesn't lock out the user from the system to get it done.

You need to be patient and see if the problem is really fixed. Based on your photo, I would say the culprit may very well be identified, but only time will tell. Your saga seems to be "everything's working fine" and then a few days later "everything's screwed up."

I will, however, give you kudos for having the b*lls to open your system up and try to isolate the problem. That's a lot more than a lot of other people would consider doing...or do it properly.

Good luck and I hope this works out for you. :cool:

I completely agree about Scannerz having a continuous mode of some sort. It would also be nice if they had the manual available in the help file (so I don't need to search for it online), and an option for the log files to be dumped somewhere other than the Documents folder. (If there was a Preference for this, I don't remember seeing it.

I had to laugh when you said that I'm one of those unlucky people. After jiggering with the SATA cable, I had a really hard time getting my Mac to boot, and even then, it would instantly jump to "do-not-save-anything-or-access-keychain-mode." Tapping the bottom of the computer made the computer more likely to boot up. This was, sadly, the only time I was ever able to make this error repeatable, but I think it more or less confirms that I was correct. (Note: electrical tape does not fix a damaged SATA wire. :p) It's kind of funny that I'm about to replace one of the last remaining original parts to my computer.

I may have mentioned earlier that about a year ago, I was having my computer repaired (turned out to be a logic board issue), and that while my computer was gone, I had tried to boot my SSD onto my school's computer using an external Firewire drive. But instead, I heard a click, and my entire drive had been deleted. At the time I had blamed Lion, so I ignored my prior experience and decided to give it another go.

*click

So now my SSD is most likely erased (again), and I am currently working from an HDD on the external Firewire. (Must have been a firmware incompatibility on the SSD. Why does it have to erase things, though?) Luckily, I have a Time Machine backup that I can restore from. But I'm thinking that if you are correct that my SSD is genuinely in trouble, now would be a good time to take advantage of that 3 year warranty...

MacRobert10
Apr 4, 2013, 02:19 AM
Ya know, that's about the tenth time I've read a post on this or other sites about SSDs suddenly losing all their data.

Rule number 1 for SSDs: Make sure you do daily backups

ObeseSquirrel
Apr 4, 2013, 09:24 AM
Ya know, that's about the tenth time I've read a post on this or other sites about SSDs suddenly losing all their data.

Rule number 1 for SSDs: Make sure you do daily backups

I honestly think this was an incompatibility issue of some kind, that won't affect my performance once the drive is in my computer. It just means that I should never use this drive externally.

I did send a Return to Manufacturer request to Corsair over the bad sectors issue, and also reported the drive-erase, so that maybe they can update their firmware.

The problem is that by the time they respond, I will probably have my new SATA cable, and I don't want to mess with Time Machine again only to end up replacing the drive anyway, as there's always something that doesn't copy right. (This last time, I had to reinstall all the printers.)

ugh... first world problems

smithrh
Apr 6, 2013, 10:04 AM
No, you think you have the problem solved. The problems you've been having have been multiple, unrelated to one another in some cases, and erratic.


Been a troubleshooter for a lot of things over the years, professionally as well as personally, and it sounds like you may be surprised at how one problem can be the root of many - or all - problems that you're having.

The fact is that a bad cable to a storage device can - and will - cause all sorts of weird and transient problems.

ObeseSquirrel
Apr 9, 2013, 12:24 PM
So, I installed the new SATA cable on Friday, and have not had the disk error since then. Four days is hardly enough time to say the problem is solved, especially given my recent history and the unpredictability of this error, but my thinking is that my problem is solved.

Corsair accepted my Return to Manufacture request, and will hopefully send me a new SSD sometime this week. Until then, I should am operating off of a near-clean HDD, with Mountain Lion installed, along with a few apps for minimum functionality (BetterTouchTool, 1Password).

But this morning I had a weird kernel panic. I don't think it's related to my hardware problems, but I want to mention it here just in case.

I was using Safari, when suddenly, my trackpad refused to scroll or click. My cursor would still move around though. (Briefly, the cursor froze, but then it came back.) I closed the lid on my Mac, but the light stayed lit, and the computer did not go to sleep. I reopened my computer, and my computer restarted. I saw a gray screen, that said my computer had restarted because of a problem, and then my computer was back.

Here is the panic report:

Interval Since Last Panic Report: 333609 sec
Panics Since Last Report: 1
Anonymous UUID: D3F49F46-8CAE-EA2D-34D3-6E48712BE2FE

Tue Apr 9 07:35:20 2013
panic(cpu 0 caller 0xffffff80140b7e95): Kernel trap at 0xffffff7f95804be6, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x000000000000008c, CR3: 0x0000000016d26000, CR4: 0x0000000000000660
RAX: 0x0000000000000000, RBX: 0xffffff8027a62400, RCX: 0x0000000000000003, RDX: 0x0000000000002800
RSP: 0xffffff80fbbd3780, RBP: 0xffffff80fbbd3780, RSI: 0x0000000000000003, RDI: 0xffffff8027a62400
R8: 0xffffff80fbbd33b8, R9: 0xffffff80fbbd33b0, R10: 0x0000000000000001, R11: 0x0000000000000000
R12: 0xffffff8027a68000, R13: 0xffffff80fbbd3818, R14: 0xffffff8027b2e800, R15: 0x0000000000020000
RFL: 0x0000000000010206, RIP: 0xffffff7f95804be6, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x000000000000008c, Error code: 0x0000000000000002, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff80fbbd3420 : 0xffffff801401d626
0xffffff80fbbd3490 : 0xffffff80140b7e95
0xffffff80fbbd3660 : 0xffffff80140cd4dd
0xffffff80fbbd3680 : 0xffffff7f95804be6
0xffffff80fbbd3780 : 0xffffff7f957f3e73
0xffffff80fbbd37b0 : 0xffffff7f9581a2cc
0xffffff80fbbd37c0 : 0xffffff7f95816fb5
0xffffff80fbbd3900 : 0xffffff7f95815c10
0xffffff80fbbd3d30 : 0xffffff7f957c220a
0xffffff80fbbd3d60 : 0xffffff7f95817de1
0xffffff80fbbd3da0 : 0xffffff7f957c4c6d
0xffffff80fbbd3de0 : 0xffffff7f957e1b9c
0xffffff80fbbd3e10 : 0xffffff7f957bd773
0xffffff80fbbd3e40 : 0xffffff7f946c03a0
0xffffff80fbbd3e80 : 0xffffff7f946c150a
0xffffff80fbbd3ef0 : 0xffffff80144467a8
0xffffff80fbbd3f30 : 0xffffff80144452aa
0xffffff80fbbd3f80 : 0xffffff80144453d9
0xffffff80fbbd3fb0 : 0xffffff80140b2977
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7f946b4000->0xffffff7f946ebfff
dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f94666000
com.apple.GeForce(8.1)[A15BB65E-3501-340F-87CB-2FD2BAD33E35]@0xffffff7f957ba000->0xffffff7f95886fff
dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f9470b000
dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7f946f7000
dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f94666000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7f946b4000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
12D78

Kernel version:
Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6
Kernel slide: 0x0000000013e00000
Kernel text base: 0xffffff8014000000
System model name: MacBookPro7,1 (Mac-F222BEC8)

System uptime in nanoseconds: 193761816834889
last loaded kext at 164935062230569: com.apple.driver.CoreStorageFsck 296.16 (addr 0xffffff7f963f3000, size 98304)
last unloaded kext at 165012383409769: com.apple.driver.AppleUSBCDC 4.1.23 (addr 0xffffff7f963f0000, size 12288)
loaded kexts:
com.apple.filesystems.smbfs 1.8
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.iokit.IOBluetoothSerialManager 4.1.3f3
com.apple.filesystems.autofs 3.0
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AGPM 100.12.87
com.apple.driver.AppleHDA 2.3.7fc4
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.ApplePolicyControl 3.3.0
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.GeForce 8.1.0
com.apple.driver.AppleBacklight 170.2.5
com.apple.driver.AppleUpstreamUserClient 3.5.10
com.apple.driver.AppleMCCSControl 1.1.11
com.apple.driver.AppleMikeyHIDDriver 122
com.apple.driver.AppleSMCLMU 2.0.3d0
com.apple.driver.AppleMikeyDriver 2.3.7fc4
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport 4.1.3f3
com.apple.driver.AppleLPC 1.6.0
com.apple.driver.SMCMotionSensor 3.0.3d1
com.apple.driver.AppleUSBTCButtons 237.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 34
com.apple.driver.AppleIRController 320.15
com.apple.driver.AppleUSBTCKeyboard 237.1
com.apple.driver.AppleUSBCardReader 3.1.7
com.apple.iokit.SCSITaskUserClient 3.5.5
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.3.1
com.apple.iokit.AppleBCM5701Ethernet 3.6.0b1
com.apple.driver.AirPort.Brcm4331 614.20.16
com.apple.driver.AppleFWOHCI 4.9.6
com.apple.driver.AppleUSBHub 5.5.5
com.apple.driver.AppleAHCIPort 2.5.1
com.apple.driver.AppleUSBEHCI 5.5.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleUSBOHCI 5.2.5
com.apple.driver.AppleEFINVRAM 1.7
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleACPIButtons 1.7
com.apple.driver.AppleSMBIOS 1.9
com.apple.driver.AppleACPIEC 1.7
com.apple.driver.AppleAPIC 1.6
com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0
com.apple.nke.applicationfirewall 4.0.39
com.apple.security.quarantine 2
com.apple.driver.AppleIntelCPUPowerManagement 196.0.0
com.apple.driver.CoreStorage 296.16
com.apple.iokit.IOSerialFamily 10.0.6
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 2.3.7fc4
com.apple.iokit.IOAudioFamily 1.8.9fc11
com.apple.kext.OSvKernDSPLib 1.6
com.apple.iokit.IOSurface 86.0.4
com.apple.iokit.IOBluetoothFamily 4.1.3f3
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleGraphicsControl 3.3.0
com.apple.nvidia.nv50hal 8.1.0
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.NVDAResman 8.1.0
com.apple.driver.AppleSMBusController 1.0.11d0
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport 4.1.3f3
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.driver.AppleHDAController 2.3.7fc4
com.apple.iokit.IOHDAFamily 2.3.7fc4
com.apple.driver.AppleSMBusPCI 1.0.11d0
com.apple.driver.IOPlatformPluginFamily 5.3.0d51
com.apple.iokit.IONDRVSupport 2.3.7
com.apple.iokit.IOGraphicsFamily 2.3.7
com.apple.driver.AppleSMC 3.1.4d2
com.apple.driver.AppleUSBMultitouch 237.3
com.apple.iokit.IOUSBHIDDriver 5.2.5
com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.5
com.apple.iokit.IOUSBMassStorageClass 3.5.1
com.apple.driver.AppleUSBMergeNub 5.5.5
com.apple.driver.AppleUSBComposite 5.2.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.5
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.5.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.5
com.apple.iokit.IOEthernetAVBController 1.0.2b1
com.apple.iokit.IO80211Family 522.4
com.apple.iokit.IONetworkingFamily 3.0
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOUSBUserClient 5.5.5
com.apple.iokit.IOAHCIFamily 2.3.1
com.apple.iokit.IOUSBFamily 5.5.5
com.apple.driver.NVSMU 2.2.9
com.apple.driver.AppleEFIRuntime 1.7
com.apple.iokit.IOHIDFamily 1.8.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 220.2
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.DiskImages 345
com.apple.iokit.IOStorageFamily 1.8
com.apple.driver.AppleKeyStore 28.21
com.apple.driver.AppleACPIPlatform 1.7
com.apple.iokit.IOPCIFamily 2.7.3
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
System Profile:
Model: MacBookPro7,1, BootROM MBP71.0039.B0E, 2 processors, Intel Core 2 Duo, 2.4 GHz, 8 GB, SMC 1.62f7
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463531323634485A2D3147314431
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463531323634485A2D3147314431
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.16)
Bluetooth: Version 4.1.3f3 11349, 2 service, 18 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: FUJITSU MJA2320BH G1, 320.07 GB
Serial ATA Device: HL-DT-ST DVDRW GS23N
USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24600000 / 2
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0x26100000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06600000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8213, 0x06610000 / 5
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x06500000 / 3
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0x06300000 / 2


Again, I do not think this is related, but when my computer reloaded all my closed apps, my most recent browser tabs were not available in Safari, and this gave me pause. (given the way the i/o errors had occurred).

If anybody understands these logs better than I do, please feel free to interject.

MacRobert10
Apr 11, 2013, 05:47 AM
I'd write that off as a YAMLB (yet another Mountain Lion bug) problem.

The fault is video related. From the logs the system is a MacBook Pro 7,1 which uses an NVIDIA GeForce 320M, and the very first messages in the log are all related to the card. The reason the tabs weren't saved is because the status gets saved periodically and on closing an app.

Unless this appears again and again, I wouldn't worry about it yet.

ObeseSquirrel
Apr 14, 2013, 04:02 PM
I'd write that off as a YAMLB (yet another Mountain Lion bug) problem.

The fault is video related. From the logs the system is a MacBook Pro 7,1 which uses an NVIDIA GeForce 320M, and the very first messages in the log are all related to the card. The reason the tabs weren't saved is because the status gets saved periodically and on closing an app.

Unless this appears again and again, I wouldn't worry about it yet.

After 5 days of running my Macbook normally, I had a similar error again! This time, my cursor froze altogether, and the lap top would not go to sleep. I restarted the computer manually, and no kernel bug report showed up. Here's the Console log:

4/14/13 12:32:02.310 PM mDNSResponder[47]: 110: Could not write data to clientPID[-1]() because of error - aborting connection
4/14/13 12:32:02.314 PM mDNSResponder[47]: 110: DNSServiceGetAddrInfo v4v6 3999.voxcdn.com. PID[-1]()
4/14/13 12:32:02.314 PM mDNSResponder[47]: 111: Could not write data to clientPID[-1]() because of error - aborting connection
4/14/13 12:32:02.320 PM mDNSResponder[47]: 111: DNSServiceGetAddrInfo v4v6 3999.voxcdn.com. PID[-1]()
4/14/13 12:32:02.320 PM mDNSResponder[47]: 112: Could not write data to clientPID[-1]() because of error - aborting connection
4/14/13 12:32:02.324 PM mDNSResponder[47]: 112: DNSServiceGetAddrInfo v4v6 3999.voxcdn.com. PID[-1]()
4/14/13 12:33:04.050 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 12:39:53.896 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 12:40:49.045 PM 1Password Helper[214]: Failed to return databaseID, encryption key is not loaded
4/14/13 12:44:22.120 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 12:44:25.486 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 12:45:09.077 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 12:53:15.440 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:02:06.223 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:11:51.729 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:23:18.583 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:35:28.652 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:38:54.246 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:41:00.151 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:41:05.078 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:41:38.575 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:48:03.506 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:48:06.719 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:48:49.519 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:48:50.743 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:50:45.898 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:51:45.168 PM netbiosd[70]: name servers down?
4/14/13 1:51:53.801 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:52:46.214 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:40.193 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:41.480 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:42.007 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:43.421 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:47.473 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:48.644 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:51.221 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:00:00.083 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:09:24.109 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:12:12.311 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:16:53.185 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:19:16.222 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:21:58.010 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:25:12.634 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:25:50.191 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:30:17.864 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:39:26.157 PM WindowServer[69]: CoreAnimation: context hosting changed while locked!
4/14/13 2:39:52.501 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:40:22.247 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:40:27.571 PM WindowServer[69]: CoreAnimation: context hosting changed while locked!
4/14/13 2:40:41.147 PM WindowServer[69]: CoreAnimation: context hosting changed while locked!
4/14/13 2:41:43.197 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:43:37.586 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:44:27.896 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:44:30.097 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:00:17.624 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:00:57.553 PM com.apple.usbmuxd[35]: _heartbeat_failed heartbeat detected detach for device 0x35c-192.168.1.65:0!
4/14/13 3:04:46.470 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:08:03.146 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:08:18.158 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:11:02.340 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:11:24.989 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:13:56.158 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:15:09.912 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:15:53.014 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:21:23.417 PM com.apple.usbmuxd[35]: _heartbeat_failed heartbeat detected detach for device 0x364-192.168.1.65:0!
4/14/13 3:22:58.408 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:24:57.606 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:26:12.056 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:26:16.752 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:28:16.100 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:28:29.408 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:29:06.271 PM talagent[154]: CGSSetWindowShadowAndRimParametersWithStretch: Invalid window 0x20
4/14/13 3:29:06.275 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.289 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.306 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.323 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.339 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.356 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.372 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.389 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.405 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.422 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.439 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.457 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.471 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.489 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.504 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.521 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.568 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.605 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.639 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.687 PM talagent[154]: CoreAnimation: rendering error 506
[I deleted 25 lines of this same dialogue for the word count.]
4/14/13 3:29:07.684 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.719 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.767 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.802 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.850 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.886 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.933 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.968 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.016 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.051 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.099 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.133 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.182 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.217 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.265 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.301 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.349 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.383 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.431 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.466 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.514 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.553 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.597 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.665 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.686 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.729 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.759 PM talagent[154]: CGSSetWindowShadowAndRimParametersWithStretch: Invalid window 0x20
4/14/13 3:29:08.771 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.780 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.802 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.813 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.830 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.846 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.867 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.884 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.906 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.922 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.934 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.950 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.970 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.983 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:09.000 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.580 PM talagent[154]: CGSSetWindowShadowAndRimParametersWithStretch: Invalid window 0x20
4/14/13 3:29:10.581 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.611 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.627 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.644 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.660 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.677 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.693 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.710 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.727 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.743 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.761 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.777 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.794 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.810 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.826 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.862 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.910 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.945 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.993 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.028 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.075 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.111 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.159 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.194 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.241 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.277 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.324 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.360 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.408 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.454 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.490 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.525 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.573 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.609 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.656 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.693 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.740 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.775 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.823 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.873 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.908 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.956 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.991 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.039 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.073 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.122 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.157 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.205 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.240 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.288 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.323 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.371 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.406 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.470 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.487 PM talagent[154]: CGSSetWindowShadowAndRimParametersWithStretch: Invalid window 0x20
4/14/13 3:29:12.488 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.505 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.520 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.537 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.554 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.569 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.586 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.603 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.620 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.637 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.653 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.670 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.686 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.705 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.720 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.736 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:33.434 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:29:58.125 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:40:01.037 PM WindowServer[69]: Created shield window 0x1ec6 for display 0x042730c0
4/14/13 3:40:01.037 PM WindowServer[69]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
4/14/13 3:40:01.069 PM WindowServer[69]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
4/14/13 3:41:57.287 PM WindowServer[69]: handle_will_sleep_auth_and_shield_windows: no lock state data
4/14/13 3:41:57.290 PM WindowServer[69]: Created shield window 0x1ec7 for display 0x003f003d
4/14/13 3:41:57.290 PM WindowServer[69]: handle_will_sleep_auth_and_shield_windows: no lock state data
4/14/13 3:42:07.646 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:44:16.000 PM kernel[0]: NVDA(OpenGL): Channel exception! exception type = 0x1a = Fifo: FBISTATE Timeout Error
4/14/13 3:44:16.000 PM kernel[0]: IOVendorGLContext::ReportGPURestart
4/14/13 3:44:36.000 PM kernel[0]: NVDA(OpenGL): Channel timeout!
4/14/13 3:45:10.000 PM kernel[0]: PM notification timeout (pid 54, hidd)
4/14/13 3:45:10.000 PM kernel[0]: PM notification timeout (pid 9613, BetterTouchTool)


This seems to be related to the GPU somehow, but I cannot tell whether it is hardware or software-related. (PLEASE be the software!!!)

Importantly, this error seems distinct from my earlier i/o problems. I have had graphics freezes in Mountain Lion before (usually related to Dashboard), but never this frequently. I first noticed these endless pages of "CoreAnimation" entries shortly after returning from my vacation/installing 10.8.3.

If anybody understands these console logs, please help me with this!

swingerofbirch
Apr 14, 2013, 07:37 PM
I created a very similar thread in the early morning hours today. I discovered this afterward or I would have added my post here. Here is my original post and also a link to it:

http://forums.macrumors.com/showthread.php?t=1570454

I have a 2012 13" MBP with a Samsung 830 256 GB SSD.

Just tonight, I tried taking a screenshot and got a message that I did not have permission to. I then tried saving open files and was told there was an error.

Creating a new folder in the Finder caused a -50 error.

I tried rebooting and got to the Apple logo with spinning wheel but it never went anywhere. No error messages.

So, I restarted to Recovery Mode (Command-R). I opened Disk Utility from there, and it told me that there were errors with both the HD (listed as Samsung) and with Macintosh HD. The Macintosh HD error had something to do with the Journal. It could not be repaired.

So, I booted to a cloned drive I had made with SuperDuper. It booted very slowly and beachballed and my internal HD did not show up.

On a whim I decided to run Disk Utility from the cloned drive on the internal drive, and it again found errors but fixed them! I was so relieved (I do have a back-up clone but it's not terribly recent).

I could see the internal Macintosh HD and all the files appear to be there. I tried restarting to the internal drive, but it just stays on the spinning wheel.

I restarted back to the clone, and it still shows the internal drive. I verified it again, and it says the drive is OK.

So, it seems like I should be able to back-up my data tomorrow (I want to wait till I get a new drive because I don't want to write over the data on my cloned drive in case it corrupts what I already have saved).

But I'm wondering if once I back up, erase, and re-install my internal drive, assuming it works, should I trust it?

I have a few theories:

I do record a lot of video and use the drive pretty heavily. Could I have depleted the write cycles in 8 months of heavy use?

Could it be another hardware error on the computer that caused the drive to corrupt? The reason I ask is that this computer previously had the SATA cable between the hard drive and logic board fail, and I had similar problems where the computer wouldn't boot. On the MacBook Pro I had before this one, that same part failed 3 times! It seems to be a pattern for me that I have SATA cables fail.

Could it have been a software bug? The computer had some weird quirks since I got it back from my last repair. The repair depot installed Lion on it, even though it came with Mountain Lion. I upgraded it to Mountain Lion instead of doing a clean install. Something was odd with permissions in that I couldn't update iLife apps through the Mac App Store because it said that I had updates for a different user. I could never figure out what to do about that, but I always assumed it was a permissions issue, possibly caused by the depot installing Lion on a computer designed for Mountain Lion and possibly also installing iLife apps that had been registered to the depot instead of me. I don't know . . .

I guess I'll figure out the answers to my own questions once I back-up, erase, and reinstall OS X on the internal drive and see if it boots. I'm just worried that even if it does work, that it may still be failing and corrupt again due to either the SSD failing or due to something else like the SATA cable.

Any thoughts?

Thank you. Sorry I wrote so much. This got me so anxious, I didn't realize how much I wrote--I literally penned this out in a couple of minutes and the words got away from me!

----------

EDIT:

When I tried selecting the Macintosh HD as the start-up disk from Startup Disk under System Preferences I got this message:

You can’t change the startup disk to the selected disk.

The bless tool was unable to set the current boot disk.

That seems like an odd message for a disk that shows up OK under disk utility.

Is this a clue as to what's wrong?

ObeseSquirrel
Apr 14, 2013, 10:41 PM
I created a very similar thread in the early morning hours today. I discovered this afterward or I would have added my post here. Here is my original post and also a link to it:

http://forums.macrumors.com/showthread.php?t=1570454

I have a 2012 13" MBP with a Samsung 830 256 GB SSD.

Just tonight, I tried taking a screenshot and got a message that I did not have permission to. I then tried saving open files and was told there was an error.

Creating a new folder in the Finder caused a -50 error.

I tried rebooting and got to the Apple logo with spinning wheel but it never went anywhere. No error messages.

So, I restarted to Recovery Mode (Command-R). I opened Disk Utility from there, and it told me that there were errors with both the HD (listed as Samsung) and with Macintosh HD. The Macintosh HD error had something to do with the Journal. It could not be repaired.

So, I booted to a cloned drive I had made with SuperDuper. It booted very slowly and beachballed and my internal HD did not show up.

On a whim I decided to run Disk Utility from the cloned drive on the internal drive, and it again found errors but fixed them! I was so relieved (I do have a back-up clone but it's not terribly recent).

I could see the internal Macintosh HD and all the files appear to be there. I tried restarting to the internal drive, but it just stays on the spinning wheel.

I restarted back to the clone, and it still shows the internal drive. I verified it again, and it says the drive is OK.

So, it seems like I should be able to back-up my data tomorrow (I want to wait till I get a new drive because I don't want to write over the data on my cloned drive in case it corrupts what I already have saved).

But I'm wondering if once I back up, erase, and re-install my internal drive, assuming it works, should I trust it?

I have a few theories:

I do record a lot of video and use the drive pretty heavily. Could I have depleted the write cycles in 8 months of heavy use?

Could it be another hardware error on the computer that caused the drive to corrupt? The reason I ask is that this computer previously had the SATA cable between the hard drive and logic board fail, and I had similar problems where the computer wouldn't boot. On the MacBook Pro I had before this one, that same part failed 3 times! It seems to be a pattern for me that I have SATA cables fail.

Could it have been a software bug? The computer had some weird quirks since I got it back from my last repair. The repair depot installed Lion on it, even though it came with Mountain Lion. I upgraded it to Mountain Lion instead of doing a clean install. Something was odd with permissions in that I couldn't update iLife apps through the Mac App Store because it said that I had updates for a different user. I could never figure out what to do about that, but I always assumed it was a permissions issue, possibly caused by the depot installing Lion on a computer designed for Mountain Lion and possibly also installing iLife apps that had been registered to the depot instead of me. I don't know . . .

I guess I'll figure out the answers to my own questions once I back-up, erase, and reinstall OS X on the internal drive and see if it boots. I'm just worried that even if it does work, that it may still be failing and corrupt again due to either the SSD failing or due to something else like the SATA cable.

Any thoughts?

Thank you. Sorry I wrote so much. This got me so anxious, I didn't realize how much I wrote--I literally penned this out in a couple of minutes and the words got away from me!

----------

EDIT:

When I tried selecting the Macintosh HD as the start-up disk from Startup Disk under System Preferences I got this message:

You can’t change the startup disk to the selected disk.

The bless tool was unable to set the current boot disk.

That seems like an odd message for a disk that shows up OK under disk utility.

Is this a clue as to what's wrong?

This seems much more serious than my problem ever was, as you are showing actual drive corruption. I suppose one of the first things I would do is check your drive's warranty and see if they will replace it.

Also, maybe take a good look at your SATA cable like I did, though my error was distinctly different than yours appears to be. (Mine would work fine for several days, then would "disconnect" randomly, correlated with movement of the laptop.)

You might want to try running Scannerz, as this helped me some.
Consistent errors in the same places=problem with the drive.
Inconsistent errors = hardware problem
(though my hardware issue was rare enough that even Scannerz didn't pick it up, but it did find some errors in the drive.)

In any case, I think you will be best served resolving this issue in your own thread, as this one has already gotten pretty bogged down in my own issues, which may very well be completely different.

Best of luck to you. :)