Trouble with installer.

Well, how much free space do you have?

 

me too!

Hi,

I have the exact same problem! The installer won't let me select a destination (it's grayed out in the list of steps it goes through), and tries to install on "(null)", whatever that is. I have more than 20Gb free space, but it tells me I'm out of space... This happens for all package installations. I get the same error log as red 2d2 too.

I'ts like the 'select destination or target select' part of the Install process is corrupt. How can we fix it?

Please help!

 

Hmm... Tricky... Do you have Boot Camp installed?

 

no i don't.

 

Okay, bugger. Check that the problem's exclusive to your Home folder. Open a new user account in System Preferences and see if you can mount from there.

 

Before doing that I would fsck/verify&repair the HD, and repair permissions. How-to's on Apple Support.

 

OK, I just tried that, new account, installed from there, but no joy, same problem...

thanks for taking an interest by the way!

 

OK, I'll have a look on Apple Support for all those procedures.

 

Well, you can bypass those methods by starting up in Safe Mode (boot while holding SHIFT). This will check your drive automatically and disable some third party features. Otherwise, just leap straight into fsck.

 

i did all the p-ram etc. still no joy.

fsck -f gave me this message:
'invalid node structure (4, 85) volume check failed"

is that bad? is there anything i can do? i haven't got disc warrior.

worried now...!

- grete

 

Did you do /sbin/fsck -fy to get it repaired or did it say it can't be repaired? Note the y after the f.

 

I just tried /sbin/fsck -fy several times.

i got the same message as before, invalid node structure etc...

 

I think you might need to get your hands on a copy of Disc Warrior or something similar. In the meantime, you can try starting from the OSX discs and using the bundled version of Disk Utility to try to repair your drive. It's essentially the same thing but booting from a separate CD/DVD may have more luck.

 

Thanks, I'll try that!

 

Schweet mate, tell us how it goes.

 

Did anyone who was having this problem solve it? If so--how did you do it? I am asking because I have been having the same problem. I tried some of the things mentioned already and I still have the problem.

Thank you,

SPG

 

I got DiskWarrior 4, and it fixed lots of faults which is good. However, Installer still doesn't work, oh well, at least I've got a healthy harddrive now.

- grete

 

I found this forum:

http://forums.appleinsider.com/showthread.php?t=66475

Where somebody posted:
"Well, I hacked it to work. Traced the error in the installer log to the TargetSelect.bundle. I replaced it with the same file from another mac, and now everything works smoothly."

I did what the poster did and it worked except after the Installer announced the installation a success, pressing "Continue" would not advance the program to the "Finish Up" stage (I haven't been able to successfully install for so long I don't even remember what the "Finish Up" stage looks like). I quit the installer anyway and discovered that the installation was indeed successful. I do not know why it wouldn't "finish up", nor what I may have missed out on by not being able to do so. I am running 10.4.8 and the mac that I got the file from was running 10.4.2.

If anybody thinks what I did was really bad, please let me (and anyone else with this problem who might do what I did) know.

Also, if anybody knows what happens during the "Finish Up" stage, please let me know.

SPG

 

interesting! i hope someone out there can enlighten us here...

- grete

 

Depending on the installer, I think the last couple of operations in Tiger involve updating prebindings (if applicable... this is something that used to be on the "to do" list in Panther but is essentially unnecessary in Tiger because it was wrapped into installations) and finalizing the receipt. But I'm not 100% sure about that.

Regarding the targetselect.bundle, it seems to be located inside the installer.app... and...suspicious... it contains localized versions.

Did anyone who had trouble in this thread by any chance use Monolingual or DeLocalizer?

 

I've encountered this from time to time typically with older installers on newer hardware/OS. The short-term fix is to go "back" and then "forward" within the installer and the correct volumes should appear.