- Creating and Using Oracle Solaris Zones
- Troubleshooting Miscellaneous Oracle Solaris Zones Problems
- Troubleshooting a Zone That Has Failed
- How to Manage a Zone That Has Become Unavailable
How to Manage a Zone That Has Become Unavailable
For demonstration purposes, this procedure refers to the UUID of the zone instead of the zone name.
- Become a zone administrator.For more information, see Using Rights Profiles to Install and Manage Zones. 
- Display the UUIDs of the zones on the system.global$ zoneadm list -cp 0:global:running:/::solaris:shared:-:: ID:zonename:status:zonepath:UUID 
- If necessary or possible, shut down the zone.global$ zoneadm -u UUID shutdown
- Verify that the zone is in the installed state.global$ zoneadm list -cpAn installedstatus indicates that a zone is not booted.
- Determine whether the zone's unavailability is temporary or permanent.Your investigation and analysis might extend beyond just zone-specific issues. 
- Change the status of the zone.The status depends on the nature of the problem. - 
                           
                           The problem is temporary. Temporary failures might be caused by dropped network connections, misconfiguration, and other resolvable issues. For this type of problem, do the following: - 
                                 
                                 Mark the zone's status as unavailable. global$ zoneadm -u UUID mark unavailableThe unavailablestatus indicates that an installed zone cannot be booted. This state is displayed by thezoneadm list -pcommand.
- 
                                 
                                 Fix the problem that caused the zone to fail. 
- 
                                 
                                 After the problem is resolved, return the zone to the installedstate.global$ zoneadm -u UUID attach
- 
                                 
                                 (Optional) Put the zone in a ready state. global$ zoneadm -u UUID mark readyPerform this step if you do not want to use the zone at this time. Booting the zone in the next step automatically brings the zone to a ready state before booting. 
- 
                                 
                                 Boot the zone. global$ zoneadm -u UUID boot
 
- 
                                 
                                 
- 
                           
                           The problem is permanent. Permanent problems might be in the form of corrupt ZFS file systems, for example. You cannot recover a zone that undergoes a permanent failure. - 
                                 
                                 Mark the zone's status as incomplete. global$ zoneadm -u UUID mark incompleteNote: Marking a zoneincompleteis irreversible.
- 
                                 
                                 Uninstall and remove the zone. 
 
- 
                                 
                                 
 
-