I7 iMac won't boot, kernel panic after migration

Question

Level 1

0 points

I7 iMac won't boot, kernel panic after migration

I received my imac yesterday, booted it, created a profile, played around, and since everything seemed to be working ok, today I decided to migrate my data from my macbook pro, which is running 10.5.8.

The migration seemingly went fine. Once it was finished, I logged into the immigrant profile. All looked well, but the bluetooth mouse wasn't recognized. Turning it off and on didn't help so I opted to reboot the machine.

After about ten seconds of the apple logo and loading symbol, I received a kernel panic. I performed a hard restart and the same thing happened. I inserted my OS dvd and performed the hardware test first. Everything checked out fine. Next I verified permissions. I was alerted to a modification of the apple remote desktop agent that couldn't be repaired. In the apple support section I discovered this message was nothing to sweat about. Next I verified the disk and it reported everything was fine. I reset the pram and booted into safe mode successfully. I wasn't sure what to do next since I'd already run disk utility from the dvd, so I tried rebooting once more to see if the machine could do it on its own now, but no luck. Instead of a panic, it now runs through the apple logo, loading symbol, and then sticks on a blank white screen.

I'm now in the process of erasing the hard drive and reinstalling the OS as there was obviously a problem caused by the migration. My question is, what caused it? I made sure the macbook pro was up to date in software update before I started. It only copies user data, applications and their settings, and system preferences, correct? What in the world could have copied over that caused such a severe problem?

I'm certainly scared off of running the migration assistant again, but even if I have to copy my data over piecemeal I'm worried that I may inadvertently copy something the new mac doesn't like.

If anyone has an idea about what's going on, please advise.

After proofreading my post, it just occurred to me, could the system preference for the start up disc have caused a problem? That doesn't seem likely though or migration assistant would never work. And I was able to boot into safe mode. Could it have been a start-up item (these are disabled in safe mode)? I have snaps pro and some color management software in my login items, but since that's specific to the account, these should only play a role once I log into that user profile, correct?

For reference, here is the apple doc on safe mode. Since the machine booted into safe mode successfully, then I must assume the problem was caused by one of the items safe mode disables which comes into play during whatever the computer loads at the apple logo.

macbook pro, Mac OS X (10.5.8)

Posted on Nov 19, 2009 7:20 PM

Reply

Answer 1

Nov 19, 2009 7:29 PM in response to dotm8rix

The new i7 will only run 10.6.2 and later. When you say that you migrated from 10.5.8 did you clone that version to the new i7 and if so that is most likely your issue.

Receiving a KP so soon after booting generally indicates that the system is not at a level that the hardware requires. I see this quite often when people clone a Intel version to a PPC machine, using target disk mode..

Message was edited by: Thomas Strange

Message was edited by: Thomas Strange

Reply

Answer 2

dotm8rix Author

Level 1

0 points

Nov 19, 2009 7:27 PM in response to dotm8rix

Just to add more info, the macbook pro I migrated from is from the first generation, running a core duo processor that, although is Intel, is not capable of 64-bit operation. Is there any reason that could be the problem? I have read about the dangers of migrating from PPC machine to Intel, but thought any Intel to Intel would be fine.

Thanks!

Reply

Answer 3

Nov 19, 2009 7:35 PM in response to dotm8rix

When you re-installed, did you start up from the optical drive with the Mac OS X installation disc that came with the iMac? Then, when you get to the Installer screen, you should run Disk Utility from the menu bar under Utilities and erase the internal drive. Make sure the internal DRIVE is selected in the sidebar, not the volume indented under the drive. Once the drive is erased this way, quit Disk Utility to go back to Installer; perform a standard installation in the blank internal drive volume.

When it restarts, it will go through Setup Assistant again. Don't do any migration initially. As you did before, run the iMac +as is+ for a while to make sure it is working 100%. Be sure to run Software Update to apply recent updates. After you are satisfied that it is working great, and you want to try Migration Assistant, run it from Applications/Utilities/.

This time, on the screen where you choose what to migrate, only check the box for Users. Do not migrate +Applications, Settings, and "Other..."+. This will migrate your user data from the other Mac, but leave out other data. I don't think migrating just your user data will cause the problems you described.

You can, of course, transfer the data manually. You can connect the other Mac manually using either +File Sharing+ over the network or FireWire Target Disk Mode.

http://support.apple.com/kb/HT1661

Reply

Answer 4

dotm8rix Author

Level 1

0 points

Nov 19, 2009 7:49 PM in response to Thomas Strange

Thomas,
I didn't clone the drive. I ran the migration assistant application located in the applications -> utilities folder. I suppose it's possible I left something checked that I shouldn't have, but unfortunately I can't recall all the options now, nor can I seem to find a list of them or a screenshot of them online. Frustrating. But generally they were options for things like applications and user profiles.

