I have the 2012 macbook pro with retina display (bough it aug 2012)
basically i use it to browse the web and documents when necessary.
At 1st it took less than a minute to boot up but since jan 2013 idk what has happen
This is annoying how can I fix this?
MacBook Pro with Retina display, Mac OS X (10.7.4)
First
Emergency backup procedure
Drag and drop copy your users file folders (music, pictures, documents etc) to a regular external powered drive as soon as possible.
Do not use, setup or trust only TimeMachine at this troubled time as it will copy corrupted data and we need just your users files safe just in case. TimeMachine cannot be used with a Windows PC.
Unmount and Disconnect all external drives once the backup process is completed.
Note:
If you have any over 4GB sized files, those won't copy to a standard formatted FAT32/MSDOS drive from the factory, if you need to save these 4GB+ files use another blank/empty drive and use Disk Utility to format it 1 Partition, Option: GUID, Format: OS X Extended Journaled (or the standard default one for older Mac's).
Mac's cannot copy to nor format a NTFS drive. ExFAT format to be used with a Windows machine must be right click formatted by Windows, not OS X (does it wrong) XP macines can install a free exFAT update from Microsoft. Vista-Win 8 can format exFAT.
Formatting a drive will erase all data on it.
Next check out these possible causes
Repair your machine
..Step by Step to fix your Mac
If you want to provide more details for a better evaluation provide the data here on this thread
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Select the messages logged after the boot, during the time something abnormal was happening. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
For example, if the problem is a slow startup taking three minutes, post the messages timestamped within three minutes after the boot time, not before. Please include the BOOT_TIME message at the beginning of the log extract.
If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.
ds store wrote:
. . .
Drag and drop copy your users file folders (music, pictures, documents etc) to a regular external powered drive as soon as possible.
Do not use, setup or trust only TimeMachine at this troubled time as it will copy corrupted data and we need just your users files safe just in case.
What are you talking about?
If files are corrupted, they're corrupted. Drag & drop may not copy them, and sure won't fix them. Neither will a clone.
Time Machine usually won't copy things that can't be indexed, or that result in I/O errors.
Sorry my internet was down here goes
7/17/13 9:03:40.062 AM com.apple.launchd *** launchd[1] has started up. ***
7/17/13 9:09:48.468 AM com.apple.launchd (com.apple.powerd) Unknown value for key POSIXSpawnType: Interactive
7/17/13 9:09:48.468 AM com.apple.launchd (com.apple.sandboxd) Unknown value for key POSIXSpawnType: Interactive
7/17/13 9:09:50.000 AM kernel BCM5701Enet: Ethernet address 40:6c:8f:4e:09:12
7/17/13 9:09:50.000 AM kernel AirPort_Brcm4331: Ethernet address 7c:d1:c3:80:92:2c
7/17/13 9:09:50.000 AM kernel IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
7/17/13 9:09:50.000 AM kernel IO80211Interface::efiNVRAMPublished():
7/17/13 9:09:53.512 AM com.apple.pfctl No ALTQ support in kernel
7/17/13 9:09:53.512 AM com.apple.pfctl ALTQ related functions disabled
7/17/13 9:09:57.201 AM com.apple.ucupdate.plist ucupdate: Checked 1 update, no match found.
7/17/13 9:09:57.000 AM kernel Waiting for DSMOS...
7/17/13 9:09:58.000 AM kernel macx_swapon SUCCESS
7/17/13 9:10:02.568 AM fseventsd event logs in /.fseventsd out of sync with volume. destroying old logs. (2 383 28078)
7/17/13 9:10:04.916 AM fseventsd log dir: /.fseventsd getting new uuid: 39ABAB31-C305-4BD2-AEB1-7FCC19F8CDF5
7/17/13 9:10:05.894 AM UserEventAgent starting CaptiveNetworkSupport as SystemEventAgent built Jun 25 2011 01:16:59
7/17/13 9:10:05.896 AM UserEventAgent CaptiveNetworkSupport:CreateInterfaceWatchList:2788 WiFi Devices Found. 🙂
7/17/13 9:10:05.896 AM UserEventAgent CaptiveNetworkSupport:CaptivePublishState:1211 en1 - PreProbe
7/17/13 9:10:05.897 AM UserEventAgent CaptiveNetworkSupport:CaptiveSCRebuildCache:81 Failed to get service order
7/17/13 9:10:05.897 AM UserEventAgent CaptiveNetworkSupport:CaptiveSCRebuildCache:81 Failed to get service order
7/17/13 9:10:05.897 AM UserEventAgent CaptiveNetworkSupport:CaptivePublishState:1211 en1 - PreProbe
7/17/13 9:10:05.897 AM UserEventAgent CaptiveNetworkSupport:CaptiveSCRebuildCache:81 Failed to get service order
7/17/13 9:10:05.897 AM UserEventAgent CaptiveNetworkSupport:CaptiveSCRebuildCache:81 Failed to get service order
7/17/13 9:10:09.960 AM mDNSResponder mDNSResponder mDNSResponder-320.16 (Jul 19 2012 21:07:07) starting OSXVers 11
7/17/13 9:10:10.000 AM kernel Previous Shutdown Cause: 5
7/17/13 9:10:10.000 AM kernel DSMOS has arrived
7/17/13 9:10:10.428 AM com.apple.usbmuxd usbmuxd-296.4 on Dec 21 2012 at 16:11:14, running 64 bit
Forsystem diagnostic reports
Date/Time: 2013-06-24 20:35:29 -0400
OS Version: 10.7.5 (Build 11G63)
Architecture: x86_64
Report Version: 9
Command: Wondershare Fantashow
Path: /Applications/Wondershare Fantashow.app/Contents/MacOS/Wondershare Fantashow
Version: 3.0.4 (3.0.4)
Parent: launchd [128]
PID: 750
Event: hang
Duration: 0.98s
Steps: 10 (100ms sampling interval)
Pageins: 4
Pageouts: 0
Process: Wondershare Fantashow [750]
Path: /Applications/Wondershare Fantashow.app/Contents/MacOS/Wondershare Fantashow
Architecture: i386
UID: 501
Thread 0x2153
User stack:
10 start + 53 (in Wondershare Fantashow) [0x2fc5]
10 main + 284 (in Wondershare Fantashow) [0x3192]
10 NSApplicationMain + 1054 (in AppKit) [0x9afbfac5]
10 -[NSApplication run] + 142 (in AppKit) [0x9ad2e7c0]
10 -[NSApplication finishLaunching] + 554 (in AppKit) [0x9ad2edf0]
10 -[NSNotificationCenter postNotificationName:object:] + 55 (in Foundation) [0x96a42272]
10 -[NSNotificationCenter postNotificationName:object:userInfo:] + 92 (in Foundation) [0x96a2cfde]
10 _CFXNotificationPost + 2776 (in CoreFoundation) [0x96d85688]
10 ___CFXNotificationPost_block_invoke_1 + 275 (in CoreFoundation) [0x96dba903]
10 __-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_1 + 49 (in Foundation) [0x96a41df1]
10 -[AppDelegate applicationWillFinishLaunching:] + 585 (in Wondershare Fantashow) [0xcc064]
10 -[AppDelegate loadMainWnd] + 62 (in Wondershare Fantashow) [0xcd037]
10 +[MainWindowCtl SharedMainWindowCtl] + 99 (in Wondershare Fantashow) [0xfe77]
10 -[NSWindowController loadWindow] + 240 (in AppKit) [0x9af33f34]
10 +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 154 (in AppKit) [0x9ad3b0cf]
10 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 235 (in AppKit) [0x9ad3b1c5]
10 loadNib + 380 (in AppKit) [0x9ad3bdde]
10 -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1389 (in AppKit) [0x9ad460a9]
10 -[MainWindowCtl awakeFromNib] + 2258 (in Wondershare Fantashow) [0x10de6]
10 -[NSViewController loadView] + 212 (in AppKit) [0x9ae6a296]
10 -[NSNib instantiateNibWithOwner:topLevelObjects:] + 304 (in AppKit) [0x9ae6ae20]
10 -[NSNib instantiateNibWithExternalNameTable:] + 652 (in AppKit) [0x9ae6b0e1]
10 -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1389 (in AppKit) [0x9ad460a9]
10 -[MessageViewController awakeFromNib] + 1067 (in Wondershare Fantashow) [0xb8616]
10 -[MessageViewController fetchMessage] + 122 (in Wondershare Fantashow) [0xb8852]
10 clientID + 95 (in Wondershare Fantashow) [0x88e7f]
10 fread + 65 (in libsystem_c.dylib) [0x91fb301f]
10 __fread + 217 (in libsystem_c.dylib) [0x91fb3110]
10 __srefill1 + 34 (in libsystem_c.dylib) [0x91fb2465]
10 _sread + 35 (in libsystem_c.dylib) [0x91fb1f0e]
10 __read_nocancel + 10 (in libsystem_kernel.dylib) [0x9cee3a62]
Kernel stack:
10 hndl_unix_scall + 281 (in mach_kernel) [0xffffff80002daa79]
10 unix_syscall + 472 (in mach_kernel) [0xffffff80005cde98]
10 read_nocancel + 120 (in mach_kernel) [0xffffff80005655c8]
10 write + 209 (in mach_kernel) [0xffffff8000564ec1]
10 read + 4590 (in mach_kernel) [0xffffff80005667ee]
10 msleep + 119 (in mach_kernel) [0xffffff8000556217]
10 wakeup + 267 (in mach_kernel) [0xffffff8000555bbb]
10 lck_mtx_sleep + 74 (in mach_kernel) [0xffffff8000227efa]
10 thread_block_reason + 299 (in mach_kernel) [0xffffff800022f42b]
10 thread_continue + 1661 (in mach_kernel) [0xffffff800022f1ad]
10 machine_switch_context + 361 (in mach_kernel) [0xffffff80002c2939]
Thread 0x2160 DispatchQueue 1701273966
User stack:
10 _dispatch_mgr_thread + 53 (in libdispatch.dylib) [0x9487c853]
10 kevent + 10 (in libsystem_kernel.dylib) [0x9cee490a]
Kernel stack:
10 kqueue_scan + 416 (in mach_kernel) [0xffffff800053b4d0]
Please read this whole message before doing anything.
Triple-click the line of text below on this page to select it:
kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -f -a TextEdit
Repeat with this line:
{ sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; sudo defaults read com.apple.loginwindow LoginHook; sudo crontab -l; } 2> /dev/null | open -f -a TextEdit
{ launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)/{print $3}'; crontab -l 2> /dev/null; } | open -f -a TextEdit
ls -1A /e*/{la,mach}* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts .la* 2> /dev/null | open -f -a TextEdit
osascript -e 'tell application "System Events" to get name of every login item' | open -f -a TextEdit
You can then quit Terminal.
It seems that many people have same issues (me too). After upgrading in 10.8.3 many MacBooks pro needing more than 5 minutes to boot. It has something to do with the internal sd drive. By some people the problem is fixed when they remove the sd card from card-reader by other by placing a sd card in reader. Apple must solve this problem!!!!
Macbook pro takes 7 minutes to boot up
