|
|
Question : Using a ghost image with Perc5i drivers to drop onto na identical server but with Perc6i raid controller ?
|
|
I've recently purchased a new server from Dell, to add into our current farm of terminal servers.
As the title says the new server now has a Perc6i raid controller instead of Perc5i after imaging the server using Bart PE \ ghost. The server will not boot. I realize this is due to the raid controller drivers not in the image, but what I can't figure out is how to add them ?
I've tried using the windows repair option and pressing F6 and loading the drivers but this works half way and then asks to load the Perc 6i drivers again and when I press enter it doesn't do anything ?
Can I manually add these drivers in recovery mode ? And can you shed any light on why using the repair option didn't work ?
Thanks.
|
Answer : Using a ghost image with Perc5i drivers to drop onto na identical server but with Perc6i raid controller ?
|
|
Traditionally we would do this same thing on HP servers and I can imagine the process would be the same for Dell as it is a Windows issue. We would do this procedure when we would move a set of disks to a server with a different controller.
What you need to do is before you create your image of your existing systems with the Perc5i controller is to add the perc6i drivers to the system. To do this, you just install the Perc6i drivers on the system (your image placed on a system with a 5i) even though it doesn't have a 6i installed. Image the system. When you put the image onto the new machine, the drivers should already be present and the OS should be able to detect them properly and boot into windows.
|
|
|
|