Solaris patching issue with Live Upgrade


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris patching issue with Live Upgrade
# 8  
Old 05-02-2013
I know that I'm a bit late to the party on this question, but this should allow you to perform the update without the error you showed in the original post.

Code:
./installpatchset -B 19_march --s10patchset --disable-space-check

Before you do this be absolutely sure you have a good, current backup of the data specifically on the two filesystems listed in the error message. It's a good idea to have a backup of everything before performing any updates, but especially in a situation like this.

-Tom
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. 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... (4 Replies)
Discussion started by: solaris_1977
4 Replies

2. 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)... (3 Replies)
Discussion started by: javanoob
3 Replies

3. 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... (4 Replies)
Discussion started by: feroccimx
4 Replies

4. Solaris

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 tail -15 /var/svc/log/rc6.log Legacy init script "/etc/rc0.d/K50pppd" exited with return code 0. Executing legacy init... (5 Replies)
Discussion started by: Siralos
5 Replies

5. Solaris

Solaris 10 Live Upgrade Issue

Hi Guys, having an issue with running Live Upgrade on a t5240 runiing Solaris 10 5/08. The system has the required patches 121430, and Live upgrade was updated from the install media sol-10-u10-ga2-sparc-dvd.iso The following boot environments were created solenv1 and solenv2 with the... (8 Replies)
Discussion started by: Revo
8 Replies

6. Solaris

Solaris Live Upgrade issue with Zones

I 'm running solaris10 u6 with 141414-02. My system is T5220 running 2 Ldoms and 7 zones on primary domain. I 'm tryin to create booth environment on my alternate root disk after breaking the SVM mirroring but it does not go well and stuck at some point , and i have to reboot the system to get rid... (1 Reply)
Discussion started by: fugitive
1 Replies
Login or Register to Ask a Question
lurename(1M)						  System Administration Commands					      lurename(1M)

NAME
lurename - change the name of a boot environment SYNOPSIS
/usr/sbin/lurename -e BE_name -n new_name [-l error_log] [-o outfile] [-X] DESCRIPTION
The lurename 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 lurename command renames the boot environment (BE) BE_name to new_name. The string new_name must not exceed 30 characters in length and must consist only of alphanumeric characters and other ASCII characters that are not special to the Unix shell. See the "Quoting" section of sh(1). The BE name can contain only single-byte, 8-bit characters. It cannot contain whitespace characters. Also, new_name must be unique on the system. A BE must have the status "complete" before you rename it. Use lustatus(1M) to determine a BE's status. Also, you cannot rename a BE that has file systems mounted with lumount(1M) or mount(1M). Renaming a BE is often useful when you upgrade the BE from one Solaris release to another. For example, following an operating system upgrade, you might rename the BE solaris7 to solaris8. The lurename command requires root privileges. OPTIONS
The lurename command has the options listed below. -e BE_name Name of the BE whose name you want to change. -l error_log Error and status messages are sent to error_log, in addition to where they are sent in your current environment. -n new_name New name of the BE. new_name must be unique on a given system. -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 /usr/share/lib/xml/dtd/lu_cli.dtd.<num> Live Upgrade DTD (see -X option) ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWluu | +-----------------------------+-----------------------------+ SEE ALSO
lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), lucurr(1M), ludelete(1M), ludesc(1M), lufslist(1M), lumake(1M), lumount(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5) SunOS 5.10 24 Jan 2002 lurename(1M)