Zone stuck in shutting down state.

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris 10: I forgot to detach a zone before zpool export. Uninstall zone?

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. AIX

Hard Drive stuck in populated state?

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

3. AIX

Open firmware state to running state

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.

4. Solaris

Zone in down state

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

5. Solaris

Zone failes to boot due to mount issue, dir exists in zone.

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. BSD

Process stuck in "pipewr" state

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

7. UNIX for Advanced & Expert Users

Processes on FreeBSD are stuck in "pipewr" state

8. Solaris

Help with zone in "mounted" state

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

9. Solaris

Non-global zone not in a patchable state

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

10. Solaris

Zone in down state.

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 ) ?

LEARN ABOUT OPENSOLARIS

brands

brands(5)						Standards, Environments, and Macros						 brands(5)

NAME

       brands - alternate operating environments for non-global zones

DESCRIPTION

       The branded zone (BrandZ) framework extends the Solaris Zones infrastructure described in zones(5) to include the creation of brands, which
       provide non-global zones that contain non-native operating environments.

       The term "brand" can refer to a wide range of operating environments. All brand management is performed as extensions to the current  zones
       structure.

       Every  zone is configured with an associated brand. The brand type is used to determine which scripts are executed when a zone is installed
       and booted. In addition, a zone's brand is used to properly identify the correct application type at application launch time.  The  default
       is the native brand.

       A  branded  zone  will support exactly one brand of non-native binary, which means that a branded zone provides a single operating environ-
       ment. Once a zone has been assigned a brand, that brand cannot be changed or removed.

       BrandZ extends the zones tools in the following ways:

	   o	  A brand is an attribute of a zone, set at zone create time.

	   o	  The zonecfg tool (see zonecfg(1M)) is used to set a zone's brand type and configure the zone.

	   o	  The zoneadm tool (see zoneadm(1M)) is used to report a zone's brand type and administer the zone.

   Device Support
       The devices supported by each zone are documented in the man pages and other documentation for that brand. The zones infrastructure detects
       any  attempt  to  add  an  unsupported device and issues a warning to the administrator. If the administrator chooses to add an unsupported
       device despite that warning, that device might or might not work as expected. The configuration will be untested and unsupported.

ATTRIBUTES

       See attributes(5) for a description of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWzoneu 		   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Evolving			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       mdb(1), zlogin(1), zonename(1), dtrace(1M),  in.rlogind(1M),  sshd(1M),	zoneadm(1M),  zonecfg(1M),  kill(2),  priocntl(2),  getzoneid(3C),
       ucred_get(3C), getzoneid(3C), proc(4), attributes(5), lx(5), native(5), privileges(5), zones(5), lx_systrace(7D), crgetzoneid(9F)

SunOS 5.11							    13 Feb 2009 							 brands(5)

Solaris