Solaris X86 Jumpstart slow

Question

I'm trying to jumpstart a Sun x4240 and during the boot up when it runs the install-discovery script, the server goes very very slow. It will eventually move past this part, but only after many hours. The server has 4 disks, which I have setup on the raid controller as JBOD's, we are not using the RAID functions of the card at all.
It seems the longest time is taken when running the the the script /boot/solaris/bin/create_diskmap, which is mostly this:
/sbin/biosdev 2> /dev/null | while read diskno diskpath
do
devname=`/bin/ls -l /dev/rdsk/*p0 | /bin/grep $diskpath | /bin/nawk '{ print $9 }'`
ctdname=`echo $devname | /bin/sed "s#/dev/rdsk/##" | /bin/sed "s#p0##"`
grubdisk=`echo $diskno | /bin/sed "s/0x8//"`
echo "$grubdisk $ctdname $diskpath" >> "$GRUBDISKMAP"
done
Then once it gets past this part (many hours) it hangs again around this part:
# x86 config cleanup logic
if [ -x /usr/sbin/install.d/atconfig ]; then
     /usr/sbin/install.d/atconfig
fi
Atconfig is described thusly:
Besides ON changes there are changes needed in the
Install consolidation. When you boot the Solaris CD/DVD,
the atconfig binary is run that searches the disk for
kernel/misc/sysinit file and copies this to
/tmp/root/kernel/misc/sysinit so the
svc_serial.c code from Suninstall can try to preserve the
hostid during an upgrade and even an install. We need
to modify this code to also search for /etc/hostid and preserve
it. However, for older systems we also need to search for
kernel/misc/sysinit for those systems that have hostid stored
there, and convert the hostid in sysinit into a hostid in /etc/hostid.
There was no contract between ON and Install for sysinit;
we now have a contract in place between the two consolidations
for Install's use of /kernel/misc/sysinit and /etc/hostid.
The server installs fine during a normal DVD install. I'm not sure what else to do on this. If anyone has any guidance that would be great.

Answer 1

Yes... I've seen and used the grub -b switches for input-device and output-device and this does change the way certain things work. However, this does not redirect input and output solely to the console, as you would, lets say, any sparc box. I start a jumpstat process, tell it to go to the console, and it hangs and waits for input from the VGA device. Right now, I have an odd interaction going on between the ILOM webgui redirection and the console. I can't login through the webgui and reboot the box through the console, nor can I hit CTRL+N to get it to boot off the network when I have the ILOM Webgui redirected to my keyboard. But when it boots off the virtual CD, or if I use the console to get into the BIOS, then and only then can I use my keyboard in the ILOM Webgui.
There is some sort of odd interaction between the console and that stupid VGA port on the ILOM that is not explained in ILOM docs that I have read. And that is what this post is trying to figure out. When you jumpstart a sparc box, you have total control from the console. This is not the case on x86.
Please re-read my other post before you comment on double posting. Both are about x86 jumpstart. One is about console redirection (this post). The other post is asking about getting jumpstart NOT to go through an interactive install through the -b switches. Two separate issues.