Dick: You should install the s10u5 packages back. Also need to install the following p7zip and cpio patch and try again:
For Solaris 10 5/08, the compression of the install images is now unzipped with the 7zip utility. In order for live upgrade to work with Solaris 10 5/08, the f ollowing patches needs to be applied: Solaris 10 sparc - 137321-01 or later Solaris 10 x86 - 137322-01 or later Solaris 9 sparc - 137477-01 or later Solaris 9 x86 - 137478-01 or later Cpio patches for live upgrade with zones: Solaris 10 sparc - 127922-03 or later Solaris 10 x86 - 127923-03 or later Dick Hoogendijk wrote: > 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. >
