@george1421 Hi George,

The issue was fixed, need to test it on more machines to make sure it’s a global a fix, but after isolating the boot drive using debug mode it appears to be deploying to the correct drive. I used /dev/sda2 as my host primary disk.

I’ve attached a photo of the drives available to the fog.

I’ll! keep you updated on this and thanks !

Bill.


@george1421 Thanks for getting back to me! Yes you are right our company machines when built do use Intel RST to create the raid 0.

The information you gave me has been really helpful and I feel like I’ve made some progress. (Raid no longer destroys its self when an image is deployed) Which is good because they’re a pain to fix.

however, the fog server still deploys to the raid (D:) rather than the boot drive (C:) if I add /dev/md126 as the primary drive on the host, the image successfully deploys avoiding the raid with no errors, but when the computer reboots it doesn’t actually appear to have done anything. There are no oobe prompts and the desktop remains the same as it did before the deployment.

I watched the entire process and it deployed exactly as it normally does and didn’t display any errors.

If you have any ideas that’d be great ! Either way thanks for all the information regardless.

kind regards,

Bill.

Rather than deploy the image to the drive with windows stored upon it, it appears to randomly select a drive to deploy to.

I’m running machines with a standalone boot drive (C:) coupled with a tri SSD raid 0 setup (D:).

So every time I use the FOG Server it breaks the Raid 0 by deploying the image to one of the SSD’s within the raid. It never used to do this so I’m sure it’s just a setting that I’m missing as I have recently updated the FOG’s firmware.

I was under the impression the FOG server could distinguish between which drive contained windows when deploying an image as I’m sure it used to function in this manner.

Kind regards,

Bill.