Deployment Solution

We are getting the 'memory allocation failed' error during image creation on Dell 760s.  We can push images to the machines just fine, though.  We've already tried changing the settings in config.sys (we're using MS-DOS to image) with no luck. 

It looks like other users are getting this error and getting mixed results when it comes to solutions.  Dell tech support redirected us to the config.sys kb 35816...so no help there.

We are on DS 6.9 build 375 SP2

Any ideas?

Mike

Hi Mike,

I've found that I've had some problems here and there in imaging some of the newer Dell machines and using the DOS environment.  I have since switched over to using Linux for most of the equipment and it seems to work fine over there.  By doing this you will also enjoy a much faster throughput (both in Linux and WinPE) as they can take advantage of the faster network cards.

You might give one of these environments a try to see if it takes care of your problem.

I'm getting that 'The disk was not found." error...

Did you add the ahci.ko file to the linux pxe-boot environment?  I put mine in the 'Linux additional files' folder, but that hasn't made any difference.

wait...ok, i found where to add the driver files, so that should work now.  what does your path look like in the job details?  do you have something like /mnt/ds/Images/pathtofile.img  or does the /mnt/ds need to be there?  The path I have for DOS imaging is .\Images\pathtofile.img.

Mike

Mine uses .\images\pathtofile.img

This assumes that /mnt/ds is mounted to \\*ALTIRISSERVER*\express

Also, I have "Disable image path validation" checked.

out of memory error again.  and the status detail of the job shows 'Error -99 during imaging process'

Mike,

I'm not sure what the problem is.  If you have an active AUP, you might contact Altiris support and see what they have to say about it.  I would be curious how it does get resolved as at some point, my company may be forced into using the 760s or newer.

-B

Yeah, it's strange, we got one 760 a few months ago, and it has worked fine.  We got more a couple of weeks ago and they are the ones having this problem.  As far as we can tell, everything about the systems is same.  I'll keep looking into it and post a resolution when I find one.

Just got a lot of new 760's myself and got this.  Have any luck yet?  Using DS 6.9 SP2, DOS or WinPE here.  Server is 2003 or 2008 and SQL 2005.

I opened a case with support and have tried WinPE, but I'm still getting the same 'memory allocation failed' error.  I'm currently waiting for a call back from support.  Have you opened a case with support? 

Since you're getting the same error, it's looking more like a specific issue with the Dell 760s.  I've tried DOS, Linux, and Windows, so it doesn't seem like just a driver issue and KB 35816 doesn't help...

rdlog:

Error description:
Memory allocation failed.
(Note: Current volume is OEM from source slot 1.)

Possible causes:
Out of memory.

Possible resolutions:
Install more memory.
Delete some files on the computer you're imaging.


==================== Technical details ====================

Logfile = created Thu Jul 23 08:11:28 2009
Build = RdeployT.exe 6.9 (9024)
Cmdline = F:\RDeploy\Windows\RdeployT.exe -noprompt -mu -f.\Images\d_drive\dell760\winpe\winpe.img -cspeed -split:2040 -dsstatus:10.10.10.3:402 -mcint:10.52.2.28

Status = 5 (0x5)
Source file = imglib\common\abuffer.cpp
Line number = 183 (0xb7)
Stack trace = 0x4c7f6c 0x4c7fb7 0x4af4c4 0x484cd1 0x487642 0x4149ef 0x40352a 0x412294 0x401db0 0x40e42d &Known=0x433e40
Note = Current volume is OEM from source slot 1.
Imaging library revision = 9024 (win32-x86-release build, Thu Jan 29 16:47:10 2009)

Working with tech support, we got Ghost to pull/create an image, so that's good.  Tech support is investigating further.

I was wondering if  tech support ever got back to you on this issue.  I am having the same problem with my new Dell Opti 960's.  I have tried all the tweeks that I have seen in these forums to no avail.
Please let me know if anyone has a fix.

No word from tech support, yet.  Last I heard they were going to try to get their hands on a 760 to troubleshoot with.  So ghost didn't work with the 960s?

I am not using Ghost, I am using Altiris Deployment Solutions.
I am going to install WinPE right now and give that a test.
If it works I will post results.

 Hi,

I've seen something like these error -99 issues a while back, but only when using ImageExplorer to edit the images. In my case I had folder excludes.

If you are using folder/file excludes, I'd try recreating your image so that you don't need to use these.

Kind Regards,
Ian./

It is trying to pull the image from slot 1.  That is the 40mb FAT partition.
Use the OS disk to remove the unwanted 40mb partition and that should do it.
Just an FYI, I did not use the universal NIC driver that I have always used in the past.  I downloaded the e1000.dos.  I dont think this has anything to do with the problem (just removing the partition should work) but just wanted to let you know.
Good Luck.

Has anyone tried removing that partition?  It seems like it would be a lot of work to have to manually remove a partition from however many machines you ordered - possibly hundreds.

You only have to remove the partition from the 1 computer you set up for the image.
When you push the image it will over write the entire hard drive.
That partition was using "slot 1"  That is why I was getting the memory allocation error.

I can confirm this EXACT error ("Memory allocation failed - error 5") on an Optiplex 960.  Boot with a Windows CD and delete the OEM partition (it's about 40 MB)  Restart your image creation job and the image creates properly.

If you are using AHCI/RAID, switch to ATA if you are using a standard XP installation disk in order to delete the partition or it will blue-screen (no AHCI support on a standard XP installation CD).  Switch it back to AHCI/RAID when you are done deleting the partition.

Create your image and when you DEPLOY it, you can use the "Distribute Disk Image Advanced" option and under "Additional Options" you can delete the Automation Partition/OEM partition when you distribute your image.  Then you shouldn't have to worry about OEM partitions again in your environment.

I recently experienced the same "out of memory" problems when reimaging a lab of 760s. 

What ianatkin suggested above was true for me.  I had edited a lab image using ImageExplorer to add a directory and then when I tried to deloy that image RDeploy failed continually with the memory allocation error.

Plenty of other 760 labs have imaged fine during our semester break, but for now I would advise staying away from using ImageExplorer to edit images for the 760s.