Technical data
zoneadm attach Command Might Fail (6550154)
When you attach a zone, if the original host and the new host have packages at the same patch
level but at dierent intermediate patch histories, the zone attach might fail. Various error
messages are displayed. The error message depends on the patch histories of the two hosts.
Workaround: Ensure that the original host and the new host machines have had the same
sequence of patch versions applied for each patch.
Solaris is Unable to Handle Mode Switches Between
Legacy and AHCI Modes for the SATA Controller
(6520224)
In systems which have an AHCI compliant SATA controller, the BIOS setup typically enables
the controller to be set in either AHCI, legacy, or RAID modes. Solaris supports AHCI and
legacy modes.
The SATA mode setting in BIOS must not be changed after an initial Solaris installation. The
SATA mode setting must also not be changed before or after a Solaris upgrade. If the SATA
mode BIOS setting is modied after installing Solaris, the system will reset and fail to boot
without indicating what led to the failure.
Workaround: If boot failure is encountered as a result of changing the BIOS setting, revert back
to the original setting in order to boot Solaris.
Deferred Activation Patching (6486471)
Starting with patch 119254-42 and 119255-42, the patch installation utilities, patchadd and
patchrm, have been modied to change the way that certain patches delivering new features or
existing les that are incompatible with the running system are handled. This utilities
modication aects the installation of these patches on any Solaris 10 release. These
“deferred-activation” patches handle the large scope of change delivered in Kernel patches
better.
In deferred Activation patching, a loopback le system, lofs, is used to create a copy of the root
le system. The original les being patched are copied to a safe location and the lofs copy of the
root le system is patched. Then the original le is lofs mounted back over the new le as it is
patched. This means the running system remains consistent over the duration of patching, new
features are not active and any incompatible change is hidden until the user reboots.
Users must reboot as soon as possible after applying a Deferred Activation Patch, but they do
not have to reboot immediately, they can still add further patches then reboot.
System Administration
Solaris 10 5/08 Release Notes • April 2008102