10-09-2009
Zone stuck in shutting down state.
One of my zone got stuck while rebooting in shutting down state. I tried following
1. Halt the zone with zoneadm -z zone1 halt
2. kill zoneadmd process for that zone and halt the zone
but none helped me. How can i shut it down and restart it ?
---------- Post updated 10-09-09 at 01:54 AM ---------- Previous update was 10-08-09 at 11:11 PM ----------
never mind i forcefully unmounted my zfs file system (dataset ) from the zone and it started running again.
10 More Discussions You Might Find Interesting
1. Solaris
One of my zone is stuck in down state, not able to boot it or halt it .. not even detach .. is there any way to recover without rebooting the whole system ( global zone ) ? (3 Replies)
Discussion started by: fugitive
3 Replies
2. Solaris
Hi
I am trying to install the latest patch cluster on a Solaris 10 box in single-user mode. However when I run the ./installcluster command I get the following error:
All our zones have been working fine as far as we know as they are all serving live websites.
Does anyone have any... (2 Replies)
Discussion started by: skewbie
2 Replies
3. Solaris
Greetings Forumers!
I have a zone in a "mounted state and cannot do anything with it:
# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
4 zone1 running... (11 Replies)
Discussion started by: bluescreen
11 Replies
4. UNIX for Advanced & Expert Users
Hi Experts,
I am executing "svn" checkout command through my java code on a freeBSD machine. SVN checkout gets started , but when I run "top" command on my freebsd machine, I have observed that "svn" processes are stuck in "pipewr" state.
Any pointer for this problem?
Thanks,
akash (0 Replies)
Discussion started by: akash.mahakode
0 Replies
5. BSD
Hi Experts,
I am executing "svn" checkout command through my java code on a freeBSD machine. SVN checkout gets started , but when I run "top" command on my freebsd machine, I have observed that "svn" processes are stuck in "pipewr" state.
Any pointer for this problem?
Thanks,
akash (0 Replies)
Discussion started by: akash.mahakode
0 Replies
6. Solaris
I have two physical servers, with zones that mount local storage.
We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point).
It failed to mount on every boot because the directory existed in the zone.
I... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies
7. Solaris
Hi all,
One of my zone is stuck in down state, not able to boot it or halt it
root@xpm9ka1 # zoneadm list -iv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
2 bsmrxdb4 down /zones/bsmrxdb4 native shared
root@xpm9ka1 # zoneadm -z bsmrxdb4 boot
zoneadm: zone... (6 Replies)
Discussion started by: peppeunz
6 Replies
8. AIX
Hi Admins,
I am having a whole system lpar in open firmware state on HMC.
How can I bring it to running state ?
Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies
9. AIX
Hi all,
I ended up replacing a failed disk drive on my power 7. I had a few issues with unmirroring as it had a stale logical volume. I ended up finally getting it to unmirror the rootvg. I had an empty space in slot 3 so I ended up putting the new disk in slot 3. It configured to hdisk0 with no... (2 Replies)
Discussion started by: AlexanderIII
2 Replies
10. UNIX for Advanced & Expert Users
Dear all,
recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes.
I did the following:
host1:
$ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed
$ zpool export zone1
host2:
$ zpool... (2 Replies)
Discussion started by: custos
2 Replies
LEARN ABOUT OPENSOLARIS
native
native(5) Standards, Environments, and Macros native(5)
NAME
native - native branded zone
DESCRIPTION
The native brand uses the branded zones framework described in brands(5) to run zones installed with the same software as is installed in
the global zone. The system software must always be in sync with the global zone when using a native brand.
SUB-COMMANDS
The following native brand-specific subcommand options are supported in zoneadm(1M).
attach [-u] [-b patchid]...
For native zones, zoneadm checks package and patch levels on the machine to which the zone is to be attached. If the packages/patches
that the zone depends on from the global zone are different (have different revision numbers) from the dependent packages/patches on
the source machine, zoneadm reports these conflicts and does not perform the attach. If the destination system has only newer dependent
packages/patches (higher revision numbers) than those on the source system, you can use the -u option to update the attached zone to
match the -revision packages and patches that exist on the new system. With -u, as in the default behavior, zoneadm does not perform an
attach if outdated packages/patches are found on the target system.
For native zones, one or more -b options can be used to specify a patch ID for a patch installed in the zone. These patches will be
backed out before the zone is attached or, if -u was also specified, updated.
install [-a archive] | [-d path] [-p] [-s] [-u] [-v] [-b patchid]...
The native brand installer supports installing the zone from either the software already installed on the system or from an image of an
installed system running the same release. This can be a full flash archive (see flash_archive(4)) or a cpio(1) or pax(1) "xustar" ar-
chive. The cpio archive be compressed with gzip or bzip2. The image can also be a level 0 ufsdump(1M), a path to the top-level of a
system's root tree, or a pre-existing zone path.
With no options the zone is installed using same software as is running the global zone.
To install the zone from a system image either the -a or -d is required. Either the -u or -p option is also required in this case.
-a archive
The path to a flash_archive(4), cpio(1), or pax(1) "xustar" archive, or a level0 ufsdump(1M), of an installed system. cpio archives
may be compressed using gzip or bzip2.
-b patchid
One or more -b options can be used to specify a patch ID for a patch installed in the system image. These patches will be backed
out during the installation process.
-d path
The path to the root directory of an installed system. If path is a hyphen (-), the zonepath is presumed to be already populated
with the system image.
-p
Preserve the system configuration after installing the zone.
-s
Install silently.
-u
Run sys-unconfig(1M) on the zone after installing it.
-v
Verbose output from the install process.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWzoneu |
+-----------------------------+-----------------------------+
|Interface Stability |Uncommitted |
+-----------------------------+-----------------------------+
SEE ALSO
cpio(1), pax(1), zlogin(1), zonename(1), sys-unconfig(1M), ufsdump(1M), zoneadm(1M), zonecfg(1M), flash_archive(4), attributes(5),
brands(5), privileges(5), zones(5), lx_systrace(7D)
SunOS 5.11 13 Feb 2009 native(5)