Glad my efforts helped someone. 
Unfortunately, the lack of Firmware RAID support was a show stopper for us and I was forced to box my FOG servers and go with Acronis Snap Deploy. 
I really like what FOG has to offer and I hope that someone will figure out this Firmware Raid issue so that we can go back to FOG in the future. 
At the risk of being accused of Thread Necromancy, I wanted to check in on these issues.
Seems that the OP & my initial issue was indeed caused by the Quadro in my case. Since my last post, I have researched Linux kernel-making, and have cooked up a kernel that now boots fine with the Quadro in the machine. Unfortunately, I am still unable to have FOG see the built-in Intel RAID controller properly (Firmware-RAID), and just canāt figure out how to get the kernel to see the RAID container instead of the individual disksā¦ I see many posts about this issue with no solutions, and would very much like to get a solution.
I can confirm that this doesnāt work on Windows 7 as written. Since Iām unfamiliar with the unix tools, I just destroyed my reference workstation. I managed to work with the 100Mb Win7 boot partition, but destroyed the partition containing the driveā¦ lol
Yes; the image was built on a RAID. Tried the steps from the link you provided and the link that page referenced, but as far as DISKPART goes, it thinks the DISK has no partitions so none of that works.
Looks like we now have a problem with the RAID. The workstations are using the MOBO built in raid controller to have the 2 HDs in RAID0 to increase performance. The 0.29 kernel didnāt see anything and just crashed, so I switched back to the old kernel and got an image. Unfortunatley, dropping the image back boots to a āNon system diskā errorā¦
OK, I swapped out the Quadro 2000 and tossed in a Geforce 9800GTX+ and PXE boots past the initial FOG menu. It complaines that the BIOS for the Z400 is unknown, but appears to function as expected. Iām going to pull an image now and see how it goes.
OK, I swapped out the Quadro 2000 and tossed in a Geforce 9800GTX+ and PXE boots past the initial FOG menu. It complaines that the BIOS for the Z400 is unknown, but appears to function as expected. Iām going to pull an image now and see how it goes.
And just to make sure I did everything right (since Unix is not my primary language):
/tftpboot/fog/images$ ls -l
total 36628
-rw-rār-- 1 fog root 30971987 2010-05-11 08:25 init.gz
-rw-rār-- 1 fog root 6530155 2011-11-30 16:12 init.gz.BACKUP
OK; I get the same message with the init.gz from the 0.29 package.
OK; so what boot image was used in 0.29?
I tried a couple of them, but I was afraid of breaking what is working. 3.1-rc8 Core was the last one I tried. I saw that FOC0.29 worked with the Z400s but I donāt know if thatās relevant since HP uses the same model number (Z400) for workstations spanning years. The Z400 on my bench is not the same Z400 that was available when 0.29 was released. Also, how does one tell which PXE Boot Image was deployed with which version of FOG?
Sorry if my questions seem simple; Iām not fluent in Unix.
The new shipment of HP Z400 workstations we recieved came with MAC addresses starting with 2c:41:38 which [url]http://standards.ieee.org/develop/regauth/oui/oui.txt[/url] shows as belonging to Hewlett-Packard Company but FOG lists them as Unknown.
So weāve been using FOG on our HP XW4400 workstaions quite successfully. Now we have gotten a shipment of new HP z400 workstations, and despite the Z400 being on the happy list with FOG, we are getting the kernel_thread_helper+0x6/0x10 message when trying to boot past the FOG menu via PXE. We tried changing kernels and manually adding the machine to the FOG host list to set the acpi=off parameter to no avail.
On the XW4400s, while watching the boot process it seems thereās a display change from 800X600 in the FOG menu to something much higher when it goes to do the imaging or inventory so Iām wondering if that is related. The old workstations have a mix of Geforce based cards and the Z400s are all Quadro 2000s. Any ideas?