Windows 2003 recovery error: Failed to allocate index buffer
Hi, i keep getting this: Failed to allocate index buffer
I've tried most combination @ http://kb.acronis.com/content/4000 and even http://forum.acronis.com/forum/10926 which has the same index buffer error, his was due to the amount of ram.
The old server has 1Gb of ram while the new server has 12Gb. The minimum i can put in is 1 x 4Gb. I tried and the same buffer error occured. It's a IBM 3650M3. The image .TIB created from an old Dell server. I tried re-taking the image with only the C Drive and nothing else. Does not work either.
There are:
1 x MBR
1 x FAT16 partition
C Drive
D Drive
in the another image i have. Same error occurs.
please help.

- Log in to post comments

dev-anon wrote:Try to execute a .cmd file like
===
echo off
for /l %%i IN (1,1,50) DO echo foo > foobar%%i
for /l %%i IN (1,1,50) DO del foobar%%i
==
in the root of the c:\ on the old server and then take the image again.
trying it now.
When restoring, there are:
- MBR
- FAT16 1 partition
- C Drive
- D Drive
Can i dont restore the MBR and FAT16 partition? Seems like the FAT16 is the Dell's pre-boot utility that does checks on RAMs etc etc/ Diagnostics.
- Log in to post comments

MBR is not a partition, you need to restore it. Id' restore FAT16 partition too - in case if it fail to boot with the FAT16 partition (due to dell-specific code or something else), just mark the C: partition as 'active' instead of that FAT16 using 'disk management' (disk director lite) feature of bootable media.
- Log in to post comments

dev-anon wrote:MBR is not a partition, you need to restore it. Id' restore FAT16 partition too - in case if it fail to boot with the FAT16 partition (due to dell-specific code or something else), just mark the C: partition as 'active' instead of that FAT16 using 'disk management' (disk director lite) feature of bootable media.
Thank you very much! It worked! However, i did not restore the FAT16 partition, only the MBR, C and D Drive. After running the .bat file you have posted in C Drive on the original server, took a new image, restore and it worked!
- Log in to post comments