Live Upgrade Patching Error: Unable to write vtoc Post: 302724289

Sponsored Content

Operating Systems Solaris Live Upgrade Patching Error: Unable to write vtoc Post 302724289 by Siralos on Wednesday 31st of October 2012 05:10:00 PM

10-31-2012

Registered User

Live Upgrade Patching Error: Unable to write vtoc

Attempting to patch several servers using live upgrade

Release: Oracle Solaris 10 8/11 s10x_u10wos_17b X86

Error I'm receiving is in the message in the log below

Code:

tail -15 /var/svc/log/rc6.log
Legacy init script "/etc/rc0.d/K50pppd" exited with return code 0.
Executing legacy init script "/etc/rc0.d/K52llc2".
Legacy init script "/etc/rc0.d/K52llc2" exited with return code 0.
Executing legacy init script "/etc/rc0.d/K62lu".
Live Upgrade: Deactivating current boot environment <sol10_U10x86>.
Live Upgrade: Executing Stop procedures for boot environment <sol10_U10x86>.
Live Upgrade: Current boot environment is <sol10_U10x86>.
Live Upgrade: New boot environment will be <patched_05102012>.
Live Upgrade: Activating boot environment <patched_05102012>.
ERROR: Live Upgrade: Unable to write the vtoc for boot environment
<patched_05102012> to device </dev/rdsk/c0t5000C50039FEF187d0s2>.
Partition 0 not aligned on cylinder boundary: "0 2 00 20352 286657920"
ERROR: Live Upgrade: Activation of boot environment <patched_05102012> FAILED.
Legacy init script "/etc/rc0.d/K62lu" exited with return code 0.

---------- Post updated at 04:10 PM ---------- Previous update was at 12:00 PM ----------

very big difference in the root size between the current BE and patched BE

Code:

# lufslist sol10_U10_101512
               boot environment name: sol10_U10_101512

Filesystem              fstype    device size Mounted on          Mount Options
----------------------- -------- ------------ ------------------- --------------
/dev/zvol/dsk/rpool/swap swap      21474836480 -                   -
rpool/ROOT/sol10_U10_101512 zfs        8365630464 /                   -
rpool/export            zfs          21292032 /export             -
rpool/export/home       zfs          21259264 /export/home        -
rpool                   zfs       32889929728 /rpool              -
# lufslist sol10_U10x86
               boot environment name: sol10_U10x86
               This boot environment is currently active.
               This boot environment will be active on next system boot.

Filesystem              fstype    device size Mounted on          Mount Options
----------------------- -------- ------------ ------------------- --------------
/dev/zvol/dsk/rpool/swap swap      21474836480 -                   -
rpool/ROOT/sol10_U10x86 zfs          59540480 /                   -
rpool/export            zfs          21292032 /export             -
rpool/export/home       zfs          21259264 /export/home        -
rpool                   zfs       32889929728 /rpool              -

Siralos

View Public Profile for Siralos

Find all posts by Siralos

6 More Discussions You Might Find Interesting

1. Solaris

Solaris Patching vs OS Upgrade

Hello, I have a doubt regarding patching and OS upgrade. What is the difference when i install a Recomended Patch Cluster using installcluster script on a solaris10 update 6 server vs Upgrading Solaris 10 update 6 to update 10 ? I have applied update10 Recomended Patch Cluster on a...

2. Solaris

Solaris patching issue with Live Upgrade

I have Solaris-10 sparc box with ZFS file-system, which is running two non global zones. I am in process of applying Solaris Recommended patch cluster via Live Upgrade. Though I have enough space in root file-system of both zones, everytime I run installcluster, it fails with complaining less...

3. Red Hat

Unable to login after patching

Hello, Sorry for posting here..i know there is another section for Urgent...However, i could not locate it... Issue: ) After patching rhel 5.8 with couple of patches. When user is trying to login via putty . They get login promt and when they type their username, screen get freezed kindaa...

4. Solaris

Solaris 10 patching using live upgrade with VxVM

Hello, I was assigned some Solaris machines and need to patch them to N-1, where N is the latest OS realease, which means, upgrade till one version before the latest one. I do not now a lot about Solaris. What I only know is that need to make use of live upgrade and be careful with VxVM...

5. 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)...

6. Solaris

How to use live-upgrade with single disk, pre-patching steps?

Hi, I have Solaris-10 x86 (running on HP hardware), with 12 non-global zones running on this. I have to install latest patch cluster/set on this server. This server is not under backup schedule, so before installing patch cluster, I want to keep a backup. In case of any issue (bad patch or...

LEARN ABOUT SUNOS

lucancel

lucancel(1M)						  System Administration Commands					      lucancel(1M)

NAME

       lucancel - cancel a scheduled Live Upgrade copy/create procedure

SYNOPSIS

       /usr/sbin/lucancel [-l error_log] [-o outfile] [-X]

DESCRIPTION

       The  lucancel  command  is  part  of  a	suite  of commands that make up the Live Upgrade feature of the Solaris operating environment. See
       live_upgrade(5) for a description of the Live Upgrade feature.

       The lucancel command cancels a boot environment (BE) creation or upgrade that was scheduled in the FMLI-based  interface,  lu(1M),  or  the
       repopulation  of  a BE, scheduled with lumake(1M). lucancel does not cancel a job that is active (that is, is in the process of creation or
       repopulation).

       The lucancel command requires root privileges.

OPTIONS

       The lucancel command has the following options:

       -l error_log

	   Error and status messages are sent to error_log, in addition to where they are sent in your current environment.

       -o outfile

	   All command output is sent to outfile, in addition to where it is sent in your current environment.

       -X

	   Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num>  is  the  version
	   number of the DTD file.

EXIT STATUS

       The following exit values are returned:

       0	Successful completion.

       >0	An error occurred.

FILES

       /etc/lutab

	   list of BEs on the system

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWluu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       lu(1M),	luactivate(1M),  lucompare(1M),  lucreate(1M),	lucurr(1M), ludelete(1M), ludesc(1M), lufslist(1M), lumake(1M), lumount(1M), lure-
       name(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5)

SunOS 5.10							    21 Dec 2001 						      lucancel(1M)