Installation guide
# 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.
x86: Adding Driver Updates Might Cause Failure of
Network Conguration (6353146)
Installation of the Solaris 10 OS might fail while you are adding Driver Updates (DU), which are
also known as Install Time Updates (ITU). This error occurs if you are using the GUI to install
the Solaris 10 software. The following message is displayed:
Unable to run cmd: /usr/sbin/sysidput
Workaround: Use either of the following workarounds.
■
Workaround 1: Congure the installation to use DHCP to gather network conguration
information.
■
Workaround 2: Use a text-based installation method.
■
If you are performing the text-based installation in a desktop session, follow these steps.
1. After you have nished adding ITUs, type Ctrl-c instead of typing e.
Upgrade Issues and Bugs
Solaris 10 5/08 Release Notes • April 200844