creating a 10.5 image problems

[larkost]

The chances that InstaDMG is going to get you any different result is near zero.

Try this:

1) Reboot (just to be certain you don’t have things open)

2) Run: sudo instaUp2Date.py –process 10.5_vanilla

If that works, then you know the problem is with your modifications. And I am pretty sure that it is going to work, since I have run it a few times in the last couple of days.

[Gary Bernstein]

Started this before seeing larkost’s comment:

ran: sudo ./instadmg/instadmg.bash -r -n KCPA-10-5-8-20100707 -m KCPA-10-5-8-20100707

debug.log:
11:52:39 ###### InstaDMG build initiated ######
InstaDMG version 1.6rc1 (svn revision: 309)
Host OS: Mac OS X 10.5.8
Host Hardware: MacPro3,1
Output file name: KCPA-10-5-8-20100707
Output disk name: KCPA-10-5-8-20100707
Host mount folder: /private/tmp/InstaDMG_temp_folder.0MUtbQ
11:52:40 ###### Finding main MacOS X installer disk ######
Found primary OS installer disk: ./InstallerFiles/BaseOS/Mac OS X Install DVD.dmg
11:52:40 ###### Looking for a Cached Image ######
Current image mount point: /private/tmp/InstaDMG_temp_folder.0MUtbQ/mount_point.C2zJRB
Shadow file location: /private/tmp/InstaDMG_temp_folder.0MUtbQ/F1311E31-2F1A-4ACA-B461-3E13E3D94E3A.shadowfile
Mounting the shadow file (/private/tmp/InstaDMG_temp_folder.0MUtbQ/F1311E31-2F1A-4ACA-B461-3E13E3D94E3A.shadowfile) onto the cached image (./Caches/BaseImageCache/480CC590.dmg)
expected CRC32 $382F3B33
/dev/disk3 GUID_partition_scheme
/dev/disk3s1 EFI
/dev/disk3s2 Apple_HFS /private/tmp/InstaDMG_temp_folder.0MUtbQ/mount_point.C2zJRB
Target OS: Mac OS X 10.5 (9A581)
Encasing installer daemon in a chroot jail
Chrooting com.apple.installdb.system daemon
11:54:15 ###### Beginning Update Installs from ./InstallerFiles/BaseUpdates ######
Working on folder 001 (11:54:15)
###### There were no items to install in: ./InstallerFiles/BaseUpdates/001 ######
11:54:15 ###### Cleaning up ######
Restoring normal installd daemon
Restoring com.apple.installdb.system daemon
Ejecting images
“disk3” unmounted.
“disk3” ejected.
Unmounted the Target Disk image from /private/tmp/InstaDMG_temp_folder.0MUtbQ/mount_point.C2zJRB
Deleting scratch DMG

Trying larkost’s comments …

[Gary Bernstein]

ran: sudo ./instadmg/AddOns/InstaUp2Date/instaUp2Date.py –process 10.5_vanilla
after a restart

