Home Forums Software InstaDMG creating a 10.5 image problems

Viewing 15 posts - 1 through 15 (of 31 total)
  • Author
    Posts
  • #378963
    Gary Bernstein
    Participant

    I am trying to use instadmg / instaUp2Date (1.6rc1 rev 309) to create my first images. I tried making a 10.5.8 image using a retail 10.5 disk and the 10.5 vanilla catalog (adding the createuser.pkg) to it. The resultant image does not boot. The machine that I created it on is a 10.6.4 machine. After trolling the forum, it looks like the problem might be because I created it on a 10.6 machine, so I copied the entire instadmg folder to a 10.5.8 machine and when I run the instaUp2Date command I get:

    22:31:16 ###### 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: KCPA10-5-8
    22:31:17 ###### Finding main MacOS X installer disk ######
    Found primary OS installer disk: ./InstallerFiles/BaseOS/Mac OS X Install DVD.dmg
    22:31:17 ###### Looking for a Cached Image ######
    Mounting the shadow file (/private/tmp/InstaDMG_temp_folder.agg2Vy/9FAA2902-6E3C-4DA2-B500-7BDB618D6033.shadowfile) onto the cached image (./Caches/BaseImageCache/E556BB16.dmg)
    Target OS: Mac OS X 10.5 (9A581)
    Encasing installer daemon in a chroot jail
    Chrooting com.apple.installdb.system daemon
    22:31:22 ###### Beginning Update Installs from /tmp/InstaUp2DateFolder-JqCAtk ######
    Working on folder 01 Mac OS X 10.5.8 Combo Update (22:31:22)
    Mounting the package dmg: MacOSXUpdCombo10.5.8 sha1-0a88c9ecfbe08faf1a2307929c67f38b4822dfcb.dmg (/tmp/InstaUp2DateFolder-JqCAtk/01 Mac OS X 10.5.8 Combo Update) at: /private/tmp/InstaDMG_temp_folder.agg2Vy/mount_point.CFjHDl/private/tmp/mount_point.oXxnM4
    ###### There were no items to install in: /private/tmp/InstaDMG_temp_folder.agg2Vy/mount_point.CFjHDl/private/tmp/mount_point.oXxnM4 ######
    22:31:23 ###### Cleaning up ######
    Restoring normal installd daemon
    Restoring com.apple.installdb.system daemon
    Ejecting images
    ###### Internal error: tried to eject an image from /private/tmp/InstaDMG_temp_folder.agg2Vy/mount_point.CFjHDl/private/tmp/mount_point.oXxnM4 but that path is not a directory ######
    Deleting scratch DMG

    So, how can I create a bootable image of 10.5.8?

    Thanks
    -Gary

    #378974
    Allister Banks
    Participant

    Hey Mr.Bernstein,
    I have had a bunch of issues with 10.5recently with similar log output from instaUp2Date, I can try to backtrack versions until I find one that works. You may want to try using the instadmg.bash option to turn of jailing the installer daemon. I think only manually populating the directories(instead of passing the –process flag to instaup2date.py) was working. Please try a few updates and let us know if at least manually calling instadmg.bash works for you, I know even ‘manually'(without instaUp2Date) createUser wasn’t working for me as of ~r301.

    Allister

    #378975
    Gary Bernstein
    Participant

    Thanks. I’ll give that a try. One question, how does one backtrace the versions? I’m not finding it on the website.
    -Gary

    #378976
    Allister Banks
    Participant

    Hey Gary,
    Here’s a link to the googlecode view of the most recent revision of instadmg.bash,
    http://code.google.com/p/instadmg/source/browse/trunk/instadmg.bash?r=309
    I’m sure there’s the terminal way of doing this that’s more efficient, but if you follow the link you can then use the nav towards the upper-right(above the sidebars “hide details” button) to browse each previous version of instadmg.bash, same if your viewing the changes for instaUp2Date.py. Then you can svn down whichever rev you’d like to test with svn checkout URL -r 2xx PATH

    Allister

    #378978
    larkost
    Participant

    The latest 10.5 requires the chroot that I put in for 10.5, but that same system will not work for 10.6, the installer changed, and Apple has recently told me that they don’t consider this a bug/problem that they are going to fix. Without changes from Apple there is probably no chance that I can fix this.

    So if you are building 10.5 or 10.4 images then you need to be running from 10.5 (the latest version please). If you are making 10.6 images, then run 10.6 (once again: latest version). I should probably code this restriction in, like I have the one for not being able to create a newer version on an older OS.

    #378980
    Gary Bernstein
    Participant

    So, are you saying that the 1.6 release should work fine if I put it on a 10.5.8 machine to create a 10.5 disk image?

    #378982
    larkost
    Participant

    [QUOTE][u]Quote by: Gary+Bernstein[/u][p]So, are you saying that the 1.6 release should work fine if I put it on a 10.5.8 machine to create a 10.5 disk image?[/p][/QUOTE]

    In a word, yes.

    #378988
    Allister Banks
    Participant

    I’m testing clearreg.pkg as posted here on AFP548 and several versions of createUser and haven’t had any packages(bare .apps are not affected) in CustomPackages work, un-jailed installer daemons or not, called via instaUp2Date or not. This has been present for many revisions of instadmg.bash as far as I can tell, and although I’d like to file bugs, I’ve had limited access to the 10.5 system I build on to verify each issue.
    I’ll follow up with issue reports as soon as I’ve tested that just putting custom .pkgs in BaseUpdates doesn’t work.

    Allister

    #379004
    Gary Bernstein
    Participant

    I just placed instadmg on a 10.5.8 PPC machine and I am still unable to use instaup2date:

    14:08:28 ###### InstaDMG build initiated ######
    InstaDMG version 1.6rc1 (svn revision: 309)
    Host OS: Mac OS X 10.5.8
    Host Hardware: PowerMac11,2
    Output file name: 10.5.8 Vanilla
    Output disk name: KCPA10-5-8
    14:08:29 ###### Finding main MacOS X installer disk ######
    Found primary OS installer disk: ./InstallerFiles/BaseOS/Mac OS X Install DVD.dmg
    14:08:29 ###### Looking for a Cached Image ######
    No cached image found
    14:08:30 ###### Mounting Mac OS X installer image ######
    Mac OS X installer image mounted
    14:08:33 ###### Creating intermediary disk image ######
    Target image: /private/tmp/InstaDMG_temp_folder.BpPO1q/27A1E2B0-2F8B-438F-A5C5-5561CD16D3F2.sparseimage mounted successfully at: /tmp/mount_point.h4yJjm
    14:08:40 ###### Beginning Installation from /private/tmp/InstaDMG_temp_folder.BpPO1q/mount_point.KvdmUZ ######
    Installing system from: /private/tmp/InstaDMG_temp_folder.BpPO1q/mount_point.KvdmUZ onto image at: /tmp/mount_point.h4yJjm using language code: en
    Base OS installed
    Compacting and saving cached image to: ./Caches/BaseImageCache/F388EB24.dmg
    14:53:26 ###### Looking for a Cached Image ######
    Mounting the shadow file (/private/tmp/InstaDMG_temp_folder.BpPO1q/9A4E9126-D7C6-4330-B8C7-16983DA58551.shadowfile) onto the cached image (./Caches/BaseImageCache/F388EB24.dmg)
    Target OS: Mac OS X 10.5 (9A581)
    Encasing installer daemon in a chroot jail
    Chrooting com.apple.installdb.system daemon
    14:53:34 ###### Beginning Update Installs from /tmp/InstaUp2DateFolder-1tE2FN ######
    Working on folder 01 Mac OS X 10.5.8 Combo Update (14:53:34)
    Mounting the package dmg: MacOSXUpdCombo10.5.8 sha1-0a88c9ecfbe08faf1a2307929c67f38b4822dfcb.dmg (/tmp/InstaUp2DateFolder-1tE2FN/01 Mac OS X 10.5.8 Combo Update) at: /private/tmp/InstaDMG_temp_folder.BpPO1q/mount_point.H98xaE/private/tmp/mount_point.3APvyF
    ###### There were no items to install in: /private/tmp/InstaDMG_temp_folder.BpPO1q/mount_point.H98xaE/private/tmp/mount_point.3APvyF ######
    14:53:36 ###### Cleaning up ######
    Restoring normal installd daemon
    Restoring com.apple.installdb.system daemon
    Ejecting images
    Deleting scratch DMG

    I am going to try using instadmg manually…..

    #379005
    Gary Bernstein
    Participant

    So, what I am doing wrong:

    $ sudo ./instadmg/instadmg.bash -r -n KCPA-10-5-8-20100706 -m KCPA-10-5-8-20100706
    Password:
    17:32:08 ###### InstaDMG build initiated ######
    InstaDMG version 1.6rc1 (svn revision: 309)
    Host OS: Mac OS X 10.5.8
    Host Hardware: PowerMac11,2
    Output file name: KCPA-10-5-8-20100706
    Output disk name: KCPA-10-5-8-20100706
    17:32:09 ###### Finding main MacOS X installer disk ######
    Found primary OS installer disk: ./InstallerFiles/BaseOS/Mac OS X Install DVD.dmg
    17:32:09 ###### Looking for a Cached Image ######
    Mounting the shadow file (/private/tmp/InstaDMG_temp_folder.jAa6cw/336CD493-55C4-4DC0-9823-1C0355EAC703.shadowfile) onto the cached image (./Caches/BaseImageCache/F388EB24.dmg)
    Target OS: Mac OS X 10.5 (9A581)
    Encasing installer daemon in a chroot jail
    Chrooting com.apple.installdb.system daemon
    17:37:34 ###### Beginning Update Installs from ./InstallerFiles/BaseUpdates ######
    Working on folder 001 (17:37:35)
    ###### There were no items to install in: ./InstallerFiles/BaseUpdates/001 ######
    17:37:35 ###### Cleaning up ######
    Restoring normal installd daemon
    Restoring com.apple.installdb.system daemon
    Ejecting images
    Deleting scratch DMG

    Thanks

    #379006
    larkost
    Participant

    The debug log is going to have more details, try perusing that near the line from “17:37:34”. My guess is that a .dmg failed to mount, and a wild guess from there is that the .dmg was already mounted. Right now InstaDMG does not handle that case well.

    #379007
    Gary Bernstein
    Participant

    The section from the debug log:

    17:32:09 ###### Looking for a Cached Image ######
    Current image mount point: /private/tmp/InstaDMG_temp_folder.jAa6cw/mount_point.anLmRT
    Shadow file location: /private/tmp/InstaDMG_temp_folder.jAa6cw/336CD493-55C4-4DC0-9823-1C0355EAC703.shadowfile
    Mounting the shadow file (/private/tmp/InstaDMG_temp_folder.jAa6cw/336CD493-55C4-4DC0-9823-1C0355EAC703.shadowfile) onto the cached image (./Caches/BaseImageCache/F388EB24.dmg)
    Checksumming Driver Descriptor Map (DDM : 0)…
    Driver Descriptor Map (DDM : 0): verified CRC32 $E821D262
    Checksumming Apple (Apple_partition_map : 1)…
    Apple (Apple_partition_map : 1): verified CRC32 $20B9C230
    Checksumming disk image (Apple_HFS : 2)…
    disk image (Apple_HFS : 2): verified CRC32 $6911ADDF
    verified CRC32 $BCBA060B
    /dev/disk3 Apple_partition_scheme
    /dev/disk3s1 Apple_partition_map
    /dev/disk3s2 Apple_HFS /private/tmp/InstaDMG_temp_folder.jAa6cw/mount_point.anLmRT
    Target OS: Mac OS X 10.5 (9A581)
    Encasing installer daemon in a chroot jail
    Chrooting com.apple.installdb.system daemon
    17:37:34 ###### Beginning Update Installs from ./InstallerFiles/BaseUpdates ######
    Working on folder 001 (17:37:35)
    ###### There were no items to install in: ./InstallerFiles/BaseUpdates/001 ######
    17:37:35 ###### 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.jAa6cw/mount_point.anLmRT
    Deleting scratch DMG

    #379012
    larkost
    Participant

    I think I finally see a possible difference: you are running on PPC hardware. My only PPC hardware is running an old server, so no testing has been done. I will see if I can find some PPC hardware to try things out on.

    I have just confirmed that 10.5.8 image creation seems to be working fine on Intel, including the iLife updaters.

    #379013
    Allister Banks
    Participant

    So larkost, can you confirm custom packages are working in 10.5 on intel for you, because clearReg(which one would expect to do the most trivial of things) is not working for me. Nothing in the debug log to say why postflight can’t touch the file to /var/db, and it used to work previous to rev ~261(off the top of my head.)

    Also, shouldn’t instadmg.bash know its running on 10.5 and choose not jail the installer daemon? Even when called by instaUp2Date?

    Allister

    #379030
    Gary Bernstein
    Participant

    On a 10.5.8 Intel machine, I just install instadmg (315) and ran through the instaup2date process. I then ran: sudo ./instadmg/AddOns/InstaUp2Date/instaUp2Date.py 10.5_KCPA_vanilla.catalog –process

    This is the end of the debug.log:
    10:52:58 ###### Looking for a Cached Image ######
    Current image mount point: /private/tmp/InstaDMG_temp_folder.04lUHR/mount_point.40CRMs
    Shadow file location: /private/tmp/InstaDMG_temp_folder.04lUHR/7E0DE845-F2FF-439B-A680-86EB4E007145.shadowfile
    Mounting the shadow file (/private/tmp/InstaDMG_temp_folder.04lUHR/7E0DE845-F2FF-439B-A680-86EB4E007145.shadowfile) onto the cached image (./Caches/BaseImageCache/480CC590.dmg)
    /dev/disk4 GUID_partition_scheme
    /dev/disk4s1 EFI
    /dev/disk4s2 Apple_HFS /private/tmp/InstaDMG_temp_folder.04lUHR/mount_point.40CRMs
    Target OS: Mac OS X 10.5 (9A581)
    Encasing installer daemon in a chroot jail
    Chrooting com.apple.installdb.system daemon
    10:53:08 ###### Beginning Update Installs from /tmp/InstaUp2DateFolder-FRPV5j ######
    Working on folder 01 Mac OS X 10.5.8 Combo Update (10:53:08)
    Mounting the package dmg: MacOSXUpdCombo10.5.8 sha1-0a88c9ecfbe08faf1a2307929c67f38b4822dfcb.dmg (/tmp/InstaUp2DateFolder-FRPV5j/01 Mac OS X 10.5.8 Combo Update) at: /private/tmp/InstaDMG_temp_folder.04lUHR/mount_point.40CRMs/private/tmp/mount_point.sFO6CX
    Mounting disk image from /Volumes/Users/Users/ciaoadmin/Desktop/instadmg/Caches/InstaUp2DateCache/MacOSXUpdCombo10.5.8 sha1-0a88c9ecfbe08faf1a2307929c67f38b4822dfcb.dmg at /private/tmp/InstaDMG_temp_folder.04lUHR/mount_point.40CRMs/private/tmp/mount_point.sFO6CX
    ###### There were no items to install in: /private/tmp/InstaDMG_temp_folder.04lUHR/mount_point.40CRMs/private/tmp/mount_point.sFO6CX ######
    10:53:09 ###### Cleaning up ######
    Restoring normal installd daemon
    Restoring com.apple.installdb.system daemon
    Ejecting images
    “disk4” unmounted.
    “disk4” ejected.
    Unmounted the Target Disk image from /private/tmp/InstaDMG_temp_folder.04lUHR/mount_point.40CRMs
    “disk3” unmounted.
    “disk3” ejected.
    Unmounted the Supporting Disk image from /private/tmp/InstaDMG_temp_folder.04lUHR/mount_point.R0aXCW
    Deleting scratch DMG

    I am going to try running instadmg manually again now…

Viewing 15 posts - 1 through 15 (of 31 total)
  • You must be logged in to reply to this topic.

Comments are closed