Closed spikehed closed 10 years ago
What does asr imagescan --source "/Volumes/Data_Drive/AutoDMG Builds/DCL_Mavericks_140321-10.9.2-13C64.hfs.dmg" say?
whqd96310m:AutoDMG Builds dcadmin$ asr imagescan --source "/Volumes/Data_Drive/AutoDMG Builds/DCL_Mavericks_140321-10.9.2-13C64.hfs.dmg" Block checksum: ....10....20....30....40....50....60....70....80....90....100
Catalog file is too fragmented for restore.
Try "fsck_hfs -r" on writeable copy of the image volume
unable to get UDIF info from "/Volumes/Data_Drive/AutoDMG Builds/DCL_Mavericks_140321-10.9.2-13C64.hfs.dmg" - Bad file descriptor.
asr: image scan failed - Bad file descriptor.
On Mar 21, 2014, at 12:34 PM, MagerValp notifications@github.com wrote:
What does asr imagescan --source "/Volumes/Data_Drive/AutoDMG Builds/DCL_Mavericks_140321-10.9.2-13C64.hfs.dmg" say?
— Reply to this email directly or view it on GitHub.
AutoDMG 1.2.1 using same source and destination completes successfully ...
2014-03-21 14:06:16 Notice: Starting phase: Finalizing disk image 2014-03-21 14:06:16 Notice: Finalize task running 2014-03-21 14:06:16 Info: Launching finalize with arguments: 2014-03-21 14:06:16 Info: '/Users/dcadmin/Applications/AutoDMG.app/Contents/Resources/progresswatcher.py' 2014-03-21 14:06:16 Info: '--socket' 2014-03-21 14:06:16 Info: '/tmp/se.gu.it.IEDSocketListener.a6414d81890e19fc' 2014-03-21 14:06:16 Info: 'imagescan' 2014-03-21 14:06:16 Info: '/Volumes/Data_Drive/AutoDMG Builds/DCL_Mavericks_140321-0200-10.9.2-13C64.hfs.dmg' 2014-03-21 14:06:17 Notice: Script phase: asr1 2014-03-21 14:06:17 Debug: (IEDWorkflow:321) nextPhase 2014-03-21 14:06:17 Notice: Starting phase: Finalizing disk image 2014-03-21 14:06:17 Notice: Script phase: asr2 2014-03-21 14:06:17 Debug: (IEDWorkflow:321) nextPhase 2014-03-21 14:06:17 Notice: Starting phase: Finalizing disk image 2014-03-21 14:07:10 Notice: Script phase: asr3 2014-03-21 14:07:10 Debug: (IEDWorkflow:321) nextPhase 2014-03-21 14:07:10 Notice: Starting phase: Finalizing disk image 2014-03-21 14:07:15 Debug: (IEDWorkflow:303) nextTask 2014-03-21 14:07:15 Notice: Starting task with 1 phases 2014-03-21 14:07:15 Debug: (IEDWorkflow:321) nextPhase 2014-03-21 14:07:15 Notice: Starting phase: Finishing 2014-03-21 14:07:15 Notice: Finish 2014-03-21 14:07:15 Debug: (IEDWorkflow:303) nextTask 2014-03-21 14:07:15 Notice: Build finished successfully, image saved to /Volumes/Data_Drive/AutoDMG Builds/DCL_Mavericks_140321-0200-10.9.2-13C64.hfs.dmg
Thanks, it looks like the automatic image size algorithm is making the image too small. Are you including a lot of packages? What size does AutoDMG select for the image?
Hope this is the relevant section... Not allot of packages - the ones included in the "Updates" plist and just 2 extra (your CreateUserPkg and another (skip registration,etc) - fairly innocuous stuff here. I don't pre-load my images w/ everything.
21 packages to install: /private/tmp/dmg.PE1v4F/Packages/OSInstall.mpkg /Users/dcadmin/Library/Application Support/AutoDMG/Updates/iBooksDelta.pkg /Users/dcadmin/Library/Application Support/AutoDMG/Updates/BookKitDelta.pkg /private/tmp/dmg.s032W4/QuickTimePlayer7.6.6_SnowLeopard.pkg /private/tmp/dmg.wgFkqv/ProAppsQTCodecs.pkg /private/tmp/dmg.jQ6V2f/Uncompressed422.pkg /private/tmp/dmg.eaxmuW/Install iTunes.pkg /private/tmp/dmg.0A038H/RAWCameraUpdate5.pkg /private/tmp/dmg.3hunXt/JavaForOSX.pkg /private/tmp/dmg.m2sBLN/HewlettPackardPrinterDrivers.pkg /private/tmp/dmg.2QOmdl/SamsungPrinterDrivers.pkg /private/tmp/dmg.BYHOxy/LexmarkPrinterDrivers.pkg /private/tmp/dmg.3ZIsBW/EPSONPrinterDrivers.pkg /private/tmp/dmg.K3Ghej/CanonLaserPrinterDrivers.pkg /private/tmp/dmg.spWjgf/CanonPrinterDrivers.pkg /private/tmp/dmg.SSjSOk/BrotherPrinterDrivers.pkg /private/tmp/dmg.imKRZF/FujiXeroxPrinterDrivers.pkg /private/tmp/dmg.CnyvKT/XeroxPrinterDrivers.pkg /private/tmp/dmg.noTejR/RicohPrinterDrivers.pkg /Volumes/Data_Drive/AutoDMG_Extras/clearReg.pkg /Volumes/Data_Drive/AutoDMG_Extras/create_dcadmin-1.4.pkg Workflow requires a 12.2 GB disk image Using a 14 GB disk image
trying to find 'size' for the successful 1.2.1 build is this it? Surely seems enough... final images come in around 9.04 GB unless 'more' padding needs to be built in for installs before finalization? 2014-03-21 13:43:47 Info: installer.Debug: Total install size including padding: 8232985600 b + 0 b non-OS collection items 2014-03-21 13:43:50 Info: installer.Notice: Calculating expected install size requirements 2014-03-21 13:56:54 Info: installer.Notice: presize 2.01 seconds 2014-03-21 14:06:16 Info: File size: 9059791605 bytes, Checksum: CRC32 $2DDBB074
1.0 - 1.2.1 all use a 32 GB image size (before compression). Try this build:
https://www.dropbox.com/s/b7llco1vpwkw5i3/AutoDMG-1.3b231.dmg
Result:
Starting phase: Finalizing disk image phase: Finalizing disk image Finalize task running message: Scanning disk image for restore Launching finalize with arguments: '/Applications/AutoDMG.app/Contents/Resources/progresswatcher.py' '--socket' '/tmp/se.gu.it.IEDSocketListener.bd42e61ce2d1d97f' 'imagescan' '/Volumes/Data_Drive/AutoDMG Builds/DCL_Mavericks_140321-10.9.2-13C64.hfs.dmg' Script phase: asr1 Phase Finalizing disk image with weight 2097152 finished after 1.141 seconds Starting phase: Finalizing disk image phase: Finalizing disk image Task exited with status 1 Workflow failed: Build failed (Task exited with status 1) Build failed: Build failed Task exited with status 1
Did it try a 16 GB image this time, but still failed with the same asr error?
Oh, and as a workaround for now you can put a VolumeSize of 32 in your template.
apologize - should have mentioned that. Yes 16GB image - error reports different (Exited status 1) - going to reboot the comp and try again - see if anything different.
I suppose I missed seeing the VolumeSize option in the template. It was not even defined in my template - so trying again with a set VolumeSize limit now - suspect it will work this time. So are we to assume that having it set to automatic is still not going to work?
Successful! Thanks for your assistance!
Yeah, my automatic calculation didn't leave enough headroom and caused a fragmented catalog. I've adjusted it so that it starts at 32 GB and grows from that, instead of the minimum 10 GB. Hopefully automatic should work for you with b232:
https://www.dropbox.com/s/q0r99kauqkt1pdj/AutoDMG-1.3b232.dmg
Otlichno!! Thanks Per, the last build was a success via CLI.
Great, closing this as fixed.
AutoDMG 1.3b220 doesn't finish ASR finalize step (log below) Built on iMac 13,2 10.9.2C64 Occurred both on CLI and GUI (image completes but haven't tested imaging w/ it)
Starting phase: Finalizing disk image phase: Finalizing disk image Finalize task running message: Scanning disk image for restore Launching finalize with arguments: '/Applications/AutoDMG.app/Contents/Resources/progresswatcher.py' '--socket' '/tmp/se.gu.it.IEDSocketListener.076a9c3ccd226021' 'imagescan' '/Volumes/Data_Drive/AutoDMG Builds/DCL_Mavericks_140321-10.9.2-13C64.hfs.dmg' Script phase: asr1 Starting phase: Finalizing disk image phase: Finalizing disk image Task exited with status 1 Workflow failed: Build failed (Task exited with status 1) Build failed: Build failed Task exited with status 1 2014-03-21 08:37:10.593 AutoDMG[88112:4307] PyObjC: Converting exception to Objective-C: sys.excepthook is missing lost sys.stderr