Technical data
global# zoneadm -z myzone ready ; zoneadm -z myzone halt
Upgrading a Solaris 10 System with Non-Global Zones
to the Solaris 10 5/08 Release Might Cause the Local
File System Service to Fail (6428258)
Upgrading a Solaris 10 3/05 system or a Solaris 10 1/06 system to the Solaris 10 6/06, Solaris 10
8/07, or the Solaris 10 5/08 release with non-global zones might cause the SMF service that
mounts local le systems to fail in the non-global zones. As a result, other services in the
non-global zones might fail to start.
After upgrading a Solaris 10 system with non-global zones to the Solaris 10 6/06, Solaris 10 8/07,
or the Solaris 10 5/08 release, services might be in the maintenance state. For example:
# zlogin myzone svcs -x
svc:/system/filesystem/local:default (local file system mounts)
State: maintenance since Wed May 24 13:18:06 2006
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/system-filesystem-local:default.log
Impact: 18 dependent services are not running. (Use -v for list.)
Workaround:
Reboot the non-global zone from the global zone. For example:
global# zoneadm -z myzone reboot
Device ID Discrepancies After Upgrading From Solaris
9 9/04 OS
In this Solaris 10 release, Solaris Volume Manager displays device ID output in a new format.
Solaris 9 9/04 OS, which introduced device ID support in disk sets, does not recognize the new
format. When you upgrade to Solaris 10 OS from the Solaris 9 9/04 release, device IDs that are
associated with existing disk sets are not updated in the Solaris Volume Manager conguration.
If you need to revert to Solaris 9 9/04 OS, conguration changes made to disk sets after the
upgrade might not be available to Solaris 9 9/04 OS. For more information, see
Chapter 25,
“Troubleshooting Solaris Volume Manager (Tasks),” in Solaris Volume Manager
Administration Guide
.
Upgrade Issues and Bugs
Chapter 1 • Installation Issues 43