Re: Random installation failures with packages in disk images.
Re: Random installation failures with packages in disk images.
- Subject: Re: Random installation failures with packages in disk images.
- From: "Kevin Harris" <email@hidden>
- Date: Wed, 3 Jan 2007 23:03:30 -0700
On 1/3/07, John Daniel <email@hidden> wrote:
The next time this happens, use the Terminal to see what is going on
inside the /Volumes directory. I have seen situations where an
installer volume did not get mounted or unmounted properly and I
would wind up with something that looks like:
/Volumes/Decoder
/Volumes/Decoder 1
Thanks for the suggestions.
I've seen that quite a few times. Unfortunately, this isn't one of
those cases. The path where the package was located was complete,
could be examined, and could even be copied elsewhere. The only hint
that something was wrong was the breakage reported by the installer.
I have seen the installer complete successfully if I ditto that
"invalid package path" somewhere else and install it from there.
The /Volumes/Decoder directory is invalid and has nothing in it. The /
Volumes/Decoder 1 path is where the DMG actually got mounted. Once
this starts happening, your file system is fairly scrambled and
you'll need to reboot. This only happened when I was building and
We don't normally run into problems with multiple mounts because we
parse the xml (plist) spit out by hdiutil to determine the mount
point.
When I've seen the files in /Volumes in the strangest state (unrelated
to the current problem) is normally when hdiutil info reports the
mount point for some volume as a non-existent /Volumes/8NpfS78@jf or
something like that (I can't find my log that shows that particular
breakage). In cases that severe (which were only common on 10.3, and
only on an automated build machine), I've normally had to kill a few
hundred diskarbitrationd processes to regain functionality of hdiutil.
testing the DMG files. So, if you are mounting/unmounting the same
DMG file with the same volume name several dozen times, you may get a
failure. It is unlikely that an end user would see this.
Unfortunately, we are having "clean" machines that are running into
this problem. I have not yet seen it happen on an Intel machine, but
we have far more PPC machines.
You can't see anything wrong from the Finder. You have to use the
Terminal. If this is also what you are experiencing, just reboot.
Rebooting does seem to solve the problem, but the indications you
mention aren't present. Unfortunately, rebooting is not a viable
option for most of our customers, should they encounter this. They
tend to do an automated install of the software on many machines in
parallel, and picking out a few sick machines for reboot would be a
hassle. It would be even worse if it happened in an upgrade and a few
but not all of our packages were successfully upgraded.
Thanks again.
-Kevin-
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden