Getting a RDeploy "Memory allocation failed" error when trying to run a Create Disk Image job
Last Updated August 22, 2009
Getting a RDeploy "Memory allocation failed" error when trying to run a Create Disk Image job.
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.
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.
Applies To Deployment Server 6.8 through 6.9 SP2
Imported Document ID: TECH43468
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe