You are not logged in.

Announcement

[2017.09.08] DeployStudio build v1.7.8 (checksum, release note).
[2016.08.26] DeployStudio build v1.6.19 (release note).
[2013.02.23] DeployStudio last universal build v1.5.17 (release note).

#1 2017-02-07 01:11:49

JustAnotherAdmin
Member
Registered: 2017-02-06

Image Scan Failing

Hi guys,

So on a brand new install of 1.7.6 I have encountered an issue I have never seen in DS before.

I am able to run an Mac (10.11) Image workflow successfully, it uploads the dmg successfully, and even creates the dss.scan job. However, this is as far as I get. The image remains stuck in the tmp folder. Upon checking the sys.log I see it is failing during the safeimagescan process and outputs "unable to read sectors 0x0489A028...0x0489C027 - image data corrupted" and will fail the scan which then aborts the runtime.


======


Feb  6 15:07:11 la-vmhost01 DeployStudioServer[99019]: Running safeimagescan.sh v1.2
Feb  6 15:07:11 la-vmhost01 DeployStudioServer[99019]: Image scan...
Feb  6 15:07:12 la-vmhost01 DeployStudioServer[99019]: Block checksum: ....10....20....30....40....50....60....70....80....90....100
Feb  6 15:14:48 la-vmhost01 DeployStudioServer[99019]: Block checksum: ....10....20....30....40....50....60....70....
Feb  6 15:14:48 la-vmhost01 DeployStudioServer[99019]: unable to read sectors 0x0489A028...0x0489C027 - image data corrupted.
Feb  6 15:14:48 la-vmhost01 DeployStudioServer[99019]: checksum failed at instruction 2, blocks 0x003E4028...0x05B1EE57 - image data corrupted.
Feb  6 15:14:48 la-vmhost01 DeployStudioServer[99019]: unable to calculate block checksum for blkx 1 - image data corrupted.
Feb  6 15:14:48 la-vmhost01 DeployStudioServer[99019]: unable to get UDIF info from "/Library/Server/Images/Masters/tmp/MacOS_02.06.17.i386.hfs.dmg" - image data corrupted.
Feb  6 15:14:48 la-vmhost01 DeployStudioServer[99019]: asr: image scan failed - image data corrupted.
Feb  6 15:14:48 la-vmhost01 DeployStudioServer[99019]: Failed scan the disk image '/Library/Server/Images/Masters/tmp/MacOS_02.06.17.i386.hfs.dmg', script aborted.
Feb  6 15:14:48 la-vmhost01 DeployStudioServer[99019]: RuntimeAbortScript



======


If I run fsck all checks out fine. If I repair permissions on the drive (while booted to another disk) it doesn't report any modifications and says the volume appears to be ok.


The drive that is being targeted for the image workflow is actually a modified version of a previous image that did successfully finish the runtime scripts and is available as a master within DS now. I have tried making the modifications to 2 different disks and both have failed with the same "image scan failed" issue.


I'm at a loss.... any ideas on how to get DS to play nice with these images?

Offline

#2 2017-02-07 02:07:26

JustAnotherAdmin
Member
Registered: 2017-02-06

Re: Image Scan Failing

Additionally...

Finder cannot mount the dmg and returns with "the following disk images could not be opened: Reason data corrupted".

As mentioned previously, the image that is failing the image scan is literally a modified version of an older image that works just fine. Finder can mount the original dmg just fine. The only difference between the two images is the install of some additional apps on the image that is failing.

This is not making very much sense to me that installing a couple apps could cause this big of an issue in DS.

Any thoughts?

Offline

#3 2017-02-07 18:54:12

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: Image Scan Failing

What happens if you recapture the drive imaged with just the previously successful image and no alteration (from the same disk that failed)?
When you say that you tried "2 different disks", was that on two different machines?

Last edited by Meat (2017-02-07 18:54:43)

Offline

#4 2017-02-07 19:33:46

JustAnotherAdmin
Member
Registered: 2017-02-06

Re: Image Scan Failing

For your first question, that tested out successful when I tried that. Any Yes to the second question, I used 2 different machines once my original test on the same machine failed with multiple drives.

However, I did end up getting this to work using the following method. On my image workflow I unchecked "try to create intermediate files on a local volume to preserve network bandwidth". This seems to have resolved the issue as it was able to successfully complete all jobs and has moved the dmg into the HFS folder finally.

Not sure how to explain this behavior because it seems like the use of these intermediate files (whatever purpose they serve) should theoretically be used exactly the same despite which drive they are used on. It would be nice if someone could offer an explanation.

Offline

Board footer

Powered by FluxBB