Mac OS x lion clean install problems

While trying to do a clean install of OS X lion, my macbook pro is stuck at "downloading additioal components required to install mac os x lion. though i have wifi access, there is no bandwidth usage in the whole process.. it starts with 22 minutes, goes upto 4 minutes and suddenly jumps to 5 hours and 54 minutes before showing an error message that says "cant download additional components required to install mac os x lion. Im stuck with a dead notebook.. would be grateful if anyone could give me an insight into a possible solution.

OS X Lion: Unable to download OS X Lion wireless...
OS X Lion Install to Different Drive
- About Lion Recovery options, half way down the page
Or put Lion installer on flash or DVD
How to create an OS X Lion installation disc MacFixIt
How to prepare your Mac for OS X 10.7 Lion
Also goes into use of recovery; doing a clean install

Similar Messages

Recently upgraded Mac 24" to Lion (clean install) and now no external hard disks work with Time Machine

Recently upgraded Mac 24" to Lion (clean install) and now no external hard disks work with Time Machine.
installed new internal disk first with fresh 10.7.3 Lion software. Also upgrade ram to 4GB. Work great, super fast.
BUT.... my WD 1TB firewire400 external disks no longer work with the Lion enabled machine now.
FURTHER... I read somewhere that WD is problematic with Lion but Seagate was not... so I went and bought a new 3TB Seagate GoFlex.
When it didnt work properly either, I patiently searched and found a software/firward upgrade and applied.
I re-partitioned disk to extened/journaled standard, etc.
Then assigned the particition to Time Machine. Drive turned the blue/grey color, so I thought it would work.
But, it has now been in "preparing" mode in Time Machine for HOURS....
What is up Apple? So dissappointed. Ive read these type of problems are notorious with Lion and I wish I never upgraded.
Are you trying to make issues with External disks, to drive people to iCloud? That trick ont work in me. I will not reward bad behaviour Apple.
Please provide a fix... I wasted hours/days screwing around with this, instead of using the Mac for what its intended!

