Gray logo after upgrading from Snow Leopard 10.6.8 to mavericks

is there any way to fix this, and i don't have the recovary cd for Snow Leopard.

OS X Mavericks: Erase and reinstall OS X
Erase your Mac, then reinstall OS X using the built-in recovery disk. Before you erase, back up your essential files. If you’re installing on a portable computer, make sure your power adapter is plugged in.
Important: To reinstall OS X, you must be connected to the Internet.
Choose Apple menu > Restart. Once your Mac restarts (and the gray screen appears), hold down the Command (⌘) and R keys.
If you’re not connected to the Internet, choose a network from the Wi-Fi menu (in the top-right corner of the screen).
Select Disk Utility, then click Continue.
Select your startup disk on the left, then click the Erase tab.
Choose Mac OS Extended (Journaled) from the Format menu, enter a name, then click Erase.
After the disk is erased, choose Disk Utility > Quit Disk Utility.
Select Reinstall OS X, click Continue, then follow the onscreen instructions. Reinstall OS X

Similar Messages

I have a big problem with Lion and PGP. After upgrading from snow leopard to lion I cannot access my PGP drive which was generated under snow leopard. PGP does not start but gives a notion that lion cannot work with my PGP version. Solution?

After upgrading from Snow Leopard to Lion I cannot access a PGP drive which was generated under snow leopard. PGP does not start. When I try to start I just receive a message that Lion cannot work with PGP. How can I now access important and confifential informatio which I have stored in PGP (snow leopard). Do I have to move back to snow leopard. If so, how can I do this?

If you have this product,
http://www.symantec.com/business/support/index?page=content&id=TECH165159
you have to go back to Snow Leopard.
To re-install SL, back up your home directory, format and re-install.

After upgrade from snow leopard to lion, where is application front row?

After upgrade from snow leopard to lion, where is application front row? i realize it when to use my remote. any one knows about this matter?

OK - Fixed it.
Turns out the cure is to use the Webcal Interface to re-create the delegations. A bit tedious, but doing this presumably forces a rewrite of the file that previously cannot be accessed. Means you need to set up the delegation again for each account - but this at least is an improvement over not being able to do anything at all.
Once fixed, delegation works just fine.
Hope this helps someone else solve the issue etc.

After upgrading from Snow Leopard to Mountain Lion, the text preference, Middle Eastern, causes Photoshop CS6 to slow down. Can this be fixed?

After upgrading from Snow Leopard to Mountain Lion, and setting the text preference, Middle Eastern, causes Photoshop CS6 to slow down. Can this be fixed?

I'm Win, not Mac, but I do have a couple saved messages
Mac 10.8.3 Bug w/Encore and BluRay http://forums.adobe.com/thread/1198709
-create folder not ISO http://forums.adobe.com/thread/1216127

Will i have problem upgrading from Snow Leopard 10.6.8 to Maverick ?

will i have problem upgrading from Snow Leopard 10.6.8 to Maverick ?

Impossible to know. But I would make a backup before doing so, just in case. I would also do the following:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
If you wish to save yourself a lot time should you need to reinstall Mavericks at some point in the future then see the following:
Make Your Own Mavericks, Mountain/Lion Installer
After downloading the installer you must first save the Install Mac OS X application. After the installer downloads DO NOT click on the Install button. Go to your Applications folder and make a copy of the installer. Move the copy into your Downloads folder. Now you can click on the Install button. You must do this because the installer deletes itself automatically when it finishes installing.
   2. Get a USB flash drive that is at least 8 GBs. Prep this flash drive as follows:
