Posts made by subtitling

Ubuntu 12.04 LTS with FOG 0.32 on DL360e Gen8, no RAID, legacy SATA support.

When we [COLOR=black]created [/COLOR]a task to [COLOR=black]install [/COLOR]an [COLOR=black]image [/COLOR]on to a new HP Proliant DL360e Gen8 Server, we found it failed to [COLOR=black]install[/COLOR]. If we booted from a GParted live disk and [COLOR=black]created [/COLOR]a (MSDOS) [COLOR=black]partition [/COLOR][COLOR=black]table[/COLOR], then started FOG again, the [COLOR=black]image [/COLOR]installed OK.

Is there away for FOG to do this to avoid having to boot from a GParted Live disk first?

Many thanks.

We continue to face hurdles, but 12.04 with FOG 0.32, grub (not grub2) seem to work with DL360e Gen8, although we now have to figure out how to avoid eth0 disappearing after cloning.

Interestingly, we tried to use our setup to image a VM and we get the same error as the OP.

Due to time constraints, we are going to retrograde to 0.32 (on another server hosting[COLOR=black]FOG[/COLOR]), but format the node to be cloned with Ext3… and hope that works OK!

Nevertheless, thank you for your effort in this.

Sorry, I missed your signature, but I just tried now but sadly I still have the issue. Thanks for your effort; however, I’m going to have to call it a night now.

Cheers.

PS - We didn’t get the issue with 0.32, but sadly it doesn’t support ext4.

Further, I put all the original files (inits and bz files) back from the default installation then ran:
wget -O bzImage --no-check-certificate [url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]

…but I still get the panic.

For good measure I ran this as well:
wget -O bzImage32 --no-check-certificate [url]https://mastacontrola.com/fogboot/kernel/bzImage32[/url]

Would you point me to what you mean by the FAQ on kernels, I am unsure what you mean?

Thanks

Sadly, ipxe.kpxe or ipxe.kkpxe haven’t fixed the issue, so I’m relying on my ‘pause’ method for the moment. Using ipxe.kkpxe renamed to undionly.kpxe caused a red screen of death with an illegal upload message.

Sorry, ignore the previous ‘mirror’ comment, that was where I failed to delete the text after double checking the server config.

Thanks.

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

Just an update to explain that this hasn’t fixed the issue, and I still have the same error. This wasn’t an issue with 0.32 and the same hardware.

Thanks.

Here’s a screen shot. Thanks.

[url=“/_imported_xf_attachments/0/769_photo.JPG?:”]photo.JPG[/url]

Ubuntu 14.02/FOG 1.0.1 server, registering a HP DL360 Gen8 with Ubuntu 10.??. After discovering a workaround that enabled me to get to the FOG PXE menu, I now have another issue.

If I try to do a compatibility test, or a [COLOR=black]quick [/COLOR][COLOR=black]registration[/COLOR], I get a [COLOR=black]kernel [/COLOR][COLOR=black]panic[/COLOR]. Guidance would be appreciated.

The [COLOR=black]kernel [/COLOR][COLOR=black]panic [/COLOR]states: [B][COLOR=black]Kernel[/COLOR][COLOR=black] panic [/COLOR]- Not [COLOR=black]syncing[/COLOR]: Attempted to kill init! exitcode=0x00000009[/B]

[B][COLOR=black]Kernel[/COLOR] Offset: 0x0 from 0xffffffff81000000 (relocate range: 0xffffffff800000000-0xffffffff9fffffff)[/B]

Thanks for posting Tom.

Thanks for that, but we are using the FOG server as the DHCP, but this isn’t our problem; if I pause the screen for a moment, it all works OK.

Yes, this is so frustrating. 0.32 was easy, but this has cost me many hours now, and I only found it by chance. I tried to pause the screen to see the error, and when I escaped I saw the PXE menu.

I think I’m going to have to use an alternative solution, my Linux skills are clearly not up to scratch. Life is too short.

Installed the latest FOG 1.0.1 on Ubuntu 14.02 LTS using all the defaults advised. When we PXE boot to inventory a computer, we get an error: [B]Could[/B][B] not start download: Operation not [/B][B]supported[/B]

If I pause at the point where it shows:[B] iPXE 1.0.0+(d28b) – Open Source Network Boot Firmware – Features: NFS HTTP HTTPS iSCSI DNS TFTP AoE bzImage ELF NBOOT PXE PXEXT Menu Configuring (net0 [I]my MAC address[/I])… [/B]then escape; I see the ‘FOG PXE menu’ as expected…

This implies a timing issue. We have experienced this on several platforms, and despite not seeing anyone on here complaining of this, wonder if there might be a bug, or a TFTP setting that needs to be changed?

Any help appreciated as this has caused as a considerable amount of wasted time. We didn’t have this problem on previous versions of FOG. Those version worked ‘out of the box’ with minimal changes.

Many thanks in advance.