Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > macOS > Help Needed: Migration Assistant causes KP...

Help Needed: Migration Assistant causes KP...
Thread Tools
cfevnmm
Fresh-Faced Recruit
Join Date: Apr 2001
Location: Milan, Italy
Status: Offline
Reply With Quote
Jun 8, 2005, 06:20 PM
 
My brother, under my advice, just bought a new dual 2.0 g5 to replace his aging Quicksilver g4.

He was very happy when I told him about the Migration Assistant feature, and how easy it would have been to transfer his account, apps and other stuff to his new g5 in a breeze.

Unfortunately, it turned out to be a real hell: the g5 panics as soon the Migration Assistant starts transferring the files.

We tried many times without success. Of course my brother is angry and nervous, also because he has already sold the old g4 and must hand it in to the new owner within two days....

We also repaired permissions on the old mac but it didn't help.

BTW, here is the log of the KP, hope someone can understand what's going on

any help would be appreciated

thanks

--------

Wed Jun 8 11:09:16 2005
panic(cpu 1 caller 0x27603AEC): DART entry exception: HyperTransport read
logical page 0x003AE

Latest stack backtrace for cpu 1:
Backtrace:
0x00095564 0x00095A7C 0x00026838 0x27603AEC 0x2FC2FD70 0x2FC2FDA8
0x2FBF5048 0x002CDC8C
0x002CCB54 0x000A9654
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleGPIO(1.1.8)@0x2fc2d000
dependency: com.apple.driver.IOPlatformFunction(1.7.0b1)@0x275 ed000
com.apple.driver.MacIOGPIO(1.1.8)@0x2fbf3000
com.apple.driver.AppleMacRISC4PE(1.6.0d9)@0x275fd0 00
dependency: com.apple.iokit.IOPCIFamily(1.6)@0x275df000
dependency: com.apple.driver.IOPlatformFunction(1.7.0b1)@0x275 ed000
Proceeding back via exception chain:
Exception state (sv=0x00A1AC80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000;
R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.0.0: Sat Mar 26 14:15:22 PST 2005; root:xnu-792.obj~1/RELEASE_PPC
*********

     
Thinine
Mac Elite
Join Date: Jul 2002
Status: Offline
Reply With Quote
Jun 8, 2005, 07:19 PM
 
What I would recommend doing is nuking the OS X install on the G5 (as long as there isn't anything there you can't lose) and install OS X from scratch, from the restore disks. Format the drive and make sure to customize the OS X install. After the system is installed, it should bring up the migration assistant. If it still doesn't work, there's probably something wrong with his hardware.

If you don't want to do that, try a different Firewire port. Also, remove any third party memory you've installed.
     
cfevnmm  (op)
Fresh-Faced Recruit
Join Date: Apr 2001
Location: Milan, Italy
Status: Offline
Reply With Quote
Jun 9, 2005, 04:35 AM
 
Originally Posted by Thinine
What I would recommend doing is nuking the OS X install on the G5 (as long as there isn't anything there you can't lose) and install OS X from scratch, from the restore disks. Format the drive and make sure to customize the OS X install. After the system is installed, it should bring up the migration assistant. If it still doesn't work, there's probably something wrong with his hardware.

If you don't want to do that, try a different Firewire port. Also, remove any third party memory you've installed.

We already tried to reinstall OS X, although not from scratch (just reinstalled over the old one).

RAM in the g5 is actually apple-installed memory.....

but I'll try another firewire port

BTW: could it be a defective cable?
     
Alton
Fresh-Faced Recruit
Join Date: Dec 2003
Status: Offline
Reply With Quote
Jul 1, 2005, 02:03 AM
 
Hiya,
I actually have a related question.
I have three drives on the old Mac. I select the system drive to restart as target. Once the restart and the firewire hook up to the new mac is complete, one of the other drives appear as available - not the one I selected originally.
I completely disconnect the ribbon cables from the other drives - leaving only the startup drive. The old machine boots fine. I choose the startup as the target on restart. The old machine restarts, ponders a few seconds and completely shuts down - not crashing, but power off! Hmmm
I can only guess that it's :
- a jumper setting on the old drive (too complicated to figure out)
- this drive was not the original startup drive. It was designated startup on a previous upgrade - but working fine since

All old and previous systems on all other drives deleted.

Anyone have any suggestions?

Thanks much,
Alton
     
   
 
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Top
Privacy Policy
All times are GMT -4. The time now is 06:51 AM.
All contents of these forums © 1995-2017 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.8 © 2000-2017, Jelsoft Enterprises Ltd.,