Solved by Pondini, on another thread I opened...
Answer:
Sounds like either:
A directory problem on your internal HD. Verify your internal HD, and Repair any other volumes being backed-up per #A5 in Time Machine - Troubleshooting.
Something in OSX may be damaged. You've tried the "combo," so a fresh copy of OSX (that won't disturb anything else) would be worth a try (and you don't need a tech for that). See Installing the ''combo'' update and/or Reinstalling OSX.

Help with Mac OS X Lion clean install

I have a late 2008 15" MacBook Pro that has Lion installed which was upgraded over Snow Leopard. I have heard that performing a clean install can freshen up the system and is just generally a good thing to do. When I downloaded Lion from the Mac App Store I made a bootable disc because I heard it's something good to have just in case. I have also been backing up to an enxternal hard drive using Time Machine. So I was thinking about doing a clean install but I wanted to make sure of a few things and to get your thoughts on if it is actually a good idea or a waste of time.
I would format my hard drive then restart and hold down the option key, choose to boot from the disc and clean install. Once finished use Migration Assistant to move my data from the external hard drive with my Time Machine back ups and that should be everything done and dusted.
I know I have probably got something wrong somewhere and have maybe even got the completely wrong idea about the whole thing.
I would appreciate any help and advice, thanks.

Install or Reinstall Lion from Scratch
If possible backup your files to an external drive or second internal drive.
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Erase the hard drive:
Select Disk Utility from the main menu and click on the Continue button.
After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Erase tab in the DU main window.
Set the format type to Mac OS Extended (Journaled.) Click on the Erase button and wait until the process has completed.
Quit DU and return to the main menu.
Reinstall Lion: Select Reinstall Lion and click on the Install button.
Note: You can also re-download the Lion installer by opening the App Store application. Hold down the OPTION key and click on the Purchases icon in the toolbar. You should now see an active Install button to the right of your Lion purchase entry. There are situations in which this will not work. For example, if you are already booted into the Lion you originally purchased with your Apple ID or if an instance of the Lion installer is located anywhere on your computer.

After a Lion clean install, how do I retrieve my data from external back-up? Following Apple advice for use of Migration Assistant did not work creating similar issues leading to clean install.

After a Lion clean install, how do I retrieve my data from external hard drive?
Following Apple advice I used Migration Assistant which crashed new system twice which is why I had to clean install Lion in the first place.
Is there a sure way of doing it?
I have only a few programs that I will have to install myself and that should not be a problem.
I just want my data, music and photos back where I can use them.

Time machine backups. I went to migration assistant a few hours ago and limited my selection to "users", no need for applications, settings and other files. Stuff started moving over at a fast pace but has now seemed to stall.
I will let it run overnight as there are lots of songs and photos as well as a few movies.
If that does not work, then I will go into TM and try restore. I have restored some things in the past such a mail files and it has worked well.
The Apple fellow at the store told me to go right into TM, he may have had a point. I'll get it eventually.

Recent update OS10.5 to 10.6 to Lion. Using Pages (4.1) only some documents won't open. At Genius bar loaded new copy Pages; reloaded Lion clean install. Still won't open although will on another computer. What now?

Pages question: recent update OS10.5 to 10.6 to Lion. Using Pages (4.1) only some documents intermittently
won't open. At Genius bar loaded new copy Pages; reloaded Lion clean install. Still won't open although will on another computer. On the other Mac (running Lion), saved a copy of a document with a new name and sent it back to first computer. At first it would open, but now it as well as multiple other Pages documents won't open. What now?

yes;
I got Pages to work now- there were two versions, one Universal, and one Intel- by moving the Universal to trash ( although I can't delete it) and moving Intel version to iWorks folder in Applications, it is now working. Doesn't explain why it didn't work though- the other MacBook pro 17 inch that could open all the Pages documents also has two copies of Pages as I see now....
I still however can't open Numbers documents on the MacBook pro 15 inch.... it is a Universal version of Numbers.

Lion Clean Install - No Disc Required - Recovery Partition Solution

There is a way to run a Lion clean install without unpacking the installation onto a new disc or thumb drive. It can be accomplished via a slightly longer, two-step upgrade process, which requires wiping your hard drive after you've upgraded to Lion. You must be able to connect to the internet for this option to work, as it will require downloading the install package again.
As always, be sure to back up your data before performing any sort of wipe of your hard drive.
STEP 1 - Initial Upgrade
Perform a normal Lion upgrade through the App Store. This will install Lion on top of your current configuration. It will also create a Recovery Partition, which is a new feature of the Lion OS. It is this Recovery Partition that you will use to perform the clean install.
STEP 2 - Wipe and Clean Install
Restart your computer into Recovery mode. This can be done by either holding down CMD-r during boot up, or holding down the Option key during bootup and selecting to boot from the Recovery partition.
Select the Disk Utility option from the main menu. Here you can select the main partition, click on the Erase tab at the top, and completely erase the partition. Once you've done this, quit Disk Utility Option, and you will return to the main menu.
Select the Lion Installation option. It will ask you to connect to the internet if you have not done so already (if wireless, you can do this via the Wi-Fi icon in the top right corner). It will also ask you to input your Apple ID login and password in order to verify that you've already purchased the software. The installation will take as long as it requires to download the package again. Once downloaded and installed, Lion will walk you through initial set up.
This solution worked for me, but I make no guarantees that it will work for others.

I've created a boot disk (several actually) following the methods outlined in this guide.
http://www.eggfreckles.net/tech/burning-a-lion-boot-disc/
I've also saved the installer dmg in several backup locations so it can be burned again fresh or transfered to bootable USB thumb drives.
The Lion install disk boots up and operates just like the Recovery Partition (Disk Utiltiy and all) with one giant benefit, you don't have to log into the MacAppStore with all it's complications or require a lenghtly internet download to install Lion.
So you won't see this annoying screen and have to wait a few hours if the servers are overloaded.
The boot disk also installs considerably faster. Two giant benefits actually.
Also once Lion is installed, Bootcamp can be used to partition the drive, then the Recovery Partiton > Disk Utiltiy used to change the BOOTCAMP partition to HFS+ journaled and then 10.6 can be installed or cloned from a external drive onto the BOOTCAMP partition.
Dual boot Snow/Lion is possible with a large enough boot drive.

Mac lagging even after clean install of mountain lion

i have mac book pro 13" mid 2102- i7 version. it is lagging while video play back in quick time, audio in itunes, even VLC is lagging sometimes. Need for speed is lagging too. CPU usage is very low like 95% is Idle, 70% RAM is free. I reinstalled OS(with secure formatting) but problem is still there. what you guys think is causing this, RAM or HDD. i tried repairing disk permissions before clean install but no luck. itunes lags like 2-3 secs which is annoying, quicktime lags for 3-4 secs and instantly plays video very fast for 2-3 secs after that stays normal for a min
MplayerX never lagged while palying but all other itunes, vlc, quick time does.

Post an image of Activity Monitor set to ALL PROCESSES and % CPU to display values from high to low. Lets see if there is a third party app that is a problem.
This is from mine:
Do you have any 'cleaning' or 'performance' applications installed?
Start up in Safe Mode and see if there is any change:
http://support.apple.com/kb/HT1455
Ciao.

The Mac OS X Lion begins installing and then stops and gives the following error message: Mac OS X can't be installed on the disk Macintosh HD because a recovery system can't be created. How do I fix this problem?

OS X Lion begins installing and then error message comes up that it can't be installed on MacIntosh HD because a recovery system can't be created. What do I do to fix this problem?

What to do if the installer warns that no Recovery HD can be created
Some disk partition configurations may result in the OS X Lion installer reporting that it could not create a Recovery HD. In these situations, even if you are permitted to continue the install, you should quit the install and create an external, bootable OS X Lion hard drive with a Recovery HD, first. You will be able to return to the upgrade to OS X Lion on your computer's boot drive after creating the external Recovery HD.
Important notes
Your storage device must have at least 13 GB available (after formatting) to install Lion and an Internet Restore partition.
These steps will erase and reformat the storage device. OS X Lion: About Lion Recovery will instruct you on setting up the storage device to use the GUID partition scheme and the Mac OS Extended (Journaled) format, which are required to install Lion and an Internet Restore partition on your external storage device. You should back up any important files that are on the device to a different drive.
This procedure will install a version of the OS X Lion that is compatible with the Mac it was created with. Using this Lion system with a different kind of Mac may produce unpredictable results.
Your computer's serial number will be sent to Apple to help authenticate your request to download and install OS X Lion.

Persisting kernel panics with mountain lion (clean install)

hi, I could really have some help on recent kernel panics I am experiecing on my 2009 MacBook Pro with Mountain lion installed. Here and there I have been doing some reading but I am not a techy, most of it I do not understand.
Last kernel panic occured while I was copying a large file (998mb) from network storage. Before a fresh install kernel panics happend literally any time and I could not pin point any reasons.. At the moment I have no third-party software installed except Spotify...
I also have recently replaced my HDD with an SSD. Currently 8gb of 1066mhz memory is installed
This is log of the latest kernel panic:
Sat Sep 1 23:42:29 2012
panic(cpu 0 caller 0xffffff80038b7b95): Kernel trap at 0xffffff80038876bc, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff84098c6f70, CR3: 0x000000000649d000, CR4: 0x0000000000000660
RAX: 0x0000000000000001, RBX: 0xffffff84098c6f48, RCX: 0xffffff8016494550, RDX: 0x0000000000000821
RSP: 0xffffff80eab43710, RBP: 0xffffff80eab43730, RSI: 0x000000002789ac07, RDI: 0xffffff8007c2b2d0
R8: 0x0000000000000001, R9: 0x0000000000000001, R10: 0xffffff8114227000, R11: 0xffffff801734fe60
R12: 0xffffff8007c2b2d0, R13: 0xffffff80eab43820, R14: 0xffffff801b63c4c0, R15: 0x00000000000c1000
RFL: 0x0000000000010286, RIP: 0xffffff80038876bc, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff84098c6f70, Error code: 0x0000000000000000, Fault CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff80eab433b0 : 0xffffff800381d5f6
0xffffff80eab43420 : 0xffffff80038b7b95
0xffffff80eab435f0 : 0xffffff80038ce4ad
0xffffff80eab43610 : 0xffffff80038876bc
0xffffff80eab43730 : 0xffffff8003881a66
0xffffff80eab43a80 : 0xffffff800385e164
0xffffff80eab43ae0 : 0xffffff8003c51bb7
0xffffff80eab43be0 : 0xffffff8003c51e5a
0xffffff80eab43c10 : 0xffffff7f84fc6720
0xffffff80eab43d20 : 0xffffff7f84f9dc47
0xffffff80eab43d30 : 0xffffff7f84f74e82
0xffffff80eab43d40 : 0xffffff7f84f9dc23
0xffffff80eab43d50 : 0xffffff7f84f72f96
0xffffff80eab43d60 : 0xffffff7f84f9dd40
0xffffff80eab43d70 : 0xffffff7f84f7464c
0xffffff80eab43db0 : 0xffffff7f84f72e8e
0xffffff80eab43de0 : 0xffffff7f84f76f9f
0xffffff80eab43e00 : 0xffffff7f849402a4
0xffffff80eab43e20 : 0xffffff7f84940237
0xffffff80eab43e50 : 0xffffff7f84f8e8cc
0xffffff80eab43e80 : 0xffffff7f84f735d2
0xffffff80eab43ed0 : 0xffffff7f84f7159f
0xffffff80eab43ef0 : 0xffffff8003c47078
0xffffff80eab43f30 : 0xffffff8003c45b8a
0xffffff80eab43f80 : 0xffffff8003c45cb9
0xffffff80eab43fb0 : 0xffffff80038b2677
      Kernel Extensions in backtrace:
         com.apple.GeForce(8.0)[4B9BE287-5251-398E-96B0-BB16C9BFB2D9]@0xffffff7f84f6d000 ->0xffffff7f8502ffff
            dependency: com.apple.NVDAResman(8.0.0)[6A699209-FB98-316B-A3C0-DCA82AA8C86B]@0xffffff7f83f 0a000
            dependency: com.apple.iokit.IONDRVSupport(2.3.4)[99CA4184-8D92-31B2-8726-46139E8E3DFF]@0xff ffff7f83ef6000
            dependency: com.apple.iokit.IOPCIFamily(2.7)[8C9E06A4-13D0-33F5-A377-9E36F0ECC229]@0xffffff 7f83e6f000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.4)[2600903C-EEDE-321B-A023-169DC9B26EA6]@0 xffffff7f83eb3000
         com.apple.iokit.IOSurface(86.0.2)[0EA70D04-C914-3BB1-9E0B-50282F71BA1C]@0xfffff f7f8493c000->0xffffff7f8494dfff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12B19
Kernel version:
Darwin Kernel Version 12.1.0: Tue Aug 14 13:29:55 PDT 2012; root:xnu-2050.9.2~1/RELEASE_X86_64
Kernel UUID: 3005059E-270B-3B9F-940D-7A66C05DDC9D
Kernel slide:     0x0000000003600000
Kernel text base: 0xffffff8003800000
System model name: MacBookPro5,3 (Mac-F22587C8)
System uptime in nanoseconds: 4290007457923
last loaded kext at 488188985519: com.apple.driver.AppleUSBCDC          4.1.22 (addr 0xffffff7f85a9c000, size 16384)
last unloaded kext at 648108662282: com.apple.driver.AppleUSBCDC          4.1.22 (addr 0xffffff7f85a9c000, size 12288)
loaded kexts:
com.apple.filesystems.afpfs          10.0
com.apple.nke.asp_tcp          7.0.0
com.apple.driver.AudioAUUC          1.60
com.apple.iokit.IOBluetoothSerialManager          4.0.9f8
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.filesystems.autofs          3.0
com.apple.driver.AGPM          100.12.69
com.apple.driver.AppleMikeyHIDDriver          122
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.0.9f8
com.apple.driver.AppleMikeyDriver          2.3.0f2
com.apple.driver.AppleHDA          2.3.0f2
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.ApplePolicyControl          3.2.6
com.apple.driver.AppleUpstreamUserClient          3.5.10
com.apple.driver.AppleMuxControl          3.2.6
com.apple.driver.AppleMCCSControl          1.0.33
com.apple.driver.AppleSMCLMU          2.0.2d0
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.driver.AppleLPC          1.6.0
com.apple.GeForce          8.0.0
com.apple.driver.SMCMotionSensor          3.0.2d6
com.apple.driver.AppleUSBTCButtons          235.4
com.apple.driver.AppleUSBTCKeyboard          235.4
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          34
com.apple.driver.AppleIRController          320.15
com.apple.driver.AppleUSBCardReader          3.1.0
com.apple.iokit.SCSITaskUserClient          3.5.1
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.2.1
com.apple.driver.AppleFWOHCI          4.9.5
com.apple.driver.AppleUSBHub          5.1.6
com.apple.driver.AirPort.Brcm4331          601.15.21
com.apple.driver.AppleAHCIPort          2.4.0
com.apple.nvenet          2.0.19
com.apple.driver.AppleUSBEHCI          5.1.5
com.apple.driver.AppleUSBOHCI          5.1.5
com.apple.driver.AppleSmartBatteryManager          161.0.0
com.apple.driver.AppleEFINVRAM          1.6.1
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleHPET          1.7
com.apple.driver.AppleACPIButtons          1.6
com.apple.driver.AppleSMBIOS          1.9
com.apple.driver.AppleACPIEC          1.6
com.apple.driver.AppleAPIC          1.6
com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
com.apple.nke.applicationfirewall          4.0.39
com.apple.security.quarantine          2
com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
com.apple.security.SecureRemotePassword          1.0
com.apple.iokit.IOSerialFamily          10.0.6
com.apple.kext.triggers          1.0
com.apple.iokit.IOFireWireIP          2.2.5
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.0.9f8
com.apple.driver.AppleSMBusPCI          1.0.10d0
com.apple.driver.DspFuncLib          2.3.0f2
com.apple.iokit.IOAudioFamily          1.8.9fc9
com.apple.kext.OSvKernDSPLib          1.6
com.apple.driver.AppleHDAController          2.3.0f2
com.apple.iokit.IOHDAFamily          2.3.0f2
com.apple.iokit.IOSurface          86.0.2
com.apple.iokit.IOBluetoothFamily          4.0.9f8
com.apple.driver.AppleGraphicsControl          3.2.6
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.driver.AppleSMBusController          1.0.10d0
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.driver.IOPlatformPluginFamily          5.2.0d16
com.apple.nvidia.nv50hal          8.0.0
com.apple.NVDAResman          8.0.0
com.apple.iokit.IONDRVSupport          2.3.4
com.apple.iokit.IOGraphicsFamily          2.3.4
com.apple.driver.AppleSMC          3.1.3d11
com.apple.driver.AppleUSBMultitouch          235.7
com.apple.iokit.IOUSBHIDDriver          5.0.0
com.apple.iokit.IOSCSIBlockCommandsDevice          3.5.1
com.apple.iokit.IOUSBMassStorageClass          3.5.0
com.apple.driver.AppleUSBMergeNub          5.1.5
com.apple.driver.AppleUSBComposite          5.0.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.1
com.apple.iokit.IOBDStorageFamily          1.7
com.apple.iokit.IODVDStorageFamily          1.7.1
com.apple.iokit.IOCDStorageFamily          1.7.1
com.apple.iokit.IOAHCISerialATAPI          2.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.1
com.apple.iokit.IOFireWireFamily          4.5.5
com.apple.iokit.IOUSBUserClient          5.0.0
com.apple.iokit.IO80211Family          500.15
com.apple.iokit.IOAHCIFamily          2.2.0
com.apple.iokit.IONetworkingFamily          3.0
com.apple.driver.NVSMU          2.2.9
com.apple.iokit.IOUSBFamily          5.1.6
com.apple.driver.AppleEFIRuntime          1.6.1
com.apple.iokit.IOHIDFamily          1.8.0
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          220
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.DiskImages          344
com.apple.iokit.IOStorageFamily          1.8
com.apple.driver.AppleKeyStore          28.18
com.apple.driver.AppleACPIPlatform          1.6
com.apple.iokit.IOPCIFamily          2.7
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.corecrypto          1.0
If there is someone out there that could help, I appreciate it very much...!!! This is getting very annoying
thank you!!

I noticed that the:
last loaded kext at 488188985519: com.apple.driver.AppleUSBCDC          4.1.22 (addr 0xffffff7f85a9c000, size 16384)
last unloaded kext at 648108662282: com.apple.driver.AppleUSBCDC          4.1.22 (addr 0xffffff7f85a9c000, size 12288)
Now, before I go any further, I'd like to point out that diagnosing, and actually eliminating, kernel panics is very tricky. There are several causes that are very well documented on the internet. However, you can run all those tests, perform all that voodoo, even reinstall the OS... and continue to have kernel panics. That said, here are some notes:
What brought me here in the first place is that, since upgrading from Lion to Mountain Lion, I've been having the same frequency of kernel panics as you.
My frequency of kernel panics using Snow Leopard and Lion averaged once a week.
On Snow Leopard I could actually reproduce the kernel panic by USB tethering my iPhone. This was a widespread and well-documented issue for people with early 2011 MacBook Pro's, and Apple supposedly fixed it in an update. Supposedly...
Updating to 10.8.1 didn't fix the problem for me.
Since upgrading to Mountain Lion, I've stopped using Spotify, as that seemed to be the worst culprit (on my machine). Keep in mind, there are thousands, maybe millions, of users who aren't having kernel panics while using Spotity on Mountain Lion, so that's really only one data point. Also, Spotify recently updated it's own software that may have fixed a kernel extension problem but I haven't used it enough yet to report anything.
I took my computer to the Apple Store in 2011, and I recently spent an hour on the phone with Apple Care. No dice.
My kernel panic logs don't seem to have a common denominator as to the cause (Spotify, USB...)
Just when I think I see a common denominator like when I'm using a certain USB port, or a secondary display, there will be a kernel panic when neither of those things are happening
You''ve got a lot going on with your machine: upgraded memory, SSD...
Taking all that into consideration, be cautious not to jump to conclusions. No doubt, it's a combination of factors. For example, it could be certain MacBook Pro's that have certain video cards, USB, Spotify, Flash... I mean, really, it just starts heading down a dangerous path of speculation and conjecture, so I'm leaving it up the Apple engineers at this point. And, of course, always back up.
Anyway, you and I and whole lot of other folks out there are having the exact same problem since updating to 10.8.0. Add to that the issues that many of us are having with Safari, Mission Control... and it spells out one thing: the price one pays for being an early adopter. By all means, follow the steps outlined here:
http://support.apple.com/kb/PH11045
and perhaps here:
http://www.thexlab.com/faqs/kernelpanics.html
and use @baltwo's excellent recommendation:
http://kelleycomputing.net/rember/
Hopefully, that will fix the problem that you're experiencing but I'm betting against it. Most likely, 10.8.x will fix or at least improve this issue.
In the meantime, here's the good news: because of the autosave state features introduced in Lion, a kernel panic has gone from being a potentinally devestatingly destructive event to a minor (albeit inccessant) nuisance. It never hurts to compusively hit Command-S but even so, I'm happy to report that I can't think of a single kernel panic that has resulted in substantial data loss (read: work). In fact, there are worse things than restarting your computer, and reallocating memory that's been leaking from Safari...
Anyway, unless you're one of the those affected that can't even boot, I'd recommmend stopping short of reinstalling the OS. Wait for a stable release, and then when you have a slow week, perform a clean install. Then begin the process of installing fresh versions of your apps one-by-one. Also, by then, third party developers will have had time to update their kernel extensions, etc.
In other words, follow the hypocratic oath: thou shall not harm. We were all good before Mountain Lion, so let's not fix what isn't broken by tinkering with our systems too much.
Best of luck to you!
Mark

Lion clean install broke existing windows xp bootcamp partition

Hi all,
I have been trawling to get educated on this but haven't found an answer yet (except purchasing windows 7-not interested, but thanks in advance for telling me that I should abandon XP because it's over 10 years old). And also dont tell me to just virtualise, i will, but i also want to use bootcamp for better performance. Lots of people theorizing what might work, but here's your chance to see what's not working in reality (and help get it to work please!).
I had snow leopard with a working bootcamp partition running xp (also using parallels), on a late 2006 Mac book pro. Things were getting very slow so I really wanted a clean install of lion (and it has made a world of difference!)
I didn't want to lose my xp partition so here's what I did:
1-used disk utility to create disk images to backup both partitions to an external drive (using spare space on my time machine drive)
2-used my lion USB stick to perform a clean install of lion on another external drive
3-erase and restore new lion installation to my internal Mac partition (previously snow leopard)
4-use migration assistant to bring back my data and settings (not applications-doing that manually)
5-download & install relevant software updates
(note that the bootcamp partition is untouched in all of this)
I noted that at first there was no lion recovery partition on my internal drive, but it has since appeared (presumably when I used software update to install an update to lion).
I didn't test the boot camp immediately but when I try to load it now the partition shows up and I can select it but windows presents me with the boot options screen (safe mode etc). It fails under all options (starts to load then flicks a blue screen before rebooting). From the safe mode log screen it appears to me that the issue could be the partition numbering (the new lion recovery partition has changed the partition number for the windows partition and it's freaked windows out).
Question is, what's the best way to fix it? I'm reluctant to try bootcamp assistant 4.0 because I know it doesn't support xp.
In hindsight maybe I should have done a clean install of snow leopard onto the external drive, erased and restored to the internal, updated snow leopard to 10.6.8 (or whatever was necessary for lion install), checked that the boot camp partition still worked (if not fix it with boot camp assistant), then upgraded to lion (seeing as upgrading to lion when there's a working xp partition on bootcamp is supposed to work).
I could still do all that but I wonder if there is a better / cleaner / easier solution.
Thanks in advance (& sorry for the long description!)

For future reference cloning can be the easy answer to preserving a BootCamp partition. I used the following procedure to upgrade 2 MBPs to Lion from SL.
Use Yasu and Diskwarrior to prepare existing Mac OSX 10.6.8 HDD.
Clone 10.6.8 Mac partition to an ext HDD with SuperDuper or Carbon Copy Cloner.
Restart from the cloned ext HDD and select it as the startup volume via System Preferences / Startup Disk.
Install 10.7 Lion on the cloned ext HDD
Install Lion 10.7.2 update on the ext HDD
Restart the ext HDD now with OSX 10.7 and test and adjust the preferences if needed.
When satisfied, clone the OSX 10.7 ext HDD back to the existing Mac HDD.
The Boot Camp partition will not be altered as to drive id which appeared to cause problems for a few people.
The recovery partition will be on the ext HDD and can be used for trouble shooting. A more convenient way to have the recovery/reinstallation environment is to have or create a Lion install USB thumb drive.

Yosemite Clean Install Problems

Hi,
I have recently tried to do a clean install of the Yosemite OS but the install was unsuccessful and I have had nothing but trouble since. If you have any ideas on how to fix my problem, I'd be very grateful. Perhaps you have or have had the same problem and have some other ideas on how to fix it.
(Note: Recently I have not used TimeMachine as it kept on corrupting my external HD, so I have backed my files up manually on another volume but no previous OS backup to revert to)
This is what I've done:
Attempt 1: Bootable USB
I created a bootable USB of Yosemite (via Terminal etc.). I was able to install Yosemite and it restarted. On restart, it continued to install the other system files, but suddenly stopped as it "could not extract files from BaseSystemBinaries.pkg". I restarted the Mac and it continued to install the other system files, but after a while it came up with a message saying "couldn't attach disk image". Then I tried once again and it came up with some other error message. I went into Disk Utility, erased the disk and the Macintosh HD partition and attempted to re-install Yosemite from the USB after another restart. Despite having erased the disk, the installation went straight back to installing the excess files (I guess once you get to that point, it remembers and you can't get out of it until the process completes). Unfortunately, once again, error messages came up. (Note: USB was formatted for Mac Os X Journalled thingo)
Attempt 2: Internet
I removed the USB and it said I could install the extra files from the net. I entered my WIFI code, AppleID password etc and the download started. Unfortunately I do not have 293 hours to wait until the download completes, and after waiting two hours and noticing the download had another 394 hours to go, I decided this was not going to work.
Attempt 3: Downgrade
I hunted around in my old CDs and DVDs and found a bootable DVD of Mac OS Lion. It installed completely and I was so over the moon! I Then thought - ah, perhaps I can upgrade from Mac OS Lion to Yosemite. I copied the Yosemite Installer from the USB on to my Mac and started the install. All went well until the computer restarted and proceeded to install the excess files - once again, I had problems as the "BaseSystemBinaries.pkg" couldn't be opened.
Attempt 4: Confused
I figured that I would easily be able to downgrade again considering it worked last time. I did exactly the same things - erased the disk in Disk Utility etc, but for some reason, the install failed and each time I tried to restart, the Mac returned to the same place (a bar "installing Mac OS Lion) and failed shortly after.
Thoughts
1) How do I get the Mac to forget or erase the previous install attempt so I can attempt another fresh install. It remembers which stage of install the installer is at be it for Yosemite or Lion. It keeps returning to the same stage and fails. Even after erasing the disk and partition, and resetting the PRAM.
2) Could my Yosemite Installer be corrupt? How on earth could it become corrupt after installing from the internet? What if I had not attempted a clean install, upgraded. I'd be in the same position and if I hadn't backed up, lost absolutely everything...

SINCE MY FIRST POST, I follow the same instructions from: http://osxdaily.com/2014/10/18/clean-install-os-x-yosemite/
I HAVE NOW SUCCESSFULLY INSTALLED YOSEMITE. Looks good. Everything in place, including all my menubar items. My most used app, Adobe Photoshop CC 2014 works (Amen) and all it's 9 or 10 plug-ins there and work. So I'm feeling a-okay about it right now.
Topic1. What happen to me;
Topic 2. What I'd suggest
Screen Shot 2014-10-23 at 8.49.21 AM.jpg
TOPIC 1. HERE'S WHAT HAPPEN TO ME (Thus far): I did NOT use a USB drive for my clean install (as osxdaily mainly suggested).
I used an external drive I had available (250GB).
At the last minute I recalled another item I read while browsing: INSTALL YOSEMITE ON AN EXTERNAL DRIVE (rather than just a USB flash drive) . - So that's what I did; installing it on the drive I had prepared for the clean install. --
There was a problem came up> The installation seemed to hang up in the way several others have mentioned (a big X and a stalled blue progress bar).
I turned the computer off after a few hours. (another suggestion I read). Turned it back on.
Much to my surprise, my computer booted from this external drive and there was Yosemite -- I'm also able to access my apps and data from my built-in iMac hard drive. Some work. Some important ones give me an error message...so I need to check all that out.
I didn't plan this, never done it before but I'm pleased. I can get to see and use Yosemite (I like it's look, features, etc. so far), can access and test what apps work and what may give me a problem and, real cool, I can simply go back to booting up from my internal hard drive and all my Mavericks stuff is there.
TOPIC 2. WHAT I'D SUGGEST (for clean install) -- which I think is a good idea and part of this OP): Follow the osxdaily steps again (they worked for me). DON'T LATER RESTORE YOUR DATA ET. AL. FROM TIME MACHINE. -- Instead when Yosemite is going through it's first set-up it asks various questions and give you options to select or not - In this initial Yosemite start-up, select the option that indicates it will MIGRATE YOUR DATA FROM ANOTHER MAC OR FROM TIME MACHINE.
Thus> Don't try to Restore your info and apps from Time Machine later -- SELECT MIGRATING YOUR DATA FROM TIME MACHINE (or Mac or one of those options) during Yosemite's initial first start-up.
Also, Big Tip, not only do the expected preparations prior to attempted installation (upgrading your OS and major apps to their latest version, running Onyx or Cocktail or something like that, and backing up Everything in some way -- but when installing DISCONNECT all unneeded USB devices and especially USB hubs -- just keeping what you need for your keyboard and mouse; this can prevent a lot of problems, I believe (maybe caused by device drivers?)
CONCLUSION: If you get that hang up in the way several others have mentioned (a big X and a stalled blue progress bar).Turn off computer after a few hours and turn on again.
I think this method will work: as mentioned> MIGRATE DATA DURING YOSEMITE'S FIRST RUN. -- After I test out a few more apps I'm going next to install Yosemite on my main, internal iMac hard drive: it's over 600GB of data on it.
I hope this helps yourself (and others).
Let us know how it goes. Good luck.
P.S. - Yosemite is oh-so clean...a nice 'fresh start' compared to my iMac with a year's worth of this and that all over the place. Contrary to the bad rumors and trolls I think Yosemite is a 'mild' upgrade, meaning it doesn't NOT threaten existing apps and data. -- It's real problems are with the NEW things it introduces, like Handshake and Continuity, Apple Pay, etc. -- Between start and finish it was close to 24 hours.

Help with iTunes database and Time Machine after Lion clean install

I did a clean install of OS X Lion and think I've given myself problems with my Snow Leopard Time Machine backup and with my iTunes Library database files.
My iMac (2007) had become very sluggish so I opted for a clean install. Before the install of Lion my Snow Leopard 10.6.8 internal 1TB HD was at about 600GBs. I was using Time Machine to backup to an external 1TB drive. I had my iTunes 10.? library on the same drive.
For the Lion install I partitioned my internal 1TB HD into two partitions - a 250GB Lion boot partition and the rest for Lion data files.
Now I have two problems - 1. I can't work out how to re-connect my Time Machine backups, since they were related to a much bigger original drive, and 2. I can't seem to find my iTunes database files.
I also don't want to restore any application files at this stage, as I'm determined to do a fresh install of only the applications I need as I go along, and hopefully avoid the issues of sluggishness I had with Snow Leopard.
I have all my iTunes files in their pre-Lion external HD folder, but that folder does not seem to have the iTunes Library.XML or iTunes Library files. I didn't delete them so I'm hoping they were in my iTunes folder on my SL boot drive. But that drive was deleted during the install, so I'll be depending on Time Machine to restore the database.
Can anyone suggest a way to deal with Time Machine for my Lion install, and a way to restore my iTunes database? I'd like to keep as much of the Snow Leopard Time Machine data as I can, while continuing to do Time Machine backups from my Lion installation.
Anyone know where iTunes stores those database files, if not in the external drive iTunes folder? Spotlight search doesn't find the files, but is there a way to search my old Time Machine backups without having the Time Machine backups folder re-connected in Lion?
Thanks.

My iTunes folder is organised like this if it helps:
And iTunes uses them from the Prefrences like this:
Regards,
Colin R.

Time Machine backup history present but inaccessible after Mountain Lion clean install

Hi all,
A few days ago, I took the Mountain Lion plunge and after performing all the preliminary data copying to external hard drives as well as on last Time Machine backup to my dedicated Time Machine external hard drive, I booted from my ML recovery USB thumb drive, reformatted the internal HD, and proceeded to perform a clean install of OS X 10.8.
The ML install and initial setup completed without a hitch, and I had no difficulty in reconnecting to my existing Time Machine EHD and performing an initial backup of the freshly upgraded Mountain Lion system. It took several minutes in the "preparing backup" phase; but once it got through that, it backed up my entire system (which was basically nothing more than the new OS and iLife at this point) within an hour or so. Time Machine has since worked reliably in performing the automatic backups every hour.
But here's the problem: My backup history went back all the way to March 2011 before the ML upgrade, and it still (sorta kinda) does now. However, although I can see all of the backup history tick marks when I enter TM, the ONLY SELECTABLE backups are from the point where ML was installed and onward. The previous Lion and Snow Leopard backups are visible; just not selectable. I also verified that the physical backup folders are still present on my TM EHD dating all the way back to last March. I ran a verify and repair operation on the TM volume, and it came back clean. I have disconnected and reconnected the TM EHD to TM and of course rebooted, but no joy. TM did not force me to "start over" with a new backup as some posters have complained of. And it seems to be working fine otherwise.
Has anyone else had a similar experience after upgrading to ML? Any thoughts on how I might reconnect to my TM backup history?
Thanks in advance for your thoughts.

How did you put your data back after the erase?
I didn't, or rather I haven't yet. Basically, all I have done so far is:
Reformat Lion HD and install ML clean from USB thumb drive
Run through initial virgin boot setup, e.g. enter my Apple ID and desired user account info
Change a few preferences (the "use right side of mouse for secondary click" setting first and foremost!)
Configured Time Machine to use pre-existing Time Machine Backups EHD and let it do initial backup (which it simply added on to the existing backup history as I had hoped)
Drag-and-drop copied my saved iTunes library (~50 GB) from my ext. FW drive to my new Home Music folder and confirmed that iTunes was working and able to sync with my iPhone and iPad
Installed the iLife suite from my Bundled Applications DVD and then updated those apps via the App Store
Obviously the iTunes folder is an exception to "I haven't yet", but basically, the Lion's share (pun intended) of my previous data has not yet been copied back from the temporary storage on the EHD.
The reason you can't see the backups of the old home folder from the new one is simply that they have different names.
Yes, I know that now. Everything was fine all along. I just didn't realize that TM [quite sensibly] grays out any backup history finder windows and right-hand-side tick marks that contain no backup of the folder currently in focus. Since the folder I had in focus was one that didn't exist before I installed Mountain Lion, there was nothing to access except for the most recent post-upgrade backups.
Thanks much for your help.

Mail backup on Mountain Lion clean install

I'm installing a new SSD in my Mac Pro and want to set it up as a clean install of ML so not from a previous TM Backup.
I only want copy the whole of mail - with all the mailboxes and filters intact and without having to set this up again.
Any help in how I do this would be really appreciate.
Thanks in advance, Matt

This will be a lot easier if you make a secondary backup using something like Carbon Copy Cloner. (That's good practice anyway... relying on one single backup isn't all that safe overall. I've seen plenty of people who only discovered their one-and-only backup was corrupt once they needed it, or who did something wrong in the restore process and destroyed it.)
Then, when you're ready to restore Mail, you need the following folders from the backup:
Users/yourusername/Library/Mail/
Users/yourusername/Library/Containers/com.apple.mail/
Move those folders from the backup to the same location on the new system. The difficulty will be that, in Mountain Lion, the user Library folder is invisible, so what will make your life easier is to run the following command in the Terminal before making your backup with Carbon Copy Cloner:
chflags nohidden ~/Library
(Terminal is in the Utilities folder in the Applications folder.)

Correct way to restore from Time Machine backup - Lion clean install

I did a clean install of Lion, and am wondering — what's the correct way to restore files in my Home folder to my new installation?
For example, I simply dragged over my iTunes folder from the "Latest" Time Machine backup.
Perhaps instead I should restore from the backup differently? For example, open the ~/Music folder, then open Time Machine.app, and restore that folder through that?
I always thought that manually dragging the "Latest" backup from the disk should do the trick the same way? Or an important question is — can some files be somehow excluded?
I did everything through dragging, and haven't noticed problems... BUT, perhaps I should go back and re-do everything the "right" way if there is one?
(I purposefully avoided doing a Restore, as I didn't want any of the caches, Applications and Library items restored — wanted to start fresh.)

For convenience mostly. I use the Terminal a lot so I have lots of "dot files" that are at the root of my home directory and hidden.
One problem is that many of those programs have data in Music, Photos, etc all organized by databases somewhere in ~/Library. You have to make sure to get them re-joined. It can be done. You just have to be careful with it. If you lose your iPhoto archive in the process, the first thing someone is going to ask is why didn't you use Migration Assistant.
Until recently, I performed all my major MacOS X upgrades using this manual procedure and, for me, the extra hassle was worth the cleanliness. I have lost a couple of software registration codes that I couldn't ever get back. C'est la vie. I would keep my old Library folder around for quite some time until I was sure I wouldn't need anything out of it. These days, I'm too busy and too lazy. I just use one of the automatic methods.

Mac OS x lion clean install problems

Similar Messages

Maybe you are looking for