Not able to create Live Upgrade BE - from scratch Post: 302414346

Sponsored Content

Operating Systems Solaris Not able to create Live Upgrade BE - from scratch Post 302414346 by incredible on Tuesday 20th of April 2010 12:48:08 AM

04-20-2010

Registered User

Not able to create Live Upgrade BE - from scratch

I have d0 as root and d4 as /var
d3 and d5 are /lu-root and /u-var respectively
Doing this on a M-series

Code:

bash-3.00# lucreate -m /:/dev/md/dsk/d3:ufs -m /var:/dev/md/dsk/d5:ufs -c Active -n Passive
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
ERROR: the file system on device </dev/md/dsk/d3> is currently mounted at </lu-root>
ERROR: device </dev/md/dsk/d3> is not available for use with mount point </>
ERROR: cannot create new boot environment using file systems as configured
ERROR: please review all file system configuration options
ERROR: cannot create new boot environment using options provided
 
bash-3.00# df -k | grep lu
/dev/md/dsk/d3****** 36149036** 35865 35751681**** 1%*** /lu-root
/dev/md/dsk/d5****** 20655025** 20505 20427970**** 1%*** /lu-var
 
bash-3.00# umount /lu-root****************************************************************************************************************************************************** << Tried unmounting the disk so as to pass the above criteria
bash-3.00# umount /lu-var
 
bash-3.00# lucreate -m /:/dev/md/dsk/d3:ufs -m /var:/dev/md/dsk/d5:ufs -c Active -n Passive
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
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
No name for current boot environment.
Current boot environment is named <Active>.
Creating initial configuration for primary boot environment <Active>.
WARNING: The device </dev/md/dsk/d0> for the root file system mount point </> is not a physical device.
WARNING: The system boot prom identifies the physical device </dev/dsk/c1t5000C5001CE82C0Bd0s0> as the system boot device.
Is the physical device </dev/dsk/c1t5000C5001CE82C0Bd0s0> the boot device for the logical device </dev/md/dsk/d0>? (yes or no) yes
INFORMATION: Assuming the boot device </dev/dsk/c1t5000C5001CE82C0Bd0s0> obtained from the system boot prom is the physical boot device for logical device </dev/md/dsk/d0>.
The device </dev/dsk/c1t5000C5001CE82C0Bd0s0> is not a root device for any boot environment; cannot get BE ID.
PBE configuration successful: PBE name <Active> PBE Boot Device </dev/dsk/c1t5000C5001CE82C0Bd0s0>.
Comparing source boot environment <Active> 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.
ERROR: The following required file systems are not mounted by the currently running OS </lu-var /lu-root>** << Fail again, this time as we unmounted the filesystem above…Is this proper?
ERROR: All required PBE file systems are not mounted.

incredible

View Public Profile for incredible

Find all posts by incredible

8 More Discussions You Might Find Interesting

1. Solaris

Live upgrade Issue

Hi, I upgraded solaris 10 x86 from update 3 to update 7 with zones installed n UFS file system . The global zone was updated but the non global zone still shows update 3 what could be the reason for this and how can i update the local zones to update 7

2. Solaris

Live upgrade question

I want to basically update an ABE that someone created a few months back. I'm sure stuff has changed since it was made, and I was going to delete it and create a new one. But from what I'm looking at, the lumake appears like it would be a faster approach. I want to use live upgrade to...

3. Solaris

Live Upgrade Issue

I tried a live upgrade for one my solaris 10u8 server which didnt go sucessfull and after that i now have following mounts in memory. df: cannot statvfs /.alt.sol10u8_2/var: No such file or directory df: cannot statvfs /.alt.sol10u8_2/var/run: No such file or directory df: cannot statvfs...

4. Emergency UNIX and Linux Support

Live Upgrade Query

I am upgrading Solaris-9 Update-7 to Solaris-9 Update-9 through live upgrade. I am able to create another boot environment and have OS DVD inside server. But i am confused for, what command/path should I give for luupgrade. OS DVD is mounted on /mnt Boot environments are Solaris9old (Active now)...

5. Solaris

Live upgrade query

Hi All, Is it possible to use external san disk for creating alternate boot environment and boot from it.My root disk is about 70 gb and i want to use external san disk for 272gb to create alternate boot environment.If this is possible can you please redirect me some good documents, i had...

6. Solaris

Problem in SVM after live upgrade

Hi I am new to live upgrade. I would like to tell you about my new setup, where my boot disk(c0d0) is mirrored with secondary disk(c0d1). I have remove the secondary whole disk(C0d1) from the mirror, so that I can do live upgrade on this secondary disk. I have done live upgrade on s0 partition...

7. Solaris

Live upgrade first steps

Hello Guys, I am a little confused about the first step in the live upgrade process. I will be glad if someone can clarify this for me. The pre-live upgrade patch, when do you add this patch to the OS you want to upgrade? 1. before creating the new boot environment? or 2. after creating...

8. Solaris

Patching using live upgrade - with non-globalzone

Hi all, I would like to ask what will be the best practice for the following setup / - c0t0d0s0 - current BE (named First) / - c0t0d1s0 - alternate BE (name Second) i have a non-global zone with zonepath in /zones/myzone /mnt/opt - c0t0d2s6 (shared between the 2 BE)...

LEARN ABOUT DEBIAN

pmvarrun

pmvarrun(8) pam_mount pmvarrun(8)

Name
pmvarrun - updates /var/run/pam_mount/user

Syntax
pmvarrun -u user [options]

Description
A separate program is needed so that /var/run/pam_mount/user may be created with a pam_mount-specific security context (otherwise SELinux
policy will conflict with gdm, which also creates file in /var/run).

pmvarrun is flexible and can run in a number of different security setups:

root-root
When pmvarrun is invoked as root, /var/run/pam_mount's permission settings can be as strict as needed; usually (0755,root,root) is a good
pick as it gives users the debug control over their refcount. Refcount files are given their respective owners (chowned to the user who
logs in).

user-user
When invoked as the user who logs in, /var/run/pam_mount needs appropriate permissions to create a file, which means the write bit must be
set. It is also highly suggested to set the sticky bit in this case, so other users do not tamper with your refcount.

root-user
Some programs or login helpers incorrectly call the PAM stack in a way that the login phase is done as root and the logout phase as a nor-
mal user. Nevertheless, pmvarrun supports this, and the same permissions as in root-root can be used. While the user may not be able to
unlink his file from /var/run/pam_mount, it will be truncated to indicate the same state.

Options
--help, -h
Display help.

--user user, -u user
User to handle, must be a valid username.

--operation number, -o number
Increase volume count by number.

-d Turn on debugging.

Files
/var/run/pam_mount/user

Author
This manpage was originally written by Bastian Kleineidam <calvin@debian.org> for the Debian distribution of libpam-mount but may be used
by others.

See /usr/share/doc/packages/libpam-mount/copyright for the list of original authors of pam_mount.

pam_mount 2008-10-08 pmvarrun(8)