Problem booting a Solaris 10 x86 after Jumpstart Installation

Question

Hi,
I have a strange problem. I have a working x86 machine with Solaris 10 installed. I have made a flash image of it's hard disk, and I have store thar flar on another machine. I have another Solaris 10 with Jumpstart.
I boot other x86 machine through PXE. The Jumpstart machine gives it a valid IP, and the process of sending the flash image begins. The process finish, and the client machine reboots. And here is the strange problem:
When starting, the Grub men� appears, and shows the two options configured: first, start Solaris in normal mode, and second, failsafe.
If I choose normal start, the screen goes black and the machine restart as if you rebooted it. I can only start in failsafe mode.
Here are the config files in Jumpstart for that machine:
Profile:
install_type flash_install
archive_location nfs 10.95.8.7:/export/backup/platform/alba-ucm/ALBA-UCM-HostID_2b72c461_4x80GbMirror-Prepared_09042008.flar
partitioning explicit
filesys c0t0d0s0 1:2650 /
filesys c0t0d0s1 2651:1600 /var
filesys c0t0d0s3 4251:400 swap
filesys c0t0d0s4 4651:1000 /opt/app
filesys c0t0d0s5 5651:3143 /repositoryCC
filesys c0t0d0s6 8794:100 /tmp
filesys c0t0d0s7 8894:26
filesys c0t2d0s0 1:8093 /datos
filesys c0t2d0s1 8094:800 /DBoracle
filesys c0t2d0s7 8894:26
After Script:
touch /a/etc/notrouter
touch /a/noautoshutdown
sync
echo "Changing and syncing bootenv.rc"
# clear the boot-args property
echo "setprop boot-args ''" >> /a/boot/solaris/bootenv.rc
# set the bootpath property to boot from the hard disk
STRING=`df | grep '^/a '� | sed 's/).*//' | sed 's/^.* (//'`
STRING=`ls -l ${STRING}`
MYROOT=`echo $STRING | sed 's/.*..\/..\/devices//'`
echo "setprop bootpath ${MYROOT}" >> /a/boot/solaris/bootenv.rc
# disable kdmconfig from running after the first reboot
sysidconfig -b /a -r /usr/openwin/bin/kdmconfig
sync
And here is the menu.lst for Grub:
title Solaris 10
root (hd0,0,a)
kernel /platform/i86pc/multiboot
module /platform/i86pc/boot_archive
title Solaris Failsafe
kernel /boot/multiboot kernel/unix -s
module /boot/x86.miniroot-safe
Please, any idea about what may be hapening?

Answer 1

Thanks for your answers.
Yes, both machines have the same hardware exactly. Finally, I could find where the problem was.
The file bootenv.rc, for some reason that I don't know, was corrupted: In it there was a correct line with bootpath variable correctly defined, but, at the end of the file, there was another line setting the bootpath variable to a long and incoherent string of chars. Booting in failsafe, mounting the system in /a, and removing that stupid line from the bootenv.rc, solved the problem.