I removed the s10u5 SUNWluxxx packages and replaced them by those of
Nevada (someone adviced this).

Here is the screen output from lucreate:

arwen# lucreate -c s10u3 -n s10u5 -m /:c1d0s0:ufs -l /root/lu.log
Discovering physical storage devices
Discovering logical storage devices
Cross referencing storage devices with boot environment configurations
Determining types of file systems supported
Validating file system requests
The device name <c1d0s0> expands to device path </dev/dsk/c1d0s0>
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
Comparing source boot environment <s10u3> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Searching /dev for possible boot environment filesystem devices
Updating system configuration files.
The device </dev/dsk/c1d0s0> is not a root device for any boot
environment; cannot get BE ID. Creating configuration for boot
environment <s10u5>. Source boot environment is <s10u3>.
Creating boot environment <s10u5>.
Checking for GRUB menu on boot environment <s10u5>.
The boot environment <s10u5> does not contain the GRUB menu.
Mounting file systems for boot environment <s10u5>.
Calculating required sizes of file systems for boot environment <s10u5>.
Populating file systems on boot environment <s10u5>.
Checking selection integrity.
Integrity check OK.
Populating contents of mount point </>.
Copying.
Creating shared file system mount points.
Copying root of zone <shire>.
Copying root of zone <midgard>.
Copying root of zone <yanta>.
ERROR: Zone <yanta> in BE <s10u3>: cannot copy root
See </tmp/.lucopy.cpio_err.11533.yanta> for details.
Creating compare databases for boot environment <s10u5>.
Creating compare database for file system </>.
Updating compare databases on boot environment <s10u5>.
Making boot environment <s10u5> bootable.
ERROR: Unable to remount ABE <s10u5>: cannot make ABE bootable
ERROR: no boot environment is mounted on root device </dev/dsk/c1d0s0>
Making the ABE <s10u5> bootable FAILED.
ERROR: Unable to make boot environment <s10u5> bootable.
ERROR: Unable to populate file systems on boot environment <s10u5>.
ERROR: Cannot make file systems for boot environment <s10u5>.
arwen#

I have absolutely no idea why it is not possible to create a boot
environment.
installgrub /boot/grub/stage1 \
/boot/grub/stage2 /dev/rdsk/c1d0s0
works OK.
I know /boot is overwritten creating a new boot env.
Should I perhaps install grub on c1d0s0 and the new ABE on another
slice? It may be a stupid question, but I really have no clue why it's
not working on a (furthermore very stable) S10U3 system.

--
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
++ http://nagual.nl/ | SunOS 10u4 08/07 ++

Dick Hoogendijk wrote:

> arwen# lucreate -c s10u3 -n s10u5 -m /:c1d0s0:ufs -l /root/lu.log

> ERROR: Unable to remount ABE <s10u5>: cannot make ABE bootable
> ERROR: no boot environment is mounted on root device </dev/dsk/c1d0s0>
> Making the ABE <s10u5> bootable FAILED.

try giving the zones their own disk slice(s) in the new BE.

-m /zones:/c1d0s4:ufs

quoting Oscar del Rio (Thu, 08 May 2008 08:20:03 -0400):
> Dick Hoogendijk wrote:
>
>> arwen# lucreate -c s10u3 -n s10u5 -m /:c1d0s0:ufs -l /root/lu.log
>
>> ERROR: Unable to remount ABE <s10u5>: cannot make ABE bootable
>> ERROR: no boot environment is mounted on root device </dev/dsk/c1d0s0>
>> Making the ABE <s10u5> bootable FAILED.
>
> try giving the zones their own disk slice(s) in the new BE.
>
> -m /zones:/c1d0s4:ufs

I will try.
I just ran the -m /:/dev... -m /zones:merged:ufs -n ..
The zone directory was merged alright in the root. But again, the same
error about not being able to make the new ABE bootable.
Here we go for the seperate slices run..
Be back in some time from now ;-)

--
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
++ http://nagual.nl/ | SunOS 10u4 08/07 ++

I wrote:
> -m /zones:/c1d0s4:ufs

oops, extra / there, guess which one

quoting Oscar del Rio (Thu, 08 May 2008 09:41:27 -0400):
> I wrote:
>> -m /zones:/c1d0s4:ufs
>
> oops, extra / there, guess which one

I had changed it in an acceptable form ;-)
But meanwhile, giving (/) root and /zones their own slice did not help.
The end is still the same. The ABE cannot be made bootable. And I have
NO idea why that is, because the normal installgrub line works OK.

I'm near giving up on LU, but it is such a tempting program (if it
works).
And why should it not work on a solid working s10u3 machine with
three zones? What could be the cause? Where do I need to look? I really
don't mind trying, but my options are blank right now.

Anybody out there any ideas about this.
Help much appreciated.

--
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
++ http://nagual.nl/ | SunOS 10u4 08/07 ++

quoting Dick Hoogendijk (Thu, 08 May 2008 17:23:44 +0200):
> I had changed it in an acceptable form ;-) But meanwhile, giving (/)
> root and /zones their own slice did not help. The end is still the
> same. The ABE cannot be made bootable. And I have NO idea why that is,
> because the normal installgrub line works OK.

I just checked the slices. All files seem to have been copied OK.
The /etc/lu directory is OK and the /etc/vfstab too.
If ONLY this ABE would be made bootable.
Why is this not happening?

--
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
++ http://nagual.nl/ | SunOS 10u4 08/07 ++

Dick Hoogendijk wrote:
> quoting Dick Hoogendijk (Thu, 08 May 2008 17:23:44 +0200):
>> I had changed it in an acceptable form ;-) But meanwhile, giving (/)
>> root and /zones their own slice did not help. The end is still the
>> same. The ABE cannot be made bootable. And I have NO idea why that is,
>> because the normal installgrub line works OK.
>
> I just checked the slices. All files seem to have been copied OK.
> The /etc/lu directory is OK and the /etc/vfstab too.
> If ONLY this ABE would be made bootable.
> Why is this not happening?
>

it seems to be failing during a remount.
maybe related to
http://bugs.opensolaris.org/bugdatab...bug_id=6629088

I wrote:
> Dick Hoogendijk wrote:
>> quoting Dick Hoogendijk (Thu, 08 May 2008 17:23:44 +0200):
>>> I had changed it in an acceptable form ;-) But meanwhile, giving (/)
>>> root and /zones their own slice did not help. The end is still the
>>> same. The ABE cannot be made bootable. And I have NO idea why that is,
>>> because the normal installgrub line works OK.
>>
>> I just checked the slices. All files seem to have been copied OK.
>> The /etc/lu directory is OK and the /etc/vfstab too.
>> If ONLY this ABE would be made bootable.
>> Why is this not happening?
>>
>
> it seems to be failing during a remount.
> maybe related to
> http://bugs.opensolaris.org/bugdatab...bug_id=6629088

the error seems to be coming from the script /usr/lib/lu/lumkboot

# Create the local database on the new BE and populate it with the
# synchronization checkpoint initial values specified in the
# synclist file.
$LUBIN/luumount -f -i $ICF &&
LU_ALT="`LU_OUTPUT_FORMAT=text $LUBIN/lumount -i $ICF 2>${TMP_RESULT_FILE}`"
if [ $? -ne 0 ]; then
$LUPRINTF -Eelp2 \
"`gettext 'Unable to remount ABE <%s>: cannot make ABE bootable'" \
$BE_NAME
exit_script 1
fi


try inserting

cat "${TMP_RESULT_FILE}"

before exit_script, it might tell you where it's failing