Considering many users who aren't computer savvy use the migration assistant to copy from a machine running an older OS to a machine running a newer one, I'll be very surprised if the problem is that migration assistant copies over incompatible system files. If anyone knows different, please share. I do recall that I used it once before successfully to restore data after upgrading my OS to Leopard (because a new hard drive wasn't formatted correctly, I had to clone the drive to an external, reformat and THEN install leopard, and then I migrated my data from the external drive).

Reply

Answer 5

dotm8rix Author

Level 1

0 points

Nov 19, 2009 8:03 PM in response to Kenichi Watanabe

Kenichi,
Yes, I booted from the cd and erased the disc and am now reinstalling the OS.

I think your idea of only migrating the one thing is good, but I'm actually not that interested in the user data, at least I don't think I am. Mostly I wanted to copy over my applications, which will otherwise be a pain in the butt to reinstall, reconfigure, and then what about bookmarks, emails saved to the disk, etc.

My initial plan was to copy things over one at a time as I needed them, but irritation about how time consuming that would be caused me to run the migration assistant, knowing I'd be copying over a lot of unnecessary data (settings for apps that have been uninstalled, apps I don't use often, etc). I'm back to thinking I should copy things over manually as needed.

Do you have any ideas about what type of file might have caused this problem?

Reply

Answer 6

Nov 19, 2009 8:12 PM in response to dotm8rix

It is really best to install applications from the original source. While you are doing so, you can weed out (not install) apps you no longer need, and make sure you have the latest versions that are compatible with Snow Leopard.

Many apps install additional support files in +Library/Application Support/+ (or other location) and others may not run when copied over because they place hidden registration files to ensure users cannot illegally copy the app file for use on multiple computers. A few (such as VMware Fusion) even need to install a kernel extension to work properly. Migration Assistant does not account for all those variables. Also, your MacBook (if Core Duo) is a 32-bit machine. Your new iMac is a 64-bit machine. That may have impact on migrating apps from one Mac to another.

Reply

Answer 7

dotm8rix Author

Level 1

0 points

Nov 19, 2009 8:33 PM in response to dotm8rix

I've reinstalled the OS and successfully booted into it. I'm proceeding to install the extra apple applications.

Reply

Answer 8

dotm8rix Author

Level 1

0 points

Nov 19, 2009 8:58 PM in response to Kenichi Watanabe

Kenichi Watanabe wrote:Migration Assistant does not account for all those variables. Also, your MacBook (if Core Duo) is a 32-bit machine. Your new iMac is a 64-bit machine. That may have impact on migrating apps from one Mac to another.

I've been wondering if that was the problem.

Overall I agree with your advice and I'm going to reinstall everything from scratch. Though I will admit that part of the trouble with that is shareware software that I downloaded instead of installed from a disk.

For instance, last night I tried to install an application. I have a license for one copy. Well, I'd rather run it on my imac but I don't know how to de-authorize it on my macbook pro, and it won't accept my serial when I try to install on the iMac. I emailed the support for that company last night and they haven't gotten back to me yet. So right now I have no way to install the application until/if they respond, unless I buy a new license or copy it over from the old machine. Of course I'm going to try and copy it from the old machine again.

I better stop now because I can feel the inclination to start a rant about why honest people with money are inclined to pirate software. hehe.

fwiw, the imac seems to be booting up faster now that i've reinstalled the OS. I can't say for sure since I didn't time the boot up before.

Reply

Answer 9

Nov 19, 2009 10:12 PM in response to dotm8rix

Whenever I start using a new Mac, I always use the included disc to reinstall the OS and bundled apps. I run it +as is+ with the factory installation (plus updates from Software Update) for a day or two, to make sure everything is fine. Then I reinstall everything, add RAM (if I bought more), install third-party apps, and transfer my data manually.

Reply

Answer 10

Nov 19, 2009 10:17 PM in response to dotm8rix

No more kernel panics is a good thing! 🙂

Reply

Answer 11

Nov 24, 2009 2:37 PM in response to dotm8rix

Exact same problem. Migrated data from Macbook Core 2 Duo 2.0Ghz. After installing VESA arm, and then power up: Kernel panic. com.apple.drivers.BOSlink (or something like that). I'm zero'ing and starting from scratch. Will migrate manually.

Reply

Answer 12

Nov 24, 2009 10:56 PM in response to dotm8rix

" … and then what about bookmarks, emails saved to the disk, etc?"

ALL of those you refer to above are User files, and are stored in your User directory. That is precisely why you want to use the Migration Assistant to move such user files over to your new machine.

The machine you purchased will not run properly using any presently available version of Mac OS X 10.6 except that which shipped with it on a Restore disc. You must use that package, and not a retail installation disk as the base installation source.

Reply

Answer 13

Nov 25, 2009 11:31 AM in response to dotm8rix

Oh my God, I am freaking out. Should I order my i5 now or wait until Apple says something about these problems and have them fixed? (The screen flickering and DOA machines)

I live in El Salvador, Central America and I am having the machine sent from the States from a friend and as you may imagine, the returning may be a pain in the butt... Please help

Reply

Answer 14

Nov 25, 2009 3:38 PM in response to bassetbob42

Looking thru plist files migrating by hand, I saw a TMOSLink driver - Temperature Monitor app. My advice is to delete that app from the migration source, and I bet one doesn't get the kernel panic.

Reply

Answer 15

jpm12

Level 1

4 points

Dec 18, 2009 5:49 AM in response to bassetbob42

Glad I found this thread, I had exactly the same problem with a brand new i7 ; it appeared after migration (500 Gb of data) from an iMac Core2Duo 2.53 Mhz

After reformatting the HD and reinstalling system it works fine - now I am VERY nervous about migrating again, but I will start with the user data as advised above.

Reply