L
Luke Alcatel
I know the issue has been discussed before but it seems the cause was either
images too large for the amount of RAM or some other configuration error.
I have been using RBS and SDI ramdisk images for quite a while but it is
only recently that we have been testing on production hardware in large
scale. The image is about 90K, I set my ramdisk to be 150K to allow for a
small swap file (needed for performance monitoring) and for temp files. We
have 1GB of RAM. With the same image on the same machines, sometimes the
image loads fine and other times we get:
Windows could not start due to an error while booting from a RAMDISK.
Windows failed to open the RAMDISK image.
The hardware is high-end compact PCI Pentium-M blades. The network is
gigabit but the performance of the RBS has always appeared woeful and I
never see the link utilization above 5%. Given that the remote boot
sometimes works and sometimes doesn't I think I should be thinking about
hardware but I wanted to check with the community before confronting the
hardware vendor.
Luke
images too large for the amount of RAM or some other configuration error.
I have been using RBS and SDI ramdisk images for quite a while but it is
only recently that we have been testing on production hardware in large
scale. The image is about 90K, I set my ramdisk to be 150K to allow for a
small swap file (needed for performance monitoring) and for temp files. We
have 1GB of RAM. With the same image on the same machines, sometimes the
image loads fine and other times we get:
Windows could not start due to an error while booting from a RAMDISK.
Windows failed to open the RAMDISK image.
The hardware is high-end compact PCI Pentium-M blades. The network is
gigabit but the performance of the RBS has always appeared woeful and I
never see the link utilization above 5%. Given that the remote boot
sometimes works and sometimes doesn't I think I should be thinking about
hardware but I wanted to check with the community before confronting the
hardware vendor.
Luke