Please pardon me if I am not in an appropriate location to discuss this...I can't seem to find a better place.
I'm having an awful time configuring jumpstart and am looking for tips to troubleshoot what's happening. Basically I have a blade chassis with 3 AMD based blades and 3 Xeon based blades. For the purposes of building the Jumpstart Server I have created a private virtual LAN within the blade chassis...no routes, no external connectivity. I have one AMD blade setup with Solaris 10 U6 to run as the jumpstart server - I have followed the notes at http://www.sun.com/bigadmin/features/articles/jumpstart_x86_x64.jsp to help me along... I have run the setup_install_server script, created the jumpstart rules, profile, sysidcfg, begin and finish script (I even have a custom probe, and have rebuilt the mini_root to have the disk array driver for my blades). I have configured the DHCP server. I have two install sysidcfg files each in their own directory - practically exactly following the Big Admin article. I PXE boot a blade, TFTP sends grub down to the blade, grub matches the MAC address and loads the correct menu, and the dots start going across the screen. The U6 kernel starts to load, all looks good until I end up with the same prompt I get when booting off the DVD - Interactive Default, Desktop Text, Serial Console, Add Driver, etc. I have tried adding -v to the kernel for verbose kernel messages and in when done I can see the Array driver being loaded, then get prompted as described above. I'm at a real loss as to where to look next. My sysidcfg are pretty straight forward (like I've used before in other places with pre-existing jumpstart servers), the rules and custom_probes files verify just fine. Might anyone have a suggestion? -- This message posted from opensolaris.org
