1 of 1 people found this helpful
if you're not doing any pre-install scripts, you should be able to boot to winpe, have bmi auto-register the system, then provision linux onto the system and choose the boot image of 'skip linux pre-install'. this will avoid gentoo all together.
That sounds like something I'd like to try. I've followed you all the way to "choose the boot image of 'skip linux pre-install'. When I select "Provision" and then my System Package, it automatically fills in the "Select Boot Image" drop down with gentoo32.
I tried creating a new boot image that was blank, which ended badly. I then gave it generic boot images to work with which also ended badly.
How, exactly, do I deal with the "Associated Boot Image" section? I appreciate your input.
1 of 1 people found this helpful
There's a hotfix for 7.6 that enables the 'skip linux pre-install' as a boot image type. there's a sql script you run in addition to applying the hotfix. Open a ticket w/ support and they can get you the latest hotfix for 7.6.
I'd like to pick this thread back up with the idea that patching is impossible (for now). We've run into issues with patch 224 and would very much like to stay at 115 for the time being.
I've cleared the problem mentioned above in this thread by downgrading the version of the Gentoo Minimalist ISO to a 2007 version that uses SquashFS 3.0. The "mkgen2img.sh" script executes cleanly without modifications now.
During the boot process with the newly generated boot images, it passes the previous error spot and lands into a "Welcome to BMC BLadelogic Provisioning" screen. It appears to fiddle around with eth0 for a bit and sends some DHCPINFORM and DCHPDISCOVER packets.
The target device and boot process then hangs on the DHCPACK responses.
Has anyone seen this behavior before or have an idea on where to begin troubleshooting? Quick looks at my DHCP log, PXE log and TFTP log did not reveal any obvious errors. As always, all input is greatly appreciated.
There's a 228 hotfix that resolves the issue introduced w/ 224. There's also hotfixes for bmi, (the provision files), that you might want to use to regenerate the image. i've seen the 1st error, that is usually ok, not sure about the 2nd. setup snoop and see if traffic is going to the right places. you've got the dhcp options setup right?
I generated this boot image with the 223 revision provisioning files.
This environment will provision a Windows machine just fine, so I'm assuming my DHCP scope options are also fine for Linux provisioning.
211 = <Application Server IP>
212 = 0x2667 (9831 in hex)
60 = PXEClient
(This thread is not "Answered"...I hit the wrong button when trying to reply and now I can't "un-Answered" it.)
maybe gentoo doesn't like the nic? can you ctrl-c out when you get those dhcpdiscover messages and do a 'ifconfig -a' and some other network troubleshooting to see that it's on the network, can talk, etc?
ifconfig -a reveals that the target device has been assigned the proper IP from the DHCP server. (Address pool: 192.168.248.200 - .224)
IP = 192.168.248.200
BCAST = 192.168.248.255
Mask = 255.255.255.0
PXE Server = 192.168.248.131 (255.255.255.0)
APP Server = 192.168.248.128 (255.255.255.0)
I can ping FROM the target device TO the PXE server and vice versa when I CTRL-C at dhcpdiscover messages. I'm still working on getting snoop up and running, but I'm not seeing anything wrong with the network. Both devices are on the same VM network, etc.
Link to snoop?
tcpdump should be in the gentoo image.