debug.log:
12:00:14 ###### InstaDMG build initiated ######
InstaDMG version 1.6rc1 (svn revision: 309)
Host OS: Mac OS X 10.5.8
Host Hardware: MacPro3,1
Output file name: 10.5.8 Vanilla
Output disk name: Macintosh HD
Host mount folder: /private/tmp/InstaDMG_temp_folder.8OgAfL
12:00:15 ###### Finding main MacOS X installer disk ######
Found primary OS installer disk: ./InstallerFiles/BaseOS/Mac OS X Install DVD.dmg
12:00:15 ###### Looking for a Cached Image ######
Current image mount point: /private/tmp/InstaDMG_temp_folder.8OgAfL/mount_point.03BEsh
Shadow file location: /private/tmp/InstaDMG_temp_folder.8OgAfL/0312D533-ADF9-440A-8099-7350AFCEAC19.shadowfile
Mounting the shadow file (/private/tmp/InstaDMG_temp_folder.8OgAfL/0312D533-ADF9-440A-8099-7350AFCEAC19.shadowfile) onto the cached image (./Caches/BaseImageCache/480CC590.dmg)
/dev/disk3 GUID_partition_scheme
/dev/disk3s1 EFI
/dev/disk3s2 Apple_HFS /private/tmp/InstaDMG_temp_folder.8OgAfL/mount_point.03BEsh
Target OS: Mac OS X 10.5 (9A581)
Encasing installer daemon in a chroot jail
Chrooting com.apple.installdb.system daemon
12:00:20 ###### Beginning Update Installs from /tmp/InstaUp2DateFolder-GgW8fb ######
Working on folder 01 Mac OS X 10.5.8 Combo Update (12:00:20)
Mounting the package dmg: MacOSXUpdCombo10.5.8 sha1-0a88c9ecfbe08faf1a2307929c67f38b4822dfcb.dmg (/tmp/InstaUp2DateFolder-GgW8fb/01 Mac OS X 10.5.8 Combo Update) at: /private/tmp/InstaDMG_temp_folder.8OgAfL/mount_point.03BEsh/private/tmp/mount_point.VNDL9F
Mounting disk image from /Volumes/Users/Users/ciaoadmin/Desktop/instadmg/Caches/InstaUp2DateCache/MacOSXUpdCombo10.5.8 sha1-0a88c9ecfbe08faf1a2307929c67f38b4822dfcb.dmg at /private/tmp/InstaDMG_temp_folder.8OgAfL/mount_point.03BEsh/private/tmp/mount_point.VNDL9F
###### There were no items to install in: /private/tmp/InstaDMG_temp_folder.8OgAfL/mount_point.03BEsh/private/tmp/mount_point.VNDL9F ######
12:00:21 ###### Cleaning up ######
Restoring normal installd daemon
Restoring com.apple.installdb.system daemon
Ejecting images
“disk3” unmounted.
“disk3” ejected.
Unmounted the Target Disk image from /private/tmp/InstaDMG_temp_folder.8OgAfL/mount_point.03BEsh
###### Internal error: tried to eject an image from /private/tmp/InstaDMG_temp_folder.8OgAfL/mount_point.03BEsh/private/tmp/mount_point.VNDL9F but that path is not a directory ######
Deleting scratch DMG

Thanks for any help:
-Gary

[Gary Bernstein]

I made a little progress yesterday and I thought I should share it.

In instadmg/InstallerFiles/BaseUpdates I was placing all of the updates in individually numbered folders. For instance: BaseUpdates/001/MacOSX10.5.8.ComboUpdate.dmg or BaseUpdates/002/QuickTime7.6.6.dmg, and etc. When I did this I was getting the errors mentioned above. I did this because it was hinted at in the instadmg docs that this was a good way to go and to provide an order to the updates.

I found last night that if I move the files up one level and rename them that instadmg works. For instance: BaseUpdates/001MacOSX10.5.8.ComboUpdate.dmg or BaseUpdates/002QuickTime7.6.6.dmg, and etc.

I was then able to successfully run:

sudo ./instadmg.bash -r -n KCPA-1058 -m KCPA-1058

I am still unable to get InstaUp2Date to run on 10.5.8 and create a 10.5.8 disk image. I get an error about There were no items to install in /private/tmp/InstaDMG_temp_folder.4pYx6b/mount_point.jTh1nO/private/tmp/mount_point.mBDYKi

Thoughts?

Thanks
-Gary

[nobrainer]

[QUOTE][u]Quote by: Gary+Bernstein[/u][p]I made a little progress yesterday and I thought I should share it.

In instadmg/InstallerFiles/BaseUpdates I was placing all of the updates in individually numbered folders. For instance: BaseUpdates/001/MacOSX10.5.8.ComboUpdate.dmg or BaseUpdates/002/QuickTime7.6.6.dmg, and etc. When I did this I was getting the errors mentioned above. I did this because it was hinted at in the instadmg docs that this was a good way to go and to provide an order to the updates.

