Problems capturing Images

[Adrian Clint_1]

Had a very confusing day with images.

I am trying to capture an image of a BL35-SATA with Redhat 3U4. I'm using the builtin Read Linux image job of RDP 2.x with Hotfix2.
When the job runs the file is created but with 0KB size and the job does not appear to run rdeploy.

Now running a job to capture a windows image on a BL35-SAS server next to the other server works fine. Rdeploy creates Image file no problems.

Running the same windows image capture job on another BL35-SAS blade with just the FAT32 image on it - creates the name of the file but again like the linux image it bombs out leaving the file 0KB length.

So I can deduce that permissions are ok for filecreation in \lib\images and there is GB of space for the files.
Any idea's why I cannot create an image of a Linux server?

[Tr3nt]

I have similar problems with a bl35p SASS - 0 kb file is created however the image is not created.

What I did notice on the RDP server was memory usage maxed the available ram (4GB) and the windows page file maxed at 8GB. Any other session to the RDP server that launches the Deployment Console received "out of memory" messages.

RDP v3.0
BL35p with SASS drives
Trying to image a Windows 64bit OS