Hi again.
Thanks for the reply. Unfortunately that hasn’t fixed my issue. In the steps below, you will see that I have tried kernel from v0.32.
To recap a bit, in my previous posts, I was asking about issues with regards to the new FOG iPXE timeout and Kernel Panic issues. To put it all in perspective:
- The iPxe timeout stopped me from seeing the FOG menu
- And the Kernel Panic was caused by a bzImage or (bzImage32) failing to be loaded onto my FOG client
My FOG server is:
- HP Tower DC7100, Ubuntu Desktop 14.04 LTS, FOG 1.0.1
Image to deploy:
- image name: Linux-testimg1, 40GB ( with 3 partitions 1GB for /boot (/dev/sda1), 2GB for /swap (/dev/sda2), and the rest for root / (/dev/sda3) )
- image OS: Linux OS, Ubuntu Server 12.04.1 LTS, 32-bit
- image FS: ext4fs
My Fog client is (This is the one that I am desperately trying to deploy the image to):
- HP DL360e Proliant - SATA (non-RAID), two 500GB HDDs.
In the following steps, I used workarounds to circumvent all these issues, but I still have problems (I have captured a short video (2min:19) [media=youtube]xnUX74Dlhno[/media]
As per my other thread that I had started:
1/ To boot the client onto Fog server’s iPXE, I press F12 (Network boot) (see video at about 00:34sec).
Then iPXE goes on and to circumvent the timeout issue, I press PAUSE|BREAK on my keyboard (see video at about 00:52sec).
I wait for about 4sec after the PAUSE|BREAK keypress then press ESC
2/ bzImage and init.xz then get loaded … ok
NOTE:
- I had to overwrite fog 1.0.1’s bzImage with fog 0.32’s bzImage
- I had to rename fog 0.32’s init.gz to init.xz then overwrite fog 1.0.1’s init.xz
Without these 2 hacks, step 2 caused a Kernel Panic crash when the original fog 1.0.1’s bzImage and init.xz were loaded on my Fog HP Proliant client. The 0.32’s bzImage and init files do not cause it to crash.
3/ Fog 0.32 boots up and tries to deploy my Linux-testimg1, but it unfortunately fails (see video)
Thanks for any help,
Subtitling