10.8.2: Randomly Unable to Save to Hard Drive

[ObeseSquirrel]

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. When I do a Google search, the "screenshot" messages appear common for people with sleep problems.

 

[benthewraith]

That isn't me. 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.

 

[smithrh]

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.

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]

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]

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]

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]

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]

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:ostMessage 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 utirg.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:owerChange: 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:ostMessage 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:owerChange: 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:ostMessage 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:owerChange: 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:ostMessage 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:owerChange: 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:ostMessage 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:owerChange: 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:ostMessage 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:owerChange: 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:ostMessage 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:owerChange: 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:ostMessage 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:owerChange: 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]

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:ostMessage 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:owerChange: 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:ostMessage 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:owerChange: 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]

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]

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]

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]

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]

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]

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]

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 With Scannerz.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]

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 With Scannerz.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]

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!!!!

 

[ObeseSquirrel]

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!!!!

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]

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]

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]

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]

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]

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! 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]

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.