> the installer seems to call the following fdisk > command a couple of times for each disk. > > /sbin/fdisk -n -R -v -W - /dev/rdsk/c2d1p0 > > When I run that I get: > * Id Act Bhead Bsect Bcyl Ehead Esect Ecyl > Rsect Numsect > 238 0 254 63 1023 254 63 > 1023 1 409639 > 175 0 254 63 1023 254 63 > 1023 409640 134217728 > 191 0 254 63 1023 254 63 > 1023 134889512 21411936 > This looks sensible. First partition is EFI, second is OSX > partition, third is Solaris2 that I created with > bootcamp and fdisk - id is 191.
I'd also double check what "prtvtoc" reports for your EFI labled disk. AFAIK, as soon as the disk has a valid EFI label, the partitions defined in the EFI label are used for the "c?t?d?s?" slices, and an fdisk partition tagged with 0xBF is more or less ignored. OTOH, there used to be a problem that Solaris x86 didn't know about the UUID tag used for the MacOS X EFI partition and was (still is?) presenting the space used by MacOS X HFS+ as free space; see bug 6374985 (which is closed a a duplicate, but what is the original bug, and is that original bug fixed?) This message posted from opensolaris.org
