|
|
StuffIt Deluxe 12: breakthrough compression of MP3 files, PDFs,
iWork and MS Office files! Reduce JPEG file sizes with no loss in
quality, burn to CD/DVD, back up archives to iDisk and more. Buy
today for only $59.99! <http://www.stuffit.com/mac/deluxe/tb/>
|
![[F]](/Images/i7/site.gif) TidBITS  TidBITS TidBITS Talk
Leopard Install Issues![[Shotton, Chuck]](/webx/?30@@1) Chuck Shotton - 08:27am Oct 27, 2007 PSTI've been trying to get a successful Leopard installation for about 24 hours now. Here are some issues and words of advice that may help others. First, if you have a second drive, internal or external, this process is GREATLY simplified. And if you don't have an external drive, how are you doing back-ups? I started with a dual G5 desktop with 2 internal 250g drives and 2 external firewire drives. The plan was to install 10.5 on the second internal drive (the first having 10.4 on it) and use the larger external firewire drive for Time Machine. Popped in the installation CD, rebooted off of it and started the install process. This is very similar to the usual OS X install process with a few cosmetic differences. In the past, I have always used the "archive and install" option to place new OS versions over existing installs. Given the amount of baggage that has grown around my current 10.4 install, I thought I'd do a clean install on the second internal drive and use the installer's "migration" features to copy my network settings, user prefs, apps, and documents to the new, clean OS installation. Bzzzt! I tried no fewer than 3 times to do this. Each time, the installer would land on the page asking if I wanted to copy info from another Mac, another partion/hard drive on the same Mac, or just do a clean install. I picked the option to copy my stuff from another drive on the same Mac each time. I selected my main user account, my prefs, my applications, and additional folders (basically everything except the unwanted user accounts). Each time, the installer skipped merrily through the installation steps, completely bypassed any sort of copying from the old drive, and dumped me into the new Finder with a completely virgin OS installation. No prefs. No apps. No nothing. There have been no error messages or warnings or any other indication why this step fails repeatedly. I'm currently in the process of cloning my boot volume (10.4) to the second internal drive and will do an archive and install on it to see if that works. But something tells me that other people are going to run into the same problems I had. There's nothing special about my existing OS X 10.4 installation, permissions, or anything else. That it just fails silently seems unfriendly at best and IMO, pretty darn broken. I'd be curious to know if there is a way to invoke the "migrate" functionality once a clean installation is complete. I'd love to skip the complete re-install each time as I try to decipher what is going on to cause this to fail.
|
|
Re: Leopard Install Issues
>> So none of you tidBITS readers have had difficulties with losing your
>> Keychain settings or losing your "My Account" with its Admin "power?"
I had lots of little irritating Keychain issues after the installation
-- I was able to solve this when I noticed that I had a Keychain that
had "MyUsername.keychain", but the System seemed to want (and had
created) one called "login.keychain." So I just renamed my old
keychain and ran it through Keychain First Aid, and it all seemed to
work out okay.
(And then came Apple's update to fix the problem.)
BRIAN
|
|
 | |
|
|
Re: Leopard Install Issues
Matt,
On Oct 30, 2007, at 1:26 PM, Matt Neuburg wrote:
> I haven't seen this problem personally, but I know that many users
> have. I
> thought that this was the sort of thing the new update from Apple was
> supposed to fix:
>
> http://www.apple.com/support/downloads/loginkeychainupdate10.html
If one could not log in to one's Admin account, there was no way to
apply the update; and of course, it didn't occur to me that I could
have used my "Troubleshooter" account (admin) to log in and apply the
update -- I wanted my [username] admin account back. As it is, when I
was finally able to install this update (on my third Erase and Install
with Migration Assistant), I still experienced no "fix" of the
Keychain, so I don't know what that update actually did.
>
>
> You can also solve the loss of your account's admin power by
> enabling the
> root user and then logging in as the root user - giving you the
> power to
> turn the existing user into an admin...
Yep, in preparation for my third E&I, I did this from my Tiger backup
disk, just in case. Also from my Tiger backup, before the third E&I, I
temporarily changed my "My Account" (admin) password, then changed it
back, so I wouldn't have an "old" 8 character password that Apple said
was causing the problem.
>
>
> However, I should add that if you do a clean install or an archive
> install,
> the problem should not arise, as there is no "my account" to lose -
> you are
> creating the only account during the installation, and that account
> is an
> admin account. m.
But if you do and E&I as I did , then migrate everything from your
backup, wouldn't you think everything, including your old "My Account"
would migrate? It was a puzzle, and very frustrating -- first
difficult OS transition I've every had.
OK -- I'm happy now with my install -- now I have to figure out how to
get my printer's "choices" back in place. Thanks for your response.
Joan
upstate NY
|
|
| |
scruffy
-
Nov 1, 2007 6:50 am
(#14 Total: 31)
|
 |
|
|
Re: Leopard Install Issues
On Oct 30, 2007, at 1:26 PM, Matt Neuburg wrote: On or about 10/29/07 6:36 AM, thus spake "Joan Miller"
<jdmiller twcny.rr.com>:
So none of you tidBITS readers have had difficulties with losing your
Keychain settings or losing your "My Account" with its Admin "power?"
I haven't seen this problem personally, but I know that many users have. I
thought that this was the sort of thing the new update from Apple was
supposed to fix:
http://www.apple.com/support/downloads/loginkeychainupdate10.html
my first install was on a Macbook and there were no problems there.
then i installed on a G5 iMac and ran into the keychain problem, even after running the login and keychain update immediately after installing.
Mail was complaining that it couldn't find my keychain file. i had to go to Keychain Access, select the login keychain, run Keychain First Aid on it, and then Make Default Keychain.
after that everything worked fine.
|
|
| |
|
|
Re: Leopard Install Issues
--On October 29, 2007 6:36:29 AM -0700 Joan Miller <jdmiller twcny.rr.com>
wrote:
> I can't find anything in either of the first two Taking Control of
> Leopard that will solve my dilemma.
> Help!
Skip the migration assistant during the original install. The account you
setup during the install is the admin account, use that to install the
patches, then run the migration assistant to pull your stuff over.
[But note that if you wait to use Migration Assistant, you'll have to use a different username for the transferred account. -Joe]
alternately after restoring your bootable backups, create a new admin
account with a simple username/password, login with that account and reset
the passwords on your other accounts to known passwords. then do the
install/migrate.
I think the first is more likely to work.
Kevin
|
|
| |
|
|
Re: Leopard Install Issues
On 11/01/2007 08:50 AM, "Brian Pearce" <red.jacket.press.mail gmail.com>
wrote:
>>> So none of you tidBITS readers have had difficulties with losing your
>>> Keychain settings or losing your "My Account" with its Admin "power?"
>
> I had lots of little irritating Keychain issues after the installation
> -- I was able to solve this when I noticed that I had a Keychain that
> had "MyUsername.keychain", but the System seemed to want (and had
> created) one called "login.keychain." So I just renamed my old
> keychain and ran it through Keychain First Aid, and it all seemed to
> work out okay.
You don't have to rename it. I get this when I'm testing Mac OS X 10.4
builds too. What you do is set the keychain you *want* to use to your
default keychain, then delete login.keychain.
--
John C. Welch
|
|
| |
|
|
Re: Leopard Install Issues
I installed Leopard yesterday. First it could not find my key chain even after I downloaded the update. I ran the Keychain first aid and the first time it failed; the second time it worked and everything was fine. It had also reset my Safari to old settings so I redid that. I let my computer sleep overnight and when I booted it up this morning, all my widgets had frozen, my Safari home page (Google news) and Safari once again had my old settings. Restarting my Mac fixed the widget problem but I had to once again customize my home page and remove old items from Safarfi's bookmarks menu. Anyone else have this problem?
Annette Stollman Bainbridge Island, WA
|
|
| |
|
|
Re: Leopard Install Issues
The thunderstorm was passing through. The power went out a couple of
times. In spite of my good judgment and my wife's objections, I
decided to install Leopard.
Luckily, by the time I started, the storm was gone. I put the DVD in
my Mac and told it to replace Tiger on my boot drive and held my
breath. I had read about all the precautions and different install
methods but I said what the hey. I like to live on the edge.
I held my breath but long and behold, the installation went very
smoothly. After booting up, all my preferences were back and it looked
almost as though I had not done anything. I had to try a few things to
make sure that Leopard was, in fact, my new OS.
It was probably the smoothest OS installation I'd done. Granted, I
have a few glitches and couple of things that do not work any longer
but they are quite minor. I may be one of the lucky few who did not
encounter any problems.
I must say Apple did a very good job.
--
Ryoichi Morita
|
|
| |
|
|
Re: Leopard Install Issues
On Nov 1, 2007, at 11:10 AM, Kevin van Haaren wrote:
> Skip the migration assistant during the original install. The
> account you
> setup during the install is the admin account, use that to install the
> patches, then run the migration assistant to pull your stuff over.
>
> [But note that if you wait to use Migration Assistant, you'll have
> to use a different username for the transferred account. -Joe]
>
> alternately after restoring your bootable backups, create a new admin
> account with a simple username/password, login with that account and
> reset
> the passwords on your other accounts to known passwords. then do the
> install/migrate.
>
> I think the first is more likely to work.
Thanks, Kevin; since I read that Apple suggested the Admin/password
problem originated with 8-or longer character passwords set before Mac
OS X 10.1, or some such thing, before I did my third (and successful)
E&I, I temporarily changed my Admin -- My Account -- password, then
changed it back to what it had been -- and that worked, or at least it
worked after that install. ("Of course") the Password/keychain
software update did nothing for my mission Keychain info -- and today
I discovered that Apple posted a fix for that -- and dated it Oct 26,
although I could swear it was not posted then, or others would have
mentioned it in Apple Discussions.
Previous transitions to newest Mac OS have been so simple -- this was
a puzzler for me!
Joan
|
|
| |
|
|
Re: Leopard Install Issues
On Nov 2, 2007, at 5:25 AM, Ryoichi and Janet Morita wrote:
> I may be one of the lucky few who did not
> encounter any problems.
I think you are part of the majority (is it "vast" or merely "large"?)
without significant problems.
--John
|
|
| |
|
|
Re: Leopard Install Issues
On Nov 2, 2007, at 8:25 AM, Ryoichi and Janet Morita wrote:
> I may be one of the lucky few who did not
> encounter any problems.
I think most users had good experiences. It's the ones who didn't
that you hear about.
Regards,
Howard
|
|
| |
|
|
Re: Leopard Install Issues
I had no problems installing OS X 10.5 on my G5 1.8 DP. I backed up my 10.49 disk to an external FW drive, did an "erase and install" on the internal HD. Then I used Migration Asst to bring over all the apps and prefs from the FW drive. Everything except a couple of utilities work fine. John W
|
|
| |
|
|
Re: Leopard Install Issues
If you are using FileVault, disable it before upgrading. Upgrading to
Leopard will corrupt the encrypted disk image, making it impossible
for you to login. (When the installation is complete, and you attempt
to log on for the first time, it will say that the home directory file
is corrupted and ask you if you want to fix it. If you choose to fix
it, the Mac will chug away for a minute or so and report that the
recovery failed. At this point, your home directory is toast.) The
frustrating part about all this is that none of the readme documents
warn you of this fact (it says that FileVault should be turned off on
UFS volumes, but that is the only reference to FileVault).
[I'm not a fan of FileVault, but it's untrue that ALL FileVault users will find their disk images corrupted by upgrading to Leoaprd. As you say, the issue you experienced may have involved preexisting corruption. -Joe]
The problem may have been a result of the fact that the home directory
file had gotten corrupt under Tiger. In fact, when I attempted to
disable FileVault, it gave me some message to that effect and also
corrupted the home directory beyond repair. Running the disk image
repair (as Apple recommends) with Disk Utility, results in the same
thing. I finally retrieved the FileVault image from backup, and
simply mounted it on the desktop and copied everything over to a spare
HD, and started from scratch.
What scares me about this whole episode is that Tiger gave no
indication of the fact that the FileVault image was corrupt to begin
with. It seems entirely possible that at some point the FileVault
image would have failed with little or no warning. So that will get
me to think twice about enabling FileVault again.
Also, if you are using a Mac with a Softraid volume as the boot drive
(using the Softraid Raid software, not Apple's Disk Utility), Leopard
will not install on the drive claiming that the drive is incapable of
booting the Mac. So this forces you to reformat the boot volume in
order to upgrade to Leopard (not a big deal given my other problem
above, but still). So, when Softraid says that Softraid 3.6.4 is
Leopard compatible, it seems just barely.
So, what I was hoping to be a couple-hour affair turned into a 24 hour
upgrade. Thank goodness for backups.
Tn
|
|
| |
|
|
Re: Leopard Install Issues
On Nov 3, 2007, at 10:19 AM, Howard Kaufman wrote:
> On Nov 2, 2007, at 8:25 AM, Ryoichi and Janet Morita wrote:
>
>> I may be one of the lucky few who did not
>> encounter any problems.
>
> I think most users had good experiences. It's the ones who didn't
> that you hear about.
I also had no problems, even though I did an upgrade install on my
MacBook Pro.
|
|
| |
|
|
Re: Leopard Install Issues
On 04/11/2007, at 01:32, Tomoharu Nishino wrote:
> If you are using FileVault, disable it before upgrading. Upgrading to
> Leopard will corrupt the encrypted disk image, making it impossible
> for you to login.
I have two Macs here which use FileVault and which have been upgraded
from Tiger to Leopard without this problem.
|
|
| |
|
|
Re: Leopard Install Issues
I installed Leopard on any empty 100 GB Partition on my NewerTech
MiniStack with no problems except I cannot seem to get Butler to
work. When I select its Icon in the menu, the Icon stays selected
with nothing happening. I used AppZapper to remove it and
reinstalled it, but no joy. It doesn't cause any problems, as I can
access all the other Icons on the menu, but when the pointer passes
over the selected Icon, it turns to a spinning beach-ball. Also, I
am unable to use either the backspace key or the return key in text
boxes in both Camino and Safari, but the enter key on the key paid
works just fine and as long as i am willing to select the text i want
to change, I am able to over write my typos. Very interesting problems. Also, some programs, such as Photoshop Elements 2 refuse to load but
PSE 4.0.1 loads just fine. I do want Path Finder to work without issues, but I expect that that
will come with time. I suspect that I will play with it and become accustomed to it until
at least version 10.5.1 before i commit myself to using it as my main
system. Also, I will no doubt still boot into Tiger to use some
programs including classic ones and i will keep my older Macs because
I need to use certain classic programs to print to some parallel dot-
matrix printers. ___________________________________________________
Michael Logue The Grateful Union
http://www.earthguild.com/ Earth Guild: Tools Materials Books
mlogue madison.main.nc.us
____________________________________________________
|
|
| |
|
|
Re: Leopard Install Issues
> [I'm not a fan of FileVault, but it's untrue that ALL FileVault
> users will find their disk images corrupted by upgrading to Leoaprd.
Of course not. Otherwise Apple wouldn't have released it. However,
given the number of Filevault related issues reported in places like
the Apple support forums, the problems may be quite widespread. So it
makes sense to disable FileVault prior to the upgrade as a precaution
(in addition to the usual one of making a full backup), even though
Apple doesn't tell you to.
> As you say, the issue you experienced may have involved preexisting
> corruption. -Joe]
The real problem (even if the upgrade is merely revealing a
preexisting corruption) is that FileVaults images can become corrupt
without any indication or warning along the way that this is
happening. (The FileVault protected account worked just fine under
Tiger, although presumably at some point I suspect that it would have
failed under Tiger as well.) This isn't really an "Leopard install
issue" to be sure, but a problem with the current implementation of
FileVault that the upgrade reveals.
Tn
|
|
| |
|
|
Re: Leopard Install Issues
One weird problem that I'm having with Leopard started just a few days
ago. Dashboard no longer works properly on my G5. When I press F12 the
screen darkens but none of my widgets display their windows. They are
all still there when I open up the widgets dock, but they just beep at
me when I click on them. I've blown away any .plist with dashboard in
it in my ~/Library, and I've used Time Machine to revert both Dashboard
and my widgets to their initial state, but nothing has worked. It all
still works right on my Powerbook G4.
--
Paul Schinder
schinder pobox.com
|
|
| |
|
|
Re: Leopard Install Issues
On Nov 6, 2007, at 13:28, Tomoharu Nishino wrote:
> The real problem (even if the upgrade is merely revealing a
> preexisting corruption) is that FileVaults images can become corrupt
> without any indication or warning along the way that this is
> happening. (The FileVault protected account worked just fine under
> Tiger, although presumably at some point I suspect that it would have
> failed under Tiger as well.) This isn't really an "Leopard install
> issue" to be sure, but a problem with the current implementation of
> FileVault that the upgrade reveals.
I ran into this -- it also is particularly unhelpful that drag-and-
drop copying will refuse to continue when erroring out on one file.
The problem files were almost always large (> 20 MB) media files.
TechTool Pro was unable to fix the .sparseimage.
The following procedure worked for recovery:
1. Mount FileVault image.
2. rsync -avE to an external drive
3. At various points, the rsync stalled and Activity Monitor.app
showed 50 MB/s disk write and no read.
4. Delete the corrupt file (or everything in the directory)
5. Restart (Tiger really does not handle corrupted disk images well)
6. Back to step 2.
7. Restore corrupted files from most recent backup.
Since Time Machine is full of fail when it comes to FileVault (only
backs up the discrete .sparsebundle, only upon logout), I've switched
my SOP to turning off FileVault for normal use and turning it on (plus
erasing free space) when bringing the laptop on an extended trip.
--
Brad Ackerman
brad facefault.org
|
|
| |
|
|
Re: Leopard Install Issues
after installing Leopard, i had lot's of keychain problems.
first everything went wrong, as I had an 8 character long password: my
user and login disappeared after the Leopard install, and when trying
to create a new user, system said, that this user already existed -
still it did not show in system preferences or remember the kogin.
finaly I changed the password to a shorter one, installed Leopard on a
clean disk and got my files and applications back from my backup.
Still keychain is not working. I installed Apples patch to solve the
problem, but it did not help.
I tryed keychain aid, it sais:
Warning: keychain ~/Library/Keychains/andreass is missing
the .keychain extension
Failed to rename ~/Library/Keychains/andreass to ~/Library/Keychains/
andreass.keychain, reason: Error Domain=NSCocoaErrorDomain Code=512
UserInfo=0x135890 "“andreass” could not be moved to “Keychains”."
...
Repair completed.
but after that it's just the same. no application can save to the
keychain: an alert pops up:
Keychain "andreass" cannot be found to store "..."
Your keychane may have been renamed, deleted, or it's on a unmounted
volume
Cancel / Reset To Deaults
It's not stored on another disk for sure - but wat exactly happens,
when I choose "Reset To defaults"
and how can I fix the problem?
Andreas
|
|
| |
|
|
Re: Leopard Install Issues
On or about 11/10/07 3:26 AM, thus spake "Andreas Steinmann"
<as-lists natfilm.dk>:
> after installing Leopard, i had lot's of keychain problems.
Did you run the Login & Keychain Update from Apple? It's supposed to help
with these problems (though I do not know whether it does in every case):
http://www.apple.com/support/downloads/loginkeychainupdate10.html
m.
|
|
|
TidBITS TidBITS TidBITS Talk Leopard Install Issues
|
|
