I was reading few posts and I think this could work
And then I can run patch set on new-zfsBE
All my zones are residing on rpool, as there is only one pool, so I will have option to revert to old environment, including all zones.
I am yet to test this.
*****UPDATE*****
I was able to create new-zfsBE on same disk and install patchset on that BE. After completion, I activated that and rebooted (with init 6) and all was good.
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)
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... (7 Replies)
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... (1 Reply)
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)
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
LEARN ABOUT MOJAVE
install-solaris
install-solaris(1M)install-solaris(1M)NAME
install-solaris - install the Solaris operating system
SYNOPSIS
install-solaris
install-solaris invokes the Solaris Install program. Depending on graphical capability and available memory at the time of invocation,
install-solaris invokes either a text-based installer or a graphical installer.
The following minimum requirements for physical memory dictate which features are available during installation:
For SPARC machines:
128 MB
Minimum physical memory for all installation types
128 MB
Minimum physical memory required for windowing system
384 MB
Minimum physical memory required for graphical-based installation
For x86 machines:
256 MB
Minimum physical memory for all installation types
256 MB
Minimum physical memory required for windowing system
512 MB
Minimum physical memory required for graphical-based installation
In some cases, even if the minimum physical memory is present, available virtual memory after system startup can limit the number of fea-
tures available.
install-solaris exists only on the Solaris installation media (CD or DVD) and should be invoked only from there. Refer to the for more
details.
install-solaris allows installation of the operating system onto any standalone system. install-solaris loads the software available on the
installation media. Refer to the for disk space requirements.
Refer to the for more information on the various menus and selections.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcdrom (Solaris instal- |
| |lation media) |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
pkginfo(1), install(1M), pkgadd(1M), attributes(5)
It is advisable to exit install-solaris by means of the exit options in the install-solaris menus.
23 Sep 2005 install-solaris(1M)