- This topic has 16 replies, 8 voices, and was last updated 13 years, 9 months ago by
mlinde.
-
AuthorPosts
-
March 21, 2011 at 8:48 pm #380550
nobrainer
ParticipantSpoke too soon. Apple continues to fork us with multiple images.
March 22, 2011 at 12:11 am #380551bw38
ParticipantWhat a pain this is. I figured that 10.6.7 would be a universal update that included the early 2011 MBPs. This is rather frustrating. 👿
March 22, 2011 at 1:16 pm #380555nobrainer
Participantin the past, I’ve taken the 10.6.x delta image (the bigger one) layered that on, then taken the machine specific patch and layered that on. it’s worked well, booted all systems w/o issues. it’s allowed me to keep 1 image for all equipment…
March 22, 2011 at 3:19 pm #380558bw38
ParticipantJust to make sure I’m getting this right, I can add the general 10.6.7 combo update to my image, then add the 10.6.7 2011-MBP update into the image as well and this image would work on any Mac supporting Snow Leopard?
March 22, 2011 at 3:26 pm #380559nobrainer
ParticipantIt worked that way for the mini a while back, but it crashed on my test build 🙁
March 22, 2011 at 5:19 pm #380561Greg Neagle
Participant[QUOTE][u]Quote by: bw38[/u][p]Just to make sure I’m getting this right, I can add the general 10.6.7 combo update to my image, then add the 10.6.7 2011-MBP update into the image as well and this image would work on any Mac supporting Snow Leopard?[/p][/QUOTE]
I doubt it — if were that simple, Apple wouldn’t have released a separate update for the new MacBook Pros.
You’ll need two base images — one for Early 2011 MacBook Pros, and one for everything else. The one for Early 2011 MacBook Pros should probably be built from a Early 2011 MacBook Pro + the 10.6.7 update for the Early 2011 MBPs. The other one can be built from a retail release of Snow Leopard and then brought to either 10.6.6 or 10.6.7 via Combo Update.
March 22, 2011 at 11:42 pm #380563Tim Sutton
ParticipantBut therein lies the facility of instadmg to minimize the overhead of maintaining different images. Just build your instaUp2Date catalog off the mbp grey disc instead of the retail generic build, and you have an identical image save for the driver differences between the retail and hardware-specific builds.
March 24, 2011 at 8:41 pm #380568typofonic
Participant[QUOTE][u]Quote by: cygnus2112[/u][p]But therein lies the facility of instadmg to minimize the overhead of maintaining different images. Just build your instaUp2Date catalog off the mbp grey disc instead of the retail generic build, and you have an identical image save for the driver differences between the retail and hardware-specific builds.[/p][/QUOTE]
Hi,
I just tried building an image using a 10.6.6 BaseImage from a 2011 MacBook Pro 15″. I updated instaDMG to the newest version from the svn, updated my catalogs with the 10.6.7 2011 specific update and ran InstaDMG. Unfortunately I got this error:
[code]Finding the Installer disc for setup
Traceback (most recent call last):
File “./instaUp2Date.py”, line 716, in
main()
File “./instaUp2Date.py”, line 678, in main
foundInstallerDiscs = findInstallerDisc.findInstallerDisc(allowedBuilds=thisController.installerDiscBuilds)
File “/Volumes/Lacie/instadmg/AddOns/InstaUp2Date/Resources/findInstallerDisc.py”, line 201, in findInstallerDisc
raise commonExceptions.FileNotFoundException(‘Unable to find OS Installer disc in any provided folder: %s%s’ % (str(searchItems), folderString))
Resources.commonExceptions.FileNotFoundException: Unable to find OS Installer disc in any provided folder: [‘/Volumes/Lacie/instadmg/InstallerFiles/InstallerDiscs’, ‘/Volumes/Lacie/instadmg/InstallerFiles/BaseOS’] ([‘.DS_Store’, ‘.svn’, ‘Mac OS X Install DVD.dmg’], [‘.DS_Store’, ‘InstallerChoices.xml’, ‘Mac OS X Install DVD.dmg’])
[/code]Can’t quite wrap my head around what’s missing :-/ Any ideas?
March 25, 2011 at 2:38 am #380571Tim Sutton
ParticipantIf you ran importDisk.py on the MBP grey disc, it should spit out a file like “MacOS X Client 10.6.6 10G3210.dmg” in InstallerFiles/InstallerDiscs. (I don’t remember if that’s the correct build no. for the 17″ MBP I did last week)
instaUp2Date will check the catalog you’re building (and its includes) for the “Installer Disc Builds:” settings line, which should contain the same build no. of the install disc you want to use. If, for example, you want to build your 10.6_vanilla image with this specific build, modify the catalog or create a new one, to include only the build no. you want. I don’t know how instaUp2Date prioritizes build no.’s if it finds multiple candidates for a catalog in InstallerDiscs.
March 25, 2011 at 9:29 am #380572typofonic
ParticipantThanks for your answer. I actually did this (and had the same build of 10.6.6). But it just doesn’t find it.I also tried downgrading findInstallerDisc.py to an older version with no luck. It seems though to be a known problem:
[url]http://code.google.com/p/instadmg/issues/detail?id=79[/url]I tried ejecting all disks (which is described on the page above), and this actually worked when running InstaDMG by itself! But instaUp2Date still gives me the same error, so the installation can’t be setup properly.
Any ideas?
March 25, 2011 at 12:38 pm #380573foilpan
Participanttry removing or commenting out the “Installer Disc Builds” line and running it again. i’ve built a few images using the new build discs that ship with these laptops, and they’ve worked fine for me.
March 25, 2011 at 1:23 pm #380574Tim Sutton
ParticipantYes, when I first started using instaUp2Date I would get that error frequently. I don’t recall there being a definitive conclusion as to why it happens for people, though I’ve heard of reboots fixing it. It could also be that there are still processes running from a previous build if it was ever aborted — if I ever abort a previous run, I ctrl-C a few times, and check that the various disk image-related processes and python are no longer running.
March 25, 2011 at 4:35 pm #380575Allister Banks
ParticipantInstaller Disc Builds: 10J3210
Output Volume Name: Macintosh HD
Output File Name: 10.6.7 VanillaThunderholeOS Updates:
MacOSXUpd10.6.7MBPEarly2011 http://supportdownload.apple.com/download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/Mac_OS_X/downloads/041-0170.20110321.Cdfr4/MacOSXUpd10.6.7MBPEarly2011.dmg sha1:846e776582678d8ec3683d3466b239acda34c110
Apple Updates:
Safari5.0.4SnowLeopard http://appldnld.apple.com/Safari5/041-0045.20110308.Frd54/Safari5.0.4SnowLeopard.dmg sha1:32afa782aefb1174359550b8167311cfe4854680
RemoteDesktopClient http://supportdownload.apple.com/download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/Mac_OS_X/downloads/041-0011.20110106.Ply65/RemoteDesktopClient.dmg sha1:46df7a3b31cd2b51213e1a6fd193d5073c004771
JavaForMacOSX10.6Update4 http://supportdownload.apple.com/download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/Mac_OS_X/downloads/061-9741.20110308.JavQ3/JavaForMacOSX10.6Update4.dmg sha1:513d5c5b62fb1257b8bf582c1c11e02e944fa808
iTunes10.2.1 http://appldnld.apple.com/iTunes10/041-0475.20110308.mAcaz/iTunes10.2.1.dmg sha1:27fa797873c68b44017a6769b9057e8428d54da8March 25, 2011 at 4:36 pm #380576Allister Banks
ParticipantAll credit(or blame) for previous catalog to @chilcote, I tested it on a 15″ today and its up to date. Reference for build number: http://support.apple.com/kb/ht1159
June 17, 2011 at 3:07 pm #380835mlinde
ParticipantLooking for a good thread to work from, I’ll use this one.
I’m running into a strange problem with the current (Late 2010/Early 2011) MacBook Air.
I am able to get a base image from the install flash drive using apple’s SIU instructions, and that will install fine.
I went to build an image, with that and core OS updates (I ignored iLife/additional apps at first), and it won’t process the updates.Here are my logs, it shows the error but I don’t know how I’m supposed to work around this. I never had to do anything special before…
10:11:03 ###### Beginning Update Installs from ./InstallerFiles/BaseUpdates ######
Working on folder 1 (10:11:03)
Copying folder ./InstallerFiles/BaseUpdates/1 into the target at /private/tmp/package.qJfEab
Installing MacOSXUpdCombo10.6.7.pkg from ./InstallerFiles/BaseUpdates/1 (1) inside a chroot jail
installer: Error trying to locate volume at /
Removing the copied folder: /private/tmp/mount_folder.GBpWBn/mount_point.GWjzcf/private/tmp/package.qJfEab
Folder 1 done (10:12:02)
Working on folder 2 (10:12:02)
Copying folder ./InstallerFiles/BaseUpdates/2 into the target at /private/tmp/package.vMEyPP
Installing MacOSXUpd10.6.7Supp.pkg from ./InstallerFiles/BaseUpdates/2 (2) inside a chroot jail
installer: Error trying to locate volume at /
Removing the copied folder: /private/tmp/mount_folder.GBpWBn/mount_point.GWjzcf/private/tmp/package.vMEyPP
Folder 2 done (10:12:02)I deleted my cached base image, it still doesn’t work.
Thanks!
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed