Jump to content

Recommended Posts

Posted

Not that there are likely to be others rushing into it like this ... but this thread is something I have just found with a few good things to try.

 

Option 1 - If your destination volume fails to appear then open up Disk Utility ... it is likely to just show you the drive with no volume. Leave it like this for 15-20 minutes and it should appear. Close Disk Utility and the install should go ahead fine.

 

Option 2 - If your destination volume fails to appear then open up Terminal from utilities.

type df -k

first tie the internal volume is not seens

type df -k again

now the volume should appear

close the Terminal and continue to install.

 

I'll try it tomorrow whilst at work (when I have my MBP restore discs to hand).

Posted

Is It the same problem as this here? http://www.glennwolsey.com/2007/10/29/leopard-migration-how-it-went-down/

 

I came across the first problem when the Leopard DVD only picked up my Storage drive, I promptly rebooted into Tiger and did a quick search on the Apple discussion boards for this problem. I was relieved to find a few others had experienced the same issue as it was quickly fixed by booting back into the Leopard DVD, opening Disk Utility, and un-mounting the drive. When I navigated back to the install screen, both drives were available for installation.
Posted
Thank god I didn't have this, installed Leapard yesterday on my MBP and it went fine without a hitch, seems to run ever so slightly slower though, might do another installation, a clean one rather than an upgrade though.
Posted

A quick comeback on the Leopard install.

 

it is now on all 3 machines (the 2 at home and the work MBP).

 

The df -k trick didn't work the first time I tried it so I restarted, and the trick of leaving the disk util open took nearly an hour to recognise the volume.

 

I was then a little cheeky ...

 

I started again but did the df -k trick *before* running disk utility ... and the volume appeared within 5 mins. I tried this again ... restart and just run disk util ... over an hour ... restart and do it with df -k twice ... appears within 5 mins.

 

Still, the upgrade (nnot and erase or archive and install) went well.

 

I am going to run it like this for a month, and then do a clean build to see the difference. this is so I can work out whether it is better to do a clean install on staff laptops or whether an upgrade is best.

 

I'll put a new topic up in a months time. Out of interest have others done a clean build or an upgrade?

Posted

I did a clean install on my MBP core 2 duo and all went fine.

 

I had no problems.

 

I had installed Leopard server first though before installing client but both worked fine.

 

My brother has just updated his client from tiger to leopard and has run into a few issues. Mainly the fact that mobile accounts don't seem to be able to sync back to the Tiger server. They keep failing. So a little heads up for those looking to deploy Leopard clients on laptops with mobile home accounts on laptops while keeping a Tiger server running.

 

There is also a few more people with this (or similar) issue in the Apple discussions under the portable homes section.

Posted

I did a upgrade on my MBP and works great took 1 hour but no problems so far (touch wood).

 

Also installed it on a intel iMac and installed pretty good :)

 

Ross

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...