Hi Lukasz,
Lukasz Celeban wrote: > Hi, > > I performed additional test to reproduce this behavior. > So, when I had configuration as following: > Device Boot Start End Blocks Id System > /dev/hda1 * 1 5610 45062293+ 7 HPFS/NTFS > > /dev/hda2 7013 9443 19527007+ 83 Linux > > /dev/hda3 5611 7012 11261565 82 Linux swap / Solaris > > /dev/hda4 9444 9728 2289262+ 82 Linux swap / Solaris > > > gui-install choose correct partition and all installation process seems to be > successful, but after restart I see only 'grub>' prompt, like in: > http://www.opensolaris.org/os/project/indiana/resources/rn3/ (# 6690824) Indeed - you are hitting 6690824. > > After this first installation the partitions configuration looks as following > (my usb stick corrupt dump from fdisk and I recreate it from memory): > Device Boot Start End Blocks Id System > /dev/hda1 1 5610 45062293+ 7 HPFS/NTFS > > /dev/hda2 7013 9443 19527007+ 83 Linux > > /dev/hda3 * 5611 7012 11261565 82 Linux swap / Solaris > > /dev/hda4 * 9444 9728 2289262+ 82 Linux swap / Solaris > > > So I tried install again and then hda4 is used as target partition instead of > hda3 - hda3 was selected as target in gui. > Its looks like this 'boot' flag is somehow important for gui-install ;) > (Notice that hda3 is second partition on disk.) The problem in this case is that you have actually more than one Solaris/Linux swap partition marked as 'active'. If you have more than one Solaris primary partition at the same disk, kernel prefers the one marked as 'active'. If there are more than one active Solaris partitions, kernel picks up the last one found, which is /dev/hda4 in your case. According to the 3rd workaround for 6690824 mentioned in release notes, if you mark only /dev/hda3 as active before you invoke installer, you should be able to successfully install into that partition. Jan
