Getting a RDeploy "Memory allocation failed" error when trying to run a Create Disk Image job

Article:TECH43468  |  Created: 2009-08-04  |  Updated: 2009-08-04  |  Article URL http://www.symantec.com/docs/TECH43468
Article Type
Technical Solution

Product(s)

Issue



Getting a RDeploy "Memory allocation failed" error when trying to run a Create Disk Image job.

Environment



Deployment Server 6.8 through 6.9 SP2

Cause



Usually when memory allocation errors occur, it is because a filesystem on a hard drive is corrupt.  

Note: The rd.log file should indicate which partition it is trying to image when this error occurs.


Solution



You can run chkdsk (Windows) or fsck (Linux) to fix filesystem errors on the partition if the rd.log indicates that it was processing one of your normal partitions when it had an error. 

If the chkdsk or fsck utilities indicates that it is processing the OEM partition, try skipping the imaging of the OEM partition by adding a "-p2" switch to the Additional Parameters in the Create Disk Image task. 

Note: You can run the showdisk utility (found under the techsup directory on the eXpress share) to determine which partitions you want to process and then specify them with the -p switch.  For example, adding a "-p2 -p3" switch (no quote signs) will create an image of only partition 2 and 3 while skipping the OEM partition 1.


Legacy ID



48400


Article URL http://www.symantec.com/docs/TECH43468


Terms of use for this information are found in Legal Notices