Open Disk Utility in your Utilities folder.
After DU loads select your flash drive (this is the entry with the mfgr.'s ID and size) from the leftside list. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
Select the volume you just created (this is the sub-entry under the drive entry) from the left side list.
Click on the Erase tab in the DU main window.
Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
Click on the Erase button. The format process can take up to an hour depending upon the flash drive size.
Make your own Mavericks flash drive installer using the Mavericks tool:
You can also create a Mavericks flash drive installer via the Terminal. Mavericks has its own built-in installer maker you use via the Terminal:
You will need a freshly partitioned and formatted USB flash drive with at least 8GBs. Leave the name of the flash drive at the system default, "Untitled." Do not change this name. Open the Terminal in the Utilities folder. Copy this entire command line after the prompt in the Terminal's window:
     sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume
     /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --nointeraction
Press RETURN. Enter your admin password when prompted. It will not be echoed to the screen so be careful to enter it correctly. Press RETURN, again.
Wait for the process to complete which will take quite some time. When completed it would be wise to test the installer by checking that it boots the computer and is then ready for installation.

Macbook Pro keeps on rebooting after upgrade from Snow Leopard to Mavericks.

After I upgraded from Snow Leopard to Mavericks, my early 2010 MBP keeps on rebooting after 30 secs when it's connected to LAN/WIFI. But when it's not connected to any internet source it works fine. Please help.

After I upgraded from Snow Leopard to Mavericks, my early 2010 MBP keeps on rebooting after 30 secs when it's connected to LAN/WIFI. But when it's not connected to any internet source it works fine. Please help.

Mail folders missing after upgrading from snow leopard to mavericks.

I seem to have lost my mail folders after the upgrade from Snow Leopard to Mavericks.
Are they hidden? if not is there any way to recover them from TimeMachine?
thanks

sorry, I found them: by clicking "On my Mac" - show.

Do I need to update Bootcamp 3.3 after upgrading from Snow Leopard to Mountain Lion?

Do I need to update Bootcamp 3.3 after upgrading directly from Snow Leopard to Mountain Lion? If so, what is the recommended version for my machine?
Other pros and cons we should consider? Not sure what is considered best practice.
We have a mid-2011 iMac (12,1) running Win7 64bit. Concerned about firmware updates not being compatible with Bootcamp 3.3. Firmware updates forThunderbolt port were part of post-Mountain Lion updater install. Not sure what other firmware/boot changes might have been applied to support the new recovery partition, for example. Will the 3.3 windows control panel still work safely?
Win7 still boots OK, at least for now. Backup is current.
I'd like to get the entire machine current again. Bootcamp 5.0 didn't want to download (appeared to hang writing to my external drive, which is otherwise fine). Bootcamp 4.1 refused to install on Win7 (claimed it wasn't for my machine, so I aborted. Downloaded from apple support page directly).
I've searched the forums for this specific question - I see plenty of info for upgrading Bootcamp 4 to 5, but nothing for 3 to 5.
Thanks much in advance,
-b

Appreciate the quick response.
There are basically 2 schools of thought here:
- If it ain't broke, don't fix it.
- Don't fall off the upgrade cycle (apply patches whether you have an issue or not in order to ward off trouble before it happens).
I don't have a specific issue that I'm chasing on the Win7 side right now. I'm attempting to address having fallen off the upgrade cycle by staying on Snow Leopard too long.
I appreciate that the Win7 side under bootcamp is its own thing (upgrades to Mac OS don't cross over or effect the bootcamp partition) - except where firmware upgrades coming out of Mountain Lion change the hardware interface to Win7. Hence my questions.
-b

Time machine can not access time capsule after upgrade from snow leopard to mountain lion

Two days ago I upgraded my 2009 17" MBP from Snow Leopard to Mountain Lion. That evening my time capsule/time machine combination worked fine and did an incremental backup of about 12 gigabyte. Yesterday - only one day later - the time machine backup did not work anymore.
It appears that the system can not find the time capsule - even though it shows the remaining free space on the time capsule (so it did find it after all).
The message is always the same:
Time Machine can not complete the backup "Time Capsule"
The image of the backup volume "/Volumes/Data/Pauls MacBookPro.sparsebundle" is not accessable (Error -1).
I also can not delete the backup image on the time capsule since it is read-only. And I do not want to format the time caspsule yet since my wife's MBAir is also using the same time casule.
I tried out all kinds of suggestions (hard and soft resetting both the MBP and the TC, entering the password again, setting the TC up again) all to no avail. No backup is possible anymore.

Mr. Zooot wrote:
Time Machine can not complete the backup "Time Capsule"
The image of the backup volume "/Volumes/Data/Pauls MacBookPro.sparsebundle" is not accessable (Error -1).
I also can not delete the backup image on the time capsule since it is read-only.
Sounds like you got this message earlier:
If so, see #C13 in Time Machine - Troubleshooting.
Offhand, I don't recall anyone not being able to delete one via the Finder (but most were only backing-up one Mac, so just erased the disk).
You may have to wait for that message to appear again (24 hours later), or you might try holding Alt/Option with the TM icon in the menubar, and select Verify Backups if it will let you.

Extended monitor problem after upgrade from Snow Leopard

Upon upgrading Mac Pro (09) from Snow Leopard, I can only get a black screen on my extended desktop monitor. I can see the mouse cursor, but nothing else. I am not using Full Screen. Any suggestions? The extended monitor is a SyncMaster 943. thanks.

After reading about kernel panics on this machine, I should also report that the MacPro has two Nvidia GT120's. I have not upgraded the driver manually and have not had a kernel panic (yet). Just the black screen on actually two extended desktop monitors.

ICal delegation failing after upgrade from Snow Leopard to Lion

I've just upgraded our Snow Leopard server to run Lion Server.
I have a problem with iCal Server.
Individual calendars work OK: can be accessed from iCal / iThings and so on, and via web interface. But calendar delegation doesn't.
If I open Accounts / Preferences / Delegation from any version of iCal / Calendar I get this error:
In the server calendar server error log I see the following:
[twext.web2.dav.method.report_expand#error] Error reading property (u'http://calendarserver.org/ns/', u'calendar-proxy-read-for') for resource /principals/__uids__/BCDF1D53-4447-40A2-A035-B30F6E2EEDE4/: <StatusResponse 403 Unable to list properties: /Volumes/StorageHD/Library/Server/Calendar and Contacts/Documents>
Anyone got any ideas what is going on and / or how to fix?
Thanks in advance for any help available.

OK - Fixed it.
Turns out the cure is to use the Webcal Interface to re-create the delegations. A bit tedious, but doing this presumably forces a rewrite of the file that previously cannot be accessed. Means you need to set up the delegation again for each account - but this at least is an improvement over not being able to do anything at all.
Once fixed, delegation works just fine.
Hope this helps someone else solve the issue etc.

Cannot enter Time Machine after upgrading from Snow Leopard

Hi all,
I've had Lion installed for a few days now and am enjoying the changes to OSX.
Last night I wanted to delete a few redundant files out of my TimeMachine backup and found I could not open the application at all.
I can still backup to Time Machine successfully (so it indicates with preparing, backing up progress (xGB of yGB), finishing, etc). So for the last few days everything appeared to be functioning as expected until last night, when I tried to enter Time Machine.
My specs:
iMac (Oct 2010), 4GB, 1TB, 3.6GHz, backing up to a WD My Passport Essential (1TB) via USB 2.0 (25% full)
I can see the destination drive (and its contents) on my desktop, via Finder and can select it via TimeMachine System Preferences (Select drive). There are no issues 'seeing' or accessing the drive in normal use.
Trying to open the Time Machine application, I have tried via the TimeMachine icon in the TitleBar (ie 'Enter Time Machine'), via Mission Control (double-clicking on Time Machine), typing 'Time Machine' into Spotlight and selecting it from the resulting list, but in all scenarios, nothing happens. Nothing at all. And yet I can backup to Time Machine without a hitch.
I have seen a number of online conversations about the AFP spec having been changed by Apple and third party periphial manufacturers being slow to comply, but using USB, I'm not sure this applies to my case? I have used Macs at home for 8 years and have never heard of AFP until now... So I don't really know if I am impacted by this or not (don't think so).
There have been some troubleshooting solutions involving identifying and deleting the com.apple.timemachine.plist from the Library/Preferences folder (going from memory here) which I did (had to use PathFinder to find the file).
Unfortunately that did not help and Time Machine still refuses to open. There are no errors appearing as a result of trying to open TimeMachine. I have checked the Console, but nothing obvious appears there. I have read others are prompted with an error about AFP, but I get no such error. I can copy files to the drive okay so I can't see how it is the drive. Just Time Machine not wanting to play...
Can anyone suggest anything?
I do have Snow Leopard SuperDupered to another 320GB WD drive if I need to go back, but I don't really want to if I can help it...
Thanks,
Alex Makin

Well finally, after 2 days of trying to work out what was the issue, I have resolved the problem.
Its very strange given that I can successfully back up but not restore, as described in my original post.
One thing I neglected to mention was the fact I had set up my Time Machine backup to use 'sparsebundles'. This allows me to have the external drive plugged into my Airport Extreme and use much like Time Capsule.
It didn't seem relevant at the time since I could backup successfully (and still now, I can't understand why Time Machine knows where to back up to, but doesn't know where to restore from).
I didn't have the Time Machine icon sitting in my dock (never needed to since if I need to restore, I access TM from the TitleBar icon). So in putting the TM app in the dock I played a little around with it by clicking it (as you would normally for any other app in the dock) and eventually held down the mouse key to bring up the menu. Tried 'Enter Time Machine' a couple of times without luck, before trying a menu item along the lines of "Try another backup destination' and voila!! Time Machine opens, animated stars, vertical time line, etc.
Well hang on now... Why the heck can't TM have worked this out already?? Why do I need to look somewhere else for my Time Machine backup, when I've already told TM (in System Preferences) where the backup is?
Pretty darn odd, but there you have it. It was there the whole time, but according to TM, it wasn't...
I still have to select the menu item 'Try another backup destination' each time I want to enter TM, but at least I know where to find it...
I'm assumming its the sparsebundles setting (which I'm sticking with), but at least I know its not my iMac, its not the hard drive, its not Lion (well, it sort of is as Snow Leopard knew where to find it...)
Alex Makin

Mail quits after upgrading from snow leopard to mountain lion

During installing Mountain lion I ported across my settings, but not my applications; Post installation mail quits after about 3 seconds (my emails all seem to be there). Any ideas? I have alot of emails in different mailboxes, Id disable some of the mailboxes if I could just find where mail/moutain lion keeps them
thanks in anticipation
Looking at the edited report below, it seems that there is a bad argument / suffix thing going on
Process:
Mail [2857]
Path:
/Applications/Mail.app/Contents/MacOS/Mail
Identifier:
com.apple.mail
Version:
6.2 (1499)
Build Info:
Mail-1499000000000000~1
Code Type:
X86-64 (Native)
Parent Process: launchd [411]
User ID:
501
Date/Time:
2013-01-04 16:02:33.004 +0000
OS Version:
Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report:
2308 sec
Crashes Since Last Report:
21
Per-App Interval Since Last Report: 502 sec
Per-App Crashes Since Last Report:   10
Anonymous UUID:
A1DD09C7-D315-C60E-0702-9AFEB576645E
Crashed Thread: 6 Dispatch queue: com.apple.root.default-priority
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[ABRecord setValue: '(
"2011-03-15 10:25:40 +0000",
"2012-03-16 10:33:43 +0000"
)' forKey: 'MailLastDates'] invalid value'
abort() called
terminate called throwing an exception
Application Specific Backtrace 1:
0   CoreFoundation
0x00007fff89ed40a6 __exceptionPreprocess + 198
1   libobjc.A.dylib
0x00007fff8c5c93f0 objc_exception_throw + 43
2   CoreFoundation
0x00007fff89ed3e7c +[NSException raise:format:] + 204
3   AddressBook
0x00007fff8714bf88 -[ABRecord setValue:forKey:] + 116
4   Message
0x00007fff8ed3e9a3 __42-[MFRecentsManager _updateRecentsForKeys:]_block_invoke_0 + 1147
5   Foundation
0x00007fff86131a7c -[NSBlockOperation main] + 124
6   Foundation
0x00007fff86107986 -[__NSOperationInternal start] + 684
7   Foundation
0x00007fff8610f1a1 __block_global_6 + 129
8   libdispatch.dylib
0x00007fff845b6f01 _dispatch_call_block_and_release + 15
9   libdispatch.dylib
0x00007fff845b30b6 _dispatch_client_callout + 8
10 libdispatch.dylib
0x00007fff845b41fa _dispatch_worker_thread2 + 304
11 libsystem_c.dylib
0x00007fff835eccab _pthread_wqthread + 404
12 libsystem_c.dylib
0x00007fff835d7171 start_wqthread + 13

Sorry ive fixed it. After restarting the mac, mail put the mailboxes in users; library; as per usual. I disabled some of my older mailboxes by stuffing them temporarily into the bin, and restarted mail, which worked fine, ill enable the restr of themailboxes one by one to see which one carries the bad bad argument. thanks for looking

After upgrading from snow leopard to lion, mail stuck in upgrade mode?

How do I get the upgrade to STOP so I can try to open Mail again without having to trash the application. Or is that the only way? and then how do I get the Mail application? Thanks for any help!

Go get a powered USB hub and try that. Lion may have issued a fix for devices drawing too much power, by cutting them off.

Can I avoid Iphoto problems in upgrading from Snow Leopard 10.6.8 to Mavericks?

I've read that upgrading to Mavericks involves problems with Iphoto. I have an older version of Iphoto (7.1.5). Should I upgrade to a newer version of Iphoto BEFORE I upgrade to Mavericks? If so, do I have a choice and to what version? Is there any reasonable way to avoid IPhoto difficulties in moving to Mavericks?

This screenshot shows which previous versions of iPhoto are compatible with Mavericks. It also indicates which versions qualify for a free upgrade to iPhoto 9.5.1 and which require a purchase:
Note 1: every day more users are reporting problems with iPhoto 8.1.2 so I've included it in the non compatible category.
Note 2: If your previous version of iPhoto was iPhoto 7 (08) or earlier you'll need to download and run the iPhoto Library Upgrader 1.1 application on the library before opening it with iPhoto 9.5.1.
OT

Gray logo after upgrading from Snow Leopard 10.6.8 to mavericks

Similar Messages

Maybe you are looking for