I found last night that if I move the files up one level and rename them that instadmg works. For instance: BaseUpdates/001MacOSX10.5.8.ComboUpdate.dmg or BaseUpdates/002QuickTime7.6.6.dmg, and etc.

I was then able to successfully run:

sudo ./instadmg.bash -r -n KCPA-1058 -m KCPA-1058

I am still unable to get InstaUp2Date to run on 10.5.8 and create a 10.5.8 disk image. I get an error about There were no items to install in /private/tmp/InstaDMG_temp_folder.4pYx6b/mount_point.jTh1nO/private/tmp/mount_point.mBDYKi

Thoughts?

Thanks
-Gary[/p][/QUOTE]

I tried the sudo ./instadmg -r and I still get

010-07-22 10:54:41.847 defaults[18141:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.I3oXw1/mount_point.tUFb0d/System/Library/CoreServices/SystemVersion, ProductVersion) does not exist
2010-07-22 10:54:41.857 defaults[18144:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.I3oXw1/mount_point.tUFb0d/System/Library/CoreServices/SystemVersion, ProductVersion) does not exist
2010-07-22 10:54:41.866 defaults[18146:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.I3oXw1/mount_point.tUFb0d/System/Library/CoreServices/SystemVersion, ProductBuildVersion) does not exist
2010-07-22 10:54:41.874 defaults[18147:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.I3oXw1/mount_point.tUFb0d/System/Library/CoreServices/SystemVersion, ProductName) does not exist
./instadmg.bash: line 700: [: 5: unary operator expected
Target OS: ()
Encasing installer daemon in a chroot jail

cp: /private/tmp/InstaDMG_temp_folder.I3oXw1/mount_point.tUFb0d/private/var/log/InstaDMG_package.log: No such file or directory

and then dumps out.

[nobrainer]

[QUOTE][u]Quote by: Gary+Bernstein[/u][p]I made a little progress yesterday and I thought I should share it.

In instadmg/InstallerFiles/BaseUpdates I was placing all of the updates in individually numbered folders. For instance: BaseUpdates/001/MacOSX10.5.8.ComboUpdate.dmg or BaseUpdates/002/QuickTime7.6.6.dmg, and etc. When I did this I was getting the errors mentioned above. I did this because it was hinted at in the instadmg docs that this was a good way to go and to provide an order to the updates.

I found last night that if I move the files up one level and rename them that instadmg works. For instance: BaseUpdates/001MacOSX10.5.8.ComboUpdate.dmg or BaseUpdates/002QuickTime7.6.6.dmg, and etc.

I was then able to successfully run:

sudo ./instadmg.bash -r -n KCPA-1058 -m KCPA-1058

I am still unable to get InstaUp2Date to run on 10.5.8 and create a 10.5.8 disk image. I get an error about There were no items to install in /private/tmp/InstaDMG_temp_folder.4pYx6b/mount_point.jTh1nO/private/tmp/mount_point.mBDYKi

Thoughts?

Thanks
-Gary[/p][/QUOTE]

I’m kind of at the same point, I renamed my update files and put them all in the base updates folder.. and I was able to run the instadmg.bash -r -n -m and the instadmg script ran through but none of the updates applied, I still have a 10.5.5 OS (instead of 10.5.8)

Checked the debug log, and while it continued on through the whole process… the actual logs showed every addon failed the install…

Install failed: The Installer could not install some files in “/private/tmp/InstaDMG_temp_folder.LWia2J/mount_point.VzhoKv”. Contact the software manufacturer for assistance.
The install failed (The Installer could not install some files in “/private/tmp/InstaDMG_temp_folder.LWia2J/mount_point.VzhoKv”. Contact the software manufacturer for assistance.)

I guess I will try an older instadmg script (this was 1.6rc1, rev: 318).

[nobrainer]

While using instadmg r261, I built a 10.5.8 using instadmg.bash -r -s -n “Macintosh HD” -m Mac1058_vanilla

I put all the updates in the installerfiles/baseupdates folder and renamed them as 01update, 02update, 03update

What did not appear to work was the CustomPKG files, so no clearreg, or admin account(s) created.

Soo…. anybody got any ideas for how to get the clearreg and admin account working?

[larkost]

The 10.5.8 updater will not work with the ‘-r’ flag. The chroot’ed installer code was put in place to handle the 10.5.7 and 10.5.8 updaters.

I have not been able to replicate any problems with the latest InstaDMG/InstaUp2Date running on 10.5.8 on Intel.

[nobrainer]

[QUOTE][u]Quote by: larkost[/u][p]The 10.5.8 updater will not work with the ‘-r’ flag. The chroot’ed installer code was put in place to handle the 10.5.7 and 10.5.8 updaters.

I have not been able to replicate any problems with the latest InstaDMG/InstaUp2Date running on 10.5.8 on Intel.[/p][/QUOTE]

I’m no where near considering myself an expert, I can only share what I found worked for me.

I do think there is a problem somewhere with instaDMG/InstaUp2Date. Maybe something your revision has or doesn’t have that others do/don’t. There looked to be several people with trouble with it (though you rarely hear about the ones that don’t have trouble).

I spent 4 full working days last week of between 9-11hrs each trying to get the instaDMG/InstaUp2Date working, different revisions, different hardware platforms, etc, and the above cmd line was the only way I got a working dmg file.

I’m more than willing to work with someone to narrow down the problems, so the next person can have a smoother experience. This is a GREAT treasure to find and the support community is top notch. I just wish I had the expertise to narrow down the trouble spot myself and constructively share 🙁

[Gary Bernstein]

I have just tried to use my 10.5 image that I thought was updated to 10.5.8 by using the combo updater. It appears to have ran but not installed the updates.

I must be missing something stupid, as this should not be this hard.

Any thoughts?

[Gary Bernstein]

[QUOTE][u]Quote by: larkost[/u][p]The 10.5.8 updater will not work with the ‘-r’ flag. The chroot’ed installer code was put in place to handle the 10.5.7 and 10.5.8 updaters.

I have not been able to replicate any problems with the latest InstaDMG/InstaUp2Date running on 10.5.8 on Intel.[/p][/QUOTE]

Perhaps you would be willing to put a 10.5.8 disk image that I could use as a starting point?

[nobrainer]

[QUOTE][u]Quote by: Gary+Bernstein[/u][p]I have just tried to use my 10.5 image that I thought was updated to 10.5.8 by using the combo updater. It appears to have ran but not installed the updates.

I must be missing something stupid, as this should not be this hard.

Any thoughts?[/p][/QUOTE]

Gary, that’s EXACTLY what I ran into a couple times that I was “successful” the DMG would finish, but when I would try and test deploy it, there would be no updates on it… I would go back through the logs and see that they all failed and I would still be on the original version of the OS 10.5.5

One thing to note – you can load the log files up in the console and watch them in real time to see if they fail… if they do fail you can abort the image and save yourself the time (a little trick I learned at the very end).

[Chris George]

I am running into the same issue as Mr. Bernstein above, running on 10.5.8 fully patched on an iMac 8,1. This is using InstaDMG 1.6rc1, svn 318, as checked out today.

Best as I can tell, it’s an issue with hdiutil or with the DiskImages framework, not the script. I tried manually executing hdiutil and mounting the 10.5.8 Combo image to the same directory as InstaDMG would be using, and I got the same “no mountable file systems,” yet if I just ran hdiutil with default options, the image mounted just fine. (I’m running DiskImages framework version 10.5.9, Source Version 2020000)

Here’s the portion of the debug log, following the OS install (which completed successfully):
[quote]20:24:21 ###### Beginning Update Installs from ./InstallerFiles/BaseUpdates ######
Working on folder 01 Mac OS X 10.5.8 Combo Update (20:24:21)
Mounting the package dmg: MacOSXUpdCombo10.5.8 sha1-0a88c9ecfbe08faf1a2307929c67f38b4822dfcb.dmg (./InstallerFiles/BaseUpdates/01 Mac OS X 10.5.8 Combo Update) at: /private/tmp/InstaDMG_temp_folder.nVw6E0/mount_point.1jRxcb/private/tmp/mount_point.lX0mVb
Mounting disk image from /Volumes/WIEBETECH/instadmg/Caches/InstaUp2DateCache/MacOSXUpdCombo10.5.8 sha1-0a88c9ecfbe08faf1a2307929c67f38b4822dfcb.dmg at /private/tmp/InstaDMG_temp_folder.nVw6E0/mount_point.1jRxcb/private/tmp/mount_point.lX0mVb
Checksumming Driver Descriptor Map (DDM : 0)…
Driver Descriptor Map (DDM : 0): verified CRC32 $54CBFDAD
Checksumming (Apple_Free : 1)…
(Apple_Free : 1): verified CRC32 $00000000
Checksumming Apple (Apple_partition_map : 2)…
Apple (Apple_partition_map : 2): verified CRC32 $11142F78
Checksumming Macintosh (Apple_Driver_ATAPI : 3)…
Macintosh (Apple_Driver_ATAPI : 3): verified CRC32 $F1E8BA9E
Checksumming (Apple_Free : 4)…
(Apple_Free : 4): verified CRC32 $00000000
Checksumming Mac_OS_X (Apple_HFS : 5)…
Mac_OS_X (Apple_HFS : 5): verified CRC32 $9CD9C0E6
Checksumming (Apple_Free : 6)…
(Apple_Free : 6): verified CRC32 $00000000
verified CRC32 $A5C1C2C1
hdiutil: attach failed – no mountable file systems
###### There were no items to install in: /private/tmp/InstaDMG_temp_folder.nVw6E0/mount_point.1jRxcb/private/tmp/mount_point.lX0mVb ######
20:24:50 ###### Cleaning up ######
Restoring normal installd daemon
Restoring com.apple.installdb.system daemon
Ejecting images
“disk3” unmounted.
“disk3” ejected.
Unmounted the Target Disk image from /private/tmp/InstaDMG_temp_folder.nVw6E0/mount_point.1jRxcb
“disk2” unmounted.
“disk2” ejected.
Unmounted the Supporting Disk image from /private/tmp/InstaDMG_temp_folder.nVw6E0/mount_point.OCoyLq
Deleting scratch DMG[/quote]

[Chris George]

For the record, I tried again on a MacBookPro 4,1 also running 10.5.8 and got the same results.

I also tried modifying the script to change from /private/tmp to just /tmp and still got the same results.

Last thing I’ll try is removing the InstaDMG_temp_folder.XXXXXX and putting everything right within /tmp, just to see what that does. I’m not holding my breath.

[Chris George]

Curiouser and curiouser. It worked.

I commented out lines 573-575 and inserted the following on line 576:
HOST_MOUNT_FOLDER=”/tmp”

I now need to go back and try and revert to /private/tmp (see my last post) and see if the changes hold. If so, it’s an issue with $MOUNT_FOLDER_TEMPLATE. If you’re working within /private/tmp you’re fine, but if you’re working within /private/tmp/InstaDMG_temp_folder.XXXXXXX, not so much.

Edit: Confirmed. Solution as noted above works; the only change required to resolve the issue is to comment out 573-575, and insert on 576:
HOST_MOUNT_FOLDER=”/private/tmp”

The build process is continuing at this time on my machine; I’ll let it finish and do my normal checks on the result, but I’m highly confident that it will be fine.

[Author